Developer Documentation Library > Interviewer - Server Admin > Customizing UNICOM Intelligence Interviewer - Server Admin > Activity configuration files > Activity interface documents > ApplicationSettings element
 
ApplicationSettings element
The ApplicationSettings element contains a collection of properties that are used internally by the activity and externally by activity management tools. The following properties must be defined for each activity.
Properties
ApplicationType
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:
design, manage, datacollection,reports, and other.
You can use other values of your own, but Server Admin puts the activities in the other group, unless these values are in the Public resources file,
DisplayName
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.
DPMAccessType
ReadOnly if the activity reads from DPM but does not write to it.
ReadWrite if the activity can read from and write to DPM. The project is locked when the activity is entered.
EditablePropertiesList
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 * (asterisk), which means that 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 following property string allows non-administrator users to edit the project’s IsMobile and QuotaAutoCommit properties:
EditablePropertiesList="IsMobile;mrInterview\QuotaAutoCommit"
When non-administrator users try to insert a new property into a project’s existing properties, the new property name must be defined in the EditablePropertiesList. Non-administrator user can create new properties only when the property names are in the EditablePropertiesList or when EditablePropertiesList is set to * (the default setting).
FileAccess
A list of file types that can be accessed by the activity. Separate the file types by using a comma or a semi‑colon. For example, "mdd;xml" or "*.mdd;*.xml".
The default value is * (asterisk).
FileAccessType
One of the following values: None, ReadOnly, ReadWrite, and ReadWriteNoLock.
None indicates that there is no file access.
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. The project is locked when the activity is entered.
ReadWriteNoLock value indicates that the activity reads and writes, but the project should not be locked while using the activity.
This property is also used with the FileManagerWebServiceAllowedActivities DPM property to indicate which activities can use the File Manager Web Service.
ProjectFilesRequired
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 can include * (for example, *.htm) or <projectid> to represent the project's name (for example, <projectid>.mdd refers to the .mdd file for the current project).
If the file list contains more than one reference, the activity is 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.
; (and) takes precedence over | (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.
PublicResourceFileName
The name of the public resource file.
PublicResourceFolder
The pathname of the folder containing the public resource file.
RequiredFilesLocation
Specifies the locations that should be searched for the project files required for this activity. Possible settings are:
User for the project’s folder in Users
Shared for the project’s folder in 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.
ShowInLauncher
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 ‘Activities and features’ on page 189.
StartURL
The relative URL that starts the activity.
SortIndex
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.
See also
Activity interface documents