Indicators and strategies distribution

You can grant access to the developed indicators or strategy(modules) for any ATAS user, set the access expiration date and turn off access at any moment of time.

To do it, it is necessary to:

1. Activate an option of loading modules into the Personal Area
2. Prepare the module
3. Load it into the service

1) To activate the option of loading module, you need:

1. To be registered in the Personal Area
2. To activate the ‘Activate the Module Section’ option in the Profile ->For Developers section
3. The My Modules section will appear in the left menu after that. In this section, you can add new module, set users, who have access to these modules, and access expiration.

2) Preparation of a module

Every module, which would be distributed among other users, should have a unique identifier. The FeatureId attribute is designed for it. This attribute should be assigned to each module, which is included into the distributed package, specifying a unique string identifier. 

Example:

[FeatureId("DFD43423-6645-4490-B5F7-45579FF940EE")]

    public class MyIndicator : Indicator

    {

        //your code

    }

One and the same identifier could be assigned to several modules. In such a case, you will be able to control the access of the whole group of modules from the Personal Area.

After the module is ready, it is necessary to compile it. We also recommend obfuscating the module for its protection.

3)Loading the module into the service

1. Go to the Modules section  
2. Press theAdd modulebutton
3. Fill in all the fields in the resulting form:
   1. Module name - name
   2. Module UID - the identifier, specified in the FeatureId attribute
   3. Description - arbitrary description
   4. File - select the compiled dll file

After creating the module, you get the link to the dll file loaded to the service.

You can send this link to your users for downloading the module.

Also, for each such module, you can specify users, who have access to it, and the date of access expiration.

If a user has a downloaded module but has no access or access expired, the user will not see this module in the platform and will not be able to use it.