Description:

The Set Item Properties step accepts an item ID, item type, and a mapping of properties and values to apply to the selected item. It provides True and False return paths for subsequent workflow processing.

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

The step supports:

• Specifying the ID of the item whose properties to change.
• Selecting the item type being updated.
• Mapping properties to the values to assign.
• Updating properties on supported FlowWright item types.
• Using the result to control subsequent workflow processing.
• Continuing through the True or False return path.

Usage:

The Set Item Properties step typically comes after a workflow identifies the FlowWright item that needs updating.

The workflow supplies:

1. The item ID.
2. The item type.
3. The properties and values to apply.

A typical workflow pattern is:

Identify Item → Set Item Properties → Continue Processing

For example:

Start
  ↓
Identify Item
  ↓
Set Item Properties
  ↓ True
Continue Process

The step can be useful when workflow execution needs to modify configuration or metadata associated with a supported FlowWright item rather than simply processing workflow data.

Typical Workflow Suggestions:

Update Task Properties

Use Set Item Properties when a workflow needs to change properties associated with a selected Task.

Example:

Identify Task
     ↓
Set Item Properties
     ↓
Continue Task Processing

Item ID:
[Task ID]

Item Type:
Task

Properties to set:
[Task property mappings]

Update User Properties

Use the step to set properties associated with a selected User.

Example:

Identify User
     ↓
Set Item Properties
     ↓
Continue User Processing

Item ID:
[User ID]

Item Type:
User

Properties to set:
[User property mappings]

Update Process Properties

Use Set Item Properties when workflow logic needs to update properties associated with a selected Process.

Example:

Identify Process
      ↓
Set Item Properties
      ↓
Continue Processing

Update Form Properties

Use the step to set properties associated with a selected Form.

Example:

Identify Form
     ↓
Set Item Properties
     ↓
Continue Form Processing

The XML explicitly identifies Form as one of the item categories referenced by the step.

Set Multiple Properties

Use Properties to set when several properties need to be updated as part of one operation.

Example:

Prepare Values
      ↓
Set Item Properties
      ↓
Continue Process

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

Set Properties After a Decision

Use Set Item Properties after a decision determines that an item needs to be changed.

Example:

Evaluate Condition
       ↓
Condition Requires Update
       ↓
Set Item Properties
       ↓
Continue Process

Update an Item After Form Submission

Use the step after collecting information from a workflow form.

Example:

Form Submission
      ↓
Validate Values
      ↓
Set Item Properties
      ↓
Continue Process

Update an Item Based on Workflow Data

Use Set Item Properties after workflow processing has determined the values that should be applied.

Example:

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

Use Dynamic Item IDs

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

Example:

Identify Target Item
       ↓
Set Item Properties
       ↓
Process Result

The exact mechanism used to resolve workflow Variables or Globals into the property should be verified in the FlowWright runtime.

Update Different Item Types in Different Workflow Paths

Use workflow decisions to select different property-update operations.

Example:

Determine Item Type
       ↓
   ┌───┴────┐
  Task    User
   ↓        ↓
Set Item  Set Item
Properties Properties

Set Properties After an Approval

Use Set Item Properties after an approval decision when additional item properties need to be updated.

Example:

Approval
   ↓
Approved
   ↓
Set Item Properties
   ↓
Continue

Handle Property Update Failure

Use the False return path to handle cases where the property-setting operation does not succeed.

Example:

Set Item Properties
      ↙       ↘
   True       False
     ↓           ↓
Continue      Log / Notify
Process       / Handle Error

Log the Property Update Result

Use a downstream activity to record the outcome of the property-setting operation.

Example:

Set Item Properties
       ↓
    True
       ↓
Log Update Result

Example:

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

• Create a new process definition called “clsSetPropertiesDef” and open the definition in designer mode. 
• Drag a “getWorkflowUserID, clsSetProperties, clsGetProperties” step to the canvas.
• Connect the dots between the “Start” and other 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.
• Click the “getWorkflowUserID” step to configure its “Required” properties. Provide a name for the step. Enter the user name to fetch. Specify a variable or a global reference to store the user ID. Click the Save button. Note: Click the "AI Predict" button for Copilot to add new process steps that match your process description. 

• Click the “clsSetProperties” step to configure its “Required” properties. Provide a name for the step. Select the item type (User, Task, Process, Form) from the dropdown list. Provide the variable or global reference that contains the appropriate GUID value. Click the “Properties to set” button to open the configuration window. Click the Add Row button to insert an empty row. Enter the property name and value. Click the Save button. You may set multiple properties by using the Add Row button.  

• Click the “clsGetProperties” step to configure its “Required” properties. Provide a name for the step. Select the item type (User, Task, Process, Form) from the dropdown list. Provide the variable or global reference that contains the appropriate GUID value. Click the “Properties to get” button to open the configuration window. Click the Add Row button to insert an empty row. Enter the property name. Click the Save button. You can retrieve multiple property values 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 view its properties. When the workflow reaches the Set Item Properties step, verify that:
  • The intended item ID is supplied.
  • The correct item type is selected.
  • The intended properties are configured.
  • The expected property values are supplied.
  • The selected item's 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 before configuring the properties.
• Configure all required properties before executing the step.
• Verify that the item ID belongs to the selected item type.
• Use meaningful property mappings so the intended changes are easy to understand.
• Review the available properties for the selected item type before configuring Properties to set.
• Test the step with a known item before using it in production workflows.
• Test both the True and False workflow paths.
• Verify the target item's properties after execution.
• Use workflow Variables or Globals for dynamic values where supported by the FlowWright configuration.
• Keep environment-specific item identifiers configurable when workflows are deployed across environments.
• Avoid hard-coding item IDs when the target item changes between environments or process instances.
• Test the workflow after changing the selected item type.
• Test the workflow after changing property mappings.
• Verify that each configured property accepts the supplied value.
• Use the False path for appropriate error handling, logging, or notification.
• When setting multiple properties, verify each property individually during testing.
• Avoid changing unrelated properties in the same operation.
• Document important property mappings when they are part of a business-critical workflow.
• Test scenarios where the target item cannot be found or updated.
• Do not assume that every property is available for every item type.
• Do not assume the exact validation, permission, or error behavior of individual item properties unless confirmed by the FlowWright implementation.
• Do not assume that a successful True result means every requested property was changed in exactly the same way unless confirmed by runtime behavior.

Definition Sample:

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

Before executing the imported definition, verify:

• Enter item ID
• Select item type
• Properties to set
• Workflow Variable references
• The selected item type
• The target item ID
• The property/value 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.