Description:

The Set Dynamic Properties workflow step sets dynamic properties on a specified Business Object using a mapped set of dynamic parameters.

The step identifies the Business Object and provides the dynamic property mappings that should be applied during workflow execution.

The step supports:

• Setting dynamic properties on a Business Object.
• Mapping Business Object properties through the BoProps data type.
• Supplying dynamic property values to a Business Object.
• Updating Business Object information from workflow data.
• Applying dynamically determined Business Object property values.
• Returning a True or False result.

This step can be used for:

• Updating Business Objects with workflow-generated information.
• Applying dynamic property values to Business Objects.
• Populating Business Object properties from Variables or other workflow data.
• Updating object information after an approval or decision.
• Synchronizing dynamically determined workflow data with Business Objects.
• Applying calculated or transformed values to Business Objects.
• Maintaining Business Object information during automated workflow execution.

Usage:

The Set Dynamic Properties step is typically used when workflow execution needs to apply dynamically supplied property mappings to a Business Object.

The workflow supplies:

• The name of the Business Object.
• The dynamic property mappings.

Typical workflow pattern:

Determine Data → Set Dynamic Properties → Continue Processing

For example:

Process Request → Set Dynamic Properties → Notify User

The workflow can determine the values to apply and then pass those values through the dynamic Business Object property mapping.

The step is particularly useful when the workflow needs to work with Business Object properties whose values are determined during process execution.

Typical Workflow Suggestions:

Update a Business Object with Dynamically Determined Data

Use the step when the values to be applied are determined during workflow execution.

Example:

Determine Customer Data → Set Dynamic Properties → Continue

For example:

CustomerType     = value determined by workflow
ProcessingStatus = current workflow status

Update After an Approval

Use Set Dynamic Properties after an approval activity to apply dynamically determined approval information.

Example:

Approval Task → Determine Values → Set Dynamic Properties → Notify

Potential properties include:

• Approval status.
• Approval date.
• Approver.
• Processing status.

Populate Properties from Form Data

Use form values as the source for dynamically populated Business Object properties.

Example:

Form Submission → Prepare Values → Set Dynamic Properties → Continue

Potential values include:

• Customer type.
• Request category.
• Priority.
• Status.
• Contact information.

Apply Calculated Values

Use the step after calculations have produced values that need to be applied to a Business Object.

Example:

Calculate Results → Set Dynamic Properties → Continue

For example:

CalculatedAmount → Business Object Amount

or:

CalculatedRisk → Business Object RiskLevel

Synchronize Workflow Data with a Business Object

Use Set Dynamic Properties to synchronize information generated during workflow execution with Business Object data.

Example:

Retrieve Data → Transform Data → Set Dynamic Properties → Continue

This pattern is useful when the values applied to the Business Object are produced or transformed during the workflow.

Update Different Property Sets

Use the dynamic property mapping when the workflow needs to apply property information determined by the processing context.

Example:

Determine Request Type → Set Dynamic Properties → Continue

For example:

Request Type = Customer

Properties to apply:
    CustomerCategory
    CustomerStatus

Request Type = Supplier

Properties to apply:
    SupplierCategory
    SupplierStatus

Update an Object After External Integration

Use the step after an external system returns information that needs to be applied to a Business Object.

Example:

External Integration → Process Response → Set Dynamic Properties → Continue

Potential values include:

• External status.
• Reference number.
• Processing result.
• External identifier.

Maintain Processing Information

Use dynamic properties to record information generated by workflow execution.

Example:

Process Record → Set Dynamic Properties → Continue

Potential information includes:

• Processing status.
• Processing date.
• Processing user.
• External reference.
• Workflow result.

Use with Decisions

Determine which values to apply before setting the Business Object properties.

Example:

Evaluate Request → Determine Properties → Set Dynamic Properties → Continue

For example:

If high priority:
    Priority = High

If normal priority:
    Priority = Normal

Update Before Sending a Notification

Use Set Dynamic Properties before notification activities when the Business Object needs to contain the latest workflow information.

Example:

Process Request → Set Dynamic Properties → Send Notification

This can help ensure that downstream processing uses the updated Business Object information.

Success and Failure Handling

Use the two return paths to distinguish successful dynamic property updates from unsuccessful execution.

