Description:

The Set Item Detail Properties workflow step is an Engine step used to set detail properties on a selected FlowWright item.

The step supports:

• Specifying the ID of the item whose detail properties should be set.
• Selecting the item type.
• Mapping detail properties to the values to assign.
• Using workflow values when preparing the property mappings.
• Continuing workflow processing based on the operation result.
• Using True and False return paths for subsequent workflow processing.

Usage:

The Set Item Detail Properties step is typically placed after the workflow has identified the FlowWright item that needs its detail properties changed.

A typical workflow pattern is:

Identify Item → Prepare Detail Properties → Set Item Detail Properties → Continue Processing

For example:

Start
  ↓
Identify Item
  ↓
Prepare Property Values
  ↓
Set Item Detail Properties
  ↓
Continue Process

Typical Workflow Suggestions:

Set Detail Properties for a Selected Item

Use Set Item Detail Properties when a workflow needs to apply detail-property values to a selected item.

Example:

Identify Item
     ↓
Set Item Detail Properties
     ↓
Continue Process

Set Multiple Detail Properties

Use Detail properties to set when several detail properties need to be supplied during the same operation.

Example:

Prepare Values
     ↓
Set Item Detail Properties
     ↓
Continue Processing

Detail Property 1 → Value 1
Detail Property 2 → Value 2
Detail Property 3 → Value 3

Set Detail Properties After a Decision

Use the step after workflow logic determines that an item's detail properties need to be changed.

Example:

Evaluate Condition
       ↓
Update Required
       ↓
Set Item Detail Properties
       ↓
Continue Process

Set Detail Properties from Workflow Data

Use workflow data to construct the detail-property values before executing the step.

Example:

Get Workflow Data
       ↓
Prepare Property Values
       ↓
Set Item Detail Properties
       ↓
Continue

Use a Dynamic Item ID

Use a workflow-generated item ID when the target item is determined during process execution.

Example:

Identify Target Item
       ↓
Set Item Detail Properties
       ↓
Process Result

Example:

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

• Create a new definition named “clsSetDetailPropertiesDef” and open it in designer mode. 
• Drag a "clsSetDetailProperties" step to the canvas.
• Connect the dots between the “Start” step and the "clsSetDetailProperties" 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, you can configure additional values.
• Define a variable or a global to store the result after execution.
• Click the "clsSetDetailProperties" step to configure its "Required" properties. Provide a name for the step and the item GUID. Select the item type (task, user, process definition, process instance, form definition, form instance). Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the button to configure the detailed properties. A pop-up window appears for configuration. Click the Add Row (+) button to insert an empty row. Enter the column name (property name) from the “deUserDetails” table. Enter a variable or a global reference to store the result. Click the Save button. You may set multiple properties by using the Add Row button. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. Configure 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 and click the process step to inspect its properties and execution result. When the workflow reaches the Set Item Detail Properties step, verify that:
  • The intended item ID is supplied.
  • The correct item type is selected.
  • The intended detail properties are configured.
  • The expected property values are supplied.
  • The selected item's detail properties are updated as expected.
  • The workflow follows the appropriate True or False path.

Tips:

• Provide a valid Enter item ID value.
• Select the correct item type.
• Configure the required Detail properties to set mapping.
• Verify that the item ID corresponds to the selected item type.
• Review the available detail properties before configuring the mapping.
• Use meaningful property mappings so the intended changes are easy to identify.
• Use Variables or Globals for dynamic values where supported.
• Test the step with a known item before using it in production workflows.
• Test both the True and False workflow paths.
• Verify the selected item's detail properties after execution.
• Test each configured property individually when troubleshooting a complex mapping.
• Test the workflow after changing the item type.
• Test the workflow after changing the detail-property mappings.
• Keep environment-specific item identifiers configurable when appropriate.
• Avoid hard-coding identifiers when the target item can vary between environments or process instances.
• Use the False path for appropriate logging, notification, or exception handling.
• Document important detail-property mappings when they support business-critical workflow behavior.
• Verify that each supplied value is valid for the corresponding detail property.
• Test scenarios where the target item cannot be found or updated.
• Test scenarios containing multiple detail-property mappings.
• Keep sensitive values out of workflow logging where the detail properties contain confidential information.
• Do not assume that every property available for an item can be modified through this step.
• Do not assume that PropertyTypes exposes the same values for every FlowWright environment.
• Do not assume the exact validation, permission, or error behavior unless confirmed by the FlowWright implementation.
• Do not assume that a True result guarantees that every individual property mapping was applied in exactly the same way unless confirmed by runtime behavior.

Definition Sample:

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

Before executing the imported definition, verify:

• Enter item ID
• Select item type
• Detail properties to set
• Workflow Variable references
• The selected item type
• The target item ID
• The detail-property mappings
• Downstream True workflow path
• Downstream False workflow path
• Environment-specific item references

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

Click here to download the sample file.