Cascading property values

Property values can be passed down from a parent process to a dependent process. The value can cascade from a direct dependent relationship or from an indirect relationship.

For example, using the table below Process A is the top level process that depends directly on Process B and Process C. Process B depends on Process D. Process C and Process D do not have any dependencies.

Properties that meet the necessary requirements can be passed down from Process A to Process B and Process C.
The property also cascades down to Process D, the inheritance flow is Process A to Process B to Process D.

Table 1. Dependent process example
Parent	Child	Child
Process A	Process B	Process C
Process B	Process D

In order to cascade a property value to a dependent process, the following requirements must be met:

- The Cascade Properties to Dependencies option must be enabled. Click System > Server Settings > Misc to enable the option.
- Define the property on process template of the top level process.
  - The property must be defined in both the parent process and the dependent processes.
  - The User May Override option must be enabled for the property. This option is on the Properties page. This option indicates that there will be a prompt for the value of the property when the process runs instead of when the process is configured.
    
    Note: This option must be enabled on the process template for each dependent process that the property value is cascaded to if the dependent process is using a different process template than the high-level process.
- The dependency trigger between the high-level process and its dependent processes that the property is cascaded is either Pull or Push. The property value is not cascaded to a dependent process if the No Trigger is specified.