To view model properties, click the model name in the My Process Models panel. The property panel of the selected model opens, where you can set and edit model properties.
Figure: Model Properties
Specific property tabs are provided for viewing problems, editing comments or setting specific model properties.
The following general properties are displayed for a model:
Figure: Model ID - Editable
For more information, please refer to the section Editing Model ID.

Figure: Picking a valid from date from the calendar
You can edit model ID in the Integrator profile only.
To edit the model ID:
Figure: Edit Model ID
If the model ID matches with another model ID, then a validation message is displayed and the ID automatically changes back to the original ID.
Figure: Edit Model ID - Validation
For general details and restrictions on model identifiers, please refer to chapter Model Element Identifiers of the Key Concepts. Model Element Identifiers of the Stardust Key Concepts.
Problems - This tab displays validations (errors and warnings)
that are performed on all the elements included in the model.
Click the Refresh Validation
icon to view the
validations. It displays Severity, Element and Description for the
validation.
Figure: Model Properties - Problems
Note that validations are not performed on sequence flows, conditional sequence flows and message transformation application.
You can specify comment in the text box and click Submit. The newest comment gets displayed at the top of the table. To delete the comment, select the comment and click the Delete icon. The user, who has submitted the comment, only that user can delete the comment. If the other user selects the comment or no comment is selected, the Delete icon remains in disabled state.
Figure: Model Properties - Comments
The Configuration Variables tab displays a table with configuration variables defined for a model. Configuration variables are displayed in the following scenarios:
Note that, although the activity criticality is calculated for models with the Criticality formula from engine side after a deployment, there is no option to define a criticality formula directly in the Modeling perspective.
For details on managing configuration variables, please refer to chapter Configuration Variables View in the Administration Perspective of the Stardust Portal.
The following columns are displayed in the Configuration Variables table:
String or Password)
Figure: Configuration Variable
To refresh the view, click the Refresh
icon in the upper left corner of the table.
Note that it is not possible to add a configuration variable directly in the configuration variable view. You can add it indirectly by referencing a variable from a String type model element as described in section Creating a Configuration Variable by Reference.
The following two types are supported for configuration variables:
Please refer to section Defining Configuration Variable Types for Security Information
for details on how to create a variable of type Password.
In the References column, all model elements that reference the variable are displayed.

Figure: References column
The corresponding column entry displays the following details:
If more than three references of a configuration variable exist, the Show All References link is displayed below the third reference. Click the link to view all the references.

Figure: Show All References
To hide the expanded references, click the Collapse References link.

Figure: Collapse References
To delete a configuration variable, perform the following steps:

Figure: Delete Configuration Variable
For example, we use a configuration variable named CustomerID with a default String value
4711.

Figure: Example Configuration Variable
This variable is referenced from a Primitive data via ${CustomerID}.

Figure: Configuration variable referenced from a Primitive Data
From the Configuration Variables tab, we delete this variable with three different options:

Figure: Default value replaced with empty literal

Figure: Default value replaced with default variable value

Figure: Enter text as arbitrary literal

Figure: Default value replaced with specified text
Note
Take care to substitute a deleted configuration variable with a reasonable value, especially if it is referenced
in a data path or a condition expression of a sequence flow!
You can reference variables in the properties of all model elements that are accessible via String properties. These could be for example data paths, default data values or condition expressions of sequence flows.
To reference a variable in an element property, enter the following syntax:
${variable name}
The validation on configuration variables is performed and displayed in the Problems tab of the
model properties. Note that the variable name must not contain invalid characters like
Configuration variables, their values and references are stored in the model file as extended attributes:
<carnot:Attribute Name="ipp:variables[7]:name" Value="Environment" Type="String"/> <carnot:Attribute Name="ipp:variables[7]:defaultValue" Value="TEST" Type="String"/> <carnot:Attribute Name="ipp:variables[7]:description" Value="Environment variable to decide whether working in production or test mode." Type="String"/>
To create a configuration variable by reference, add a reference to a configuration variable, which does not
exist, in a model element via the pattern described in the previous section, e.g. ${CompanyName}.
For example, add a reference to a non-existing configuration variable CompanyName via
${CompanyName} in the value field of a composite descriptor.

