The process property is the most basic type of property. Process properties are defined locally for each process, for example a subprocess can have its own process property, processes in shared modules can have their own process properties, and so on.
- A process property can be assigned to multiple activities within the process. At design time, when you assign a process property to an activity, only the name and the type of the property is associated with the activity, not its value. The value of the property is stored in the process and remains a part of the process. At runtime, the value gets injected into the property. So, if a property is assigned to multiple activities, if you change the value of the property on one activity, keep in mind that the value of the property will change for all activities that use that property.
- Even though a process property is assigned to multiple activities, it can have only one value across all activities. You cannot use the same process property for multiple activities in a process but assign a different values for the property for each activity that it is assigned to.
- Multiple process properties within the same module can get their value from the same Module property.
- Process properties are also visible in the Outline view of a process.