Project properties are similar to global data except for a few key differences. Global data cannot be edited in the properties.config file. You can write to global data, but you can only read project properties. Also, global data values can be different for each invoked instance of the process. Project properties stay constant across all instances.
The project properties are as follows:
Project properties stay constant across all instances of the project.
Project properties are stored with the project files in properties.config
Project properties are only Text (string) data type.
Project properties are accessible anywhere in your project.
Use project properties like you use any other data element. Project properties appear as a separate node in the variable picker.
Remember, project properties are visible only in the components that take Text (string) type data.
After you publish a project with project properties, you can edit the values of the properties in the properties.config file without having to publish again.
By default properties.config is located in C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\Project Name.
Symantec recommends that you use project properties for environment settings (such as a SQL server connection string). Instead of setting environment settings as static variables in your process, use project properties. If the environment settings change in the future, you can easily edit them in the properties.config file.
Although project properties can be only Text (string) data type, you can enter other data, such as a date or a number. If you use these alternative values, use components in your project to translate the values into Text (string) type. For example, you can use a Get Number From String or Convert String To Date component to convert Text data into Number data. You can also set a project property to be a password property. Password properties are masked values. Password properties are useful for other things than passwords, such as database connection strings (which often contain passwords). Use password properties to mask any value that you do not want all future designers to have access to when they work on your project.
Project properties also have description and category fields. Symantec recommends that you include a description of all of your properties. Categories are optional. If you have a number of related properties, you may want to create categories to group them together.
Notice that the defined categories show up as headers in the Properties Editor during publishing.
Imported Document ID: HOWTO61638
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe