The activity's type. The following values are defined in the UNICOM Intelligence Interviewer - Server Admin resource file together with corresponding descriptions to display in Server Admin itself:

You may use other values of your own but unless these values are in the Public resources file, Server Admin puts the activities in the other group.

The name of the activity as it is to be displayed in Server Admin. If this property is empty, the activity ID is used instead.

ReadOnly if the activity reads from DPM but does not write to it. ReadWrite if the activity can read from and write to DPM.

Controls how non-administrator users can edit project properties in the Project Editor. Administrator users are always allowed to edit project properties.

The default value is an asterisk "*" character. When the property is empty or missing it will default to an asterisk. The default value means non-administrator users can edit all project properties in the Project Editor.

Specific property strings, that control access to specific project properties, can be defined for EditablePropertiesList. For example, the property string

allows non-administrator users to edit the project’s IsMobile and QuotaAutoCommit properties.

When non-administrator users attempt to insert a new property into a project’s existing properties, the new property name must be defined in the EditablePropertiesList. An error message is returned when a non-administrator user creates a property that is not defined in the EditablePropertiesList. Non-administrator user can only create new properties when the property names are in the EditablePropertiesList or when EditablePropertiesList is set to * (the default setting).

ReadOnly if the activity can read from existing files but not write to them. ReadWrite if the activity can read from existing files and write to them.

Files that must exist in RequiredFilesLocation in order for the activity to be visible in Server Admin. File references must be separated by semicolons, and may include * (for example, *.htm) or the special reference <projectid> to represent the project's name (for example, <projectid>.mdd to refer to the .mdd file for the current project).

If the file list contains more than one reference, the activity will be made available only if all files named in the list are present in the specified locations (the specification is read as an And condition). To make an activity available if one file or another is available, separate those file references with the | symbol. If a file list contains both And (;) and Or (|) symbols, the And takes precedence over the Or. For example,<projectid>.mdd;<projectid>.sif|*.sav makes the activity available on projects that have an .mdd file and a .sif for that project, and on projects that have a .sav file of any name.

The name of the public resource file.

The pathname of the folder containing the public resource file.

Specifies the locations that should be searched for the project files required for this activity. Possible settings are:

User for the project's folder within Users

Shared for the project's folder within Shared

Both for the project's folder in both the Users and Shared folders

Any for the project's folder in either the Users folder, or the Shared folder, or both.

True (1) if the activity is to appear in Server Admin. Some activities, such as Server Admin itself, need to register with DPM but should not appear in Server Admin. In these cases, ShowInLauncher should be False (0).

ShowInLauncher can be False when you want to control the activity's availability at a user level. A typical example is where users are to be allowed to test and activate questionnaires through the Build activity, but are not to have access to the Launch activity via the activity list. In these cases, users who need to see the restricted activities in the activity list should have the activity feature canViewInLauncher set. For more information, see Features element.

The relative URL that starts the activity.

A numeric value determining the activity's position in the Server Admin activity list. Activities are sorted in ascending numerical order of the SortIndex; activities with no SortIndex have an implied index of 999. If activities have different values for the ApplicationType property, then activities are sorted by sort index within activity type.