Figure: Reference a non-existing variable
Now switch to the Configuration Variables tab of the model property. You see the newly created configuration variable CompanyName listed in the table.

Figure: New configuration variable
You can define a data type for a configuration variable, which initiates a type validation of the values defined via API or from within the Configuration Variables view. This allows a runtime configuration of arbitrary server-side security-relevant data at required places in the model.
To create a configuration variable of type Password, perform the following steps:
${name:type}, for example:
${token:Password}. Note that the type must be specified as Password.

Figure: Define Password Type
token is created with type Password.

Figure: Configuration Variable - Password Type
If you enter a default value for a configuration variable of type Password, this value is masked in
the table.

Figure: Masked default value
In this tab in you can add and modify Quality Assurance codes that can be used to track the reasons for Quality Assurance failures.
In an interactive activity marked for quality assurance, you can select one or more of these quality assurance codes. Please refer to section Quality Assurance Codes of chapter Specifying Activity Properties for details.
The Quality Assurance Codes tab contains a table of all Quality Assurance codes defined for the model with their values.

Figure: Quality Assurance Codes
To add a new code, click the Add icon
in the toolbar. Enter the code ID, name and description.
Note the following restrictions:
For further restrictions and general details on model element identifiers, please refer to chapter Model Element Identifiers of the Key Concepts. Model Element Identifiers of the Stardust Key Concepts.
To delete a code, select the according row and click Delete icon
in the toolbar.
To edit a code in the table, click in the according entry field and enter the new value.
Figure: Editing Quality Assurance Code entries
You can use the Move Up and Move Down buttons to adjust the order of the codes in the table.
Figure: Moving Quality Assurance Code entries
You can secure the model using the Read-only tab.
The read-only action locks the model from any editing and requires the password to make it editable. For models that are editable, the status is displayed as Writable. To secure a model, perform the following steps:
Figure: Read-only tab - Editable Model
Figure: Specify Password
Figure: My Process Models -
Lock icon for Read-only Model
Figure:
Warning - Save Models
Note that the context menu of a read-only model does not contain the options to rename, delete or create a new process.

Figure: Read-only Model - Context Menu Options
Also, the Undo and Redo icons are disabled when you mark the model as read-only.
All the other operations on all the elements of a model are not displayed for a read-only model. All fields and controls in all views and property panels are disabled except the Test tab of the applications. The process diagram canvas and the main toolbar icons are also disabled except the Zoom In, Zoom Out and Print icons. If you try to click the element added in process diagram canvas, the following message is displayed.
Figure: Read-only Model - Process Diagram Canvas
If the model is marked as Read-only then you can again provide the password and remove the security. To remove the model security, perform the following steps:
Figure: Make Writable
In the following scenarios, Eclipse compatibility of read-only models is required.
If you download a read-only model and import it in the Eclipse-based modeler, the model becomes editable.
However, if you import the same model (which was marked as read-only in the Modeling perspective) from the Eclipse-based modeler into the Modeling perspective, the Read-only status is maintained.
When the model is marked as read-only,
stardust:security:hash
attribute is added to the XPDL file of the model. If you download
and remove this attribute from the XPDL file of the read-only
model then the read-only status is not maintained when imported in
the Modeling perspective.
<carnot:Attribute Name="stardust:security:hash" Value=""/>
Note that you can reference the read-only model in any other model. But you cannot modify any element of the referenced read-only model.
To avoid undetected overwrites, the edit lock functionality is
provided. If a user is editing a model then any other user won't
be able to edit the same model from any other user session. If a
user is working on model A, then any other user session displays
the lock icon
on the model node and a tooltip text in the My Process Models
panel.
Figure: Model Node - Lock icon and Tooltip Text
Note that right-clicking on any element of the locked model in the My Process Models panel, won't open the context menu for it. Only Download and Deploy operations are supported from the context menu of the locked model.
Open the Edit Lock tab in the Model Properties and note the status of a locked model. Lock is released when the owner triggers the Save All operation.
Figure: Edit Lock
Locks can be broken manually by:
Click Yes in the Break Edit Lock dialog. Any edit or save operation from the previous owner's session will be prevented.
Figure: Break Edit Lock
Then, check the current state of the model in the Edit Lock tab of model properties.
Figure: Edit Lock