Resources

Field Description

Field Name

Resource. The context of the resource to be packed.

resource

Resource Description. Resource description that will be used in the resource table. This field supports localization. If Use Context Description is specified, Resource Description will be equal to the description of the local context pointed by Resource parameter.

description

Context Description. The description that will be used to name the context created during application deployment. This field supports localization. If Use Context Description is specified, description of the context on the target server (where the application was deployed) will be equal to description of local context pointed by Resource parameter.

contextDescription

Category. The category in which the resource will be placed within the resource table. This field supports localization. If Use Application Description is specified, Category will be equal to the application description.

category

Subcategory. The subcategory in which the resource will be placed within the resource table. This field supports localization.

subcategory

Group Name. This field defines name of a group in which the resource will be created during application deployment. If Use Application Name is specified, Group Name will be equal to the name of this Application context. If Do Not Create Group is specified, the resource will not be added to any group during application deployment.

groupName

Group Description. This field defines description of a group in which resource will be created during application deployment. This field supports localization. If Use Application Description is specified, Group Description will be equal to the description of this Application itself.

groupDescription

Version. Version of the resource, an integer number that starts from 1 and should be incremented each time a resource template is modified.

version

Dependencies. A table of resources on which the current resource will depend. For example, if two classes share a many-to-many relation or mutual foreign keys, each class must be added as a resource to the application, and each resource must list the other as a dependency.

dependencies

It is important to accurately determine all dependencies. Each context from the list of dependencies must exist.

Create on First Server Launch. The resource will be created when the server is first started if this does not contradict the resource creation mode selected during the server installation.

createOnFirstServerLaunch

Protected. A protected resource does not allow reading and changing its settings on the target server where the application was deployed. This helps to protect applications from reverse engineering.

protected

Note that resource protection is currently supported only for models.

Include Dependent Resources. If enabled, the application includes all dependent contexts in the export.

includeDependentResources

Include Dependent Variables. If enabled, the application includes all dependent variable values in the export.

includeDependentVariables

Include Dependent Variables must be enabled in order to preserve application behaviour that depends on variable values. For example, a trained Trainable Unit stores its data in a dependent variables. In order for the imported Trainable Unit to function without being retrained, it must be imported with its dependent variables.

Creation Template Expression. This expression must evaluate to a Data Table when the export action is run. The resulting Data Table is saved in the export and will be passed to the create method during the import procedure.

templateCreationExpression

Default Data Table

None

Default Row

None

Environment Variables

Standard environment variables