Example:

Set Dynamic Properties → True → Continue Processing

** ↳ False → Log Failure / Retry / Notify Administrator**

The XML explicitly provides True and False return values.

To use this step, we need business objects configured in FlowWright Business Objects.

We must define the configured Business object in the Process Definition. On the process designer page, select Actions > Manage Business Objects > Add.

Example:

Let’s build and execute the “setBODynamicPropertiesDef” example.          

• Create a new definition named “setBODynamicPropertiesDef” and open it in designer mode.
• Drag a “setBODynamicProperties” step to the canvas. 
• Connect the dots between the Start and “setBODynamicProperties” steps, as shown above. 
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, additional values are available for configuration.
• Click the “setBODynamicProperties” step to configure its “Required” properties. Provide a name for the step and the name of the business object configured in the process definition. Click the button to set the business object’s values, then click Save. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the button to set the business object's values. Click the (+) Add Row button to insert an empty row. Enter the property name and value in the format “cDevBO.” The associated objects and methods are listed below. Click the Save button. You may add multiple property names by using the Add Row button. 

• Upon completion, the dynamic parameters for the business object are provided below for reference. 

• The “Logging” configuration is necessary for documentation and to measure workflow progress and percent complete. This is done by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. Render the process instance. When the workflow reaches the Set Dynamic Properties step, FlowWright uses the specified Business Object and configured dynamic property mappings to set the Business Object properties. The workflow then follows the True or False return path according to the execution result.

Tips:

• Verify the Business Object name before configuring the step.
• Ensure that the Business Object exists in the target FlowWright environment.
• Configure all required properties before executing the workflow.
• Confirm that the dynamic property mappings correspond to the intended Business Object.
• Use meaningful workflow Variable names when supplying dynamic values.
• Ensure that dynamic values have the appropriate format for their target properties.
• Test the workflow with representative Business Object data.
• Test each dynamic property mapping independently when troubleshooting.
• Verify the Business Object after execution to confirm that the expected properties were updated.
• Use the True path for successful processing.
• Use the False path for appropriate error handling.
• Log relevant Business Object and workflow information when troubleshooting.
• Test dynamic mappings after importing the Process Definition into another environment.
• Verify that the target environment contains the required Business Object configuration.
• Do not assume that Business Object configurations are identical across environments.
• Confirm that the dynamic properties expected by the workflow are available in the target environment.
• Test values generated at runtime rather than testing only static values.
• If dynamic properties depend on workflow decisions, test each decision path.
• If dynamic values come from external systems, test both valid and unexpected responses.
• Test behavior when the Business Object cannot be resolved.
• Test behavior when a dynamic property is invalid or unavailable.
• Test the False path rather than assuming the operation will always succeed.
• Avoid relying on undocumented runtime behavior for missing properties, invalid values, or other Business Object errors.

Notes:

• The Set Dynamic Properties step is defined in the Business Objects category with the internal name setbodynamicproperties, label “Set business object dynamic properties”, and display name “Set dynamic properties.”
• The step is implemented by FlowWright.Workflow.SetBODynamicProperties in FlowWright.Workflow.dll and is a Process step with 2 incoming connections and 2 outgoing connections.
• The XML defines two configurable properties, both of which are required.
• The two properties are:
  • boName – Name of the business object
  • boProps – Dynamic parms to the business object 
• The boName property uses the string data type, implemented by FlowWright.DataTypes.ClsTextBox.
• The boProps property uses the BoProps data type, implemented by FlowWright.DataTypes.BoProps, which is described as “Map business object properties.”
• The step provides two predefined return values: False and True.

Feature Comparison:

Both SetBOProperties and SetBODynamicProperties are FlowWright Business Objects process steps used to set properties on a business object. Their XML definitions are almost identical: both accept a business object name and a BoProps property mapping, and both provide True/False return paths. The primary distinction is the nature of the parameter set they pass to the business object: standard properties versus dynamic properties.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.

Note: Verify and complete any missing configuration after importing the sample, including:

• Business Object selection.
• Dynamic Business Object property mappings.
• Workflow Variable references.
• Environment-specific Business Object configuration.
• Downstream True and False workflow paths.

Verify that the Business Object and required dynamic properties are available in the target environment.

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.