Description:

This step updates FlowWright configuration settings.

The Set Configuration Settings workflow step allows a workflow to modify application configuration values by specifying either a single configuration key/value pair or multiple configuration settings in a single operation. These settings are written to the FlowWright configuration repository, allowing administrators and workflows to dynamically adjust system behavior without manual intervention.

This step provides an efficient way to automate application configuration changes during deployment, administration, environment initialization, feature enablement, maintenance, or business process automation.

The step supports:

• Updating a single configuration value
• Updating multiple configuration values
• Dynamic configuration using workflow variables
• Batch configuration updates
• Integration with the FlowWright system administration
• Runtime configuration management

This step can be used for:

• Environment configuration
• Application initialization
• Feature management
• Administrative automation
• System maintenance
• Deployment workflows
• Business process automation

Usage:

The Set Configuration Settings step is typically placed within administrative workflows, deployment processes, system initialization routines, or maintenance workflows that need to automatically update application configuration values.

The workflow updates the specified configuration settings and makes the new values available for subsequent workflow execution and application behavior.

A typical workflow might look like this:

Once the configuration settings have been updated, later workflow steps can:

• Restart dependent services
• Notify administrators
• Execute configuration validation
• Generate audit reports
• Continue deployment workflows
• Initialize application components

Configuration keys should already exist in the FlowWright environment unless the deployment supports new configuration entries.

Example:

You must navigate to the Status > Settings > Settings Designer page. The UI is displayed below. FlowWright application keys and values are listed here. You may select a line item and right-click it to modify the value. Note: System keys and values should be changed with due diligence. 

Let’s build and execute the “setConfigurationValuesDef” example to change one of the system keys and values. 

• Create a new process definition named “setConfigurationValuesDef” and open it in designer mode. 
• Drag a “setConfigurationValues” step to the canvas. 
• Connect the dots between the “Start” step and the “setConfigurationValues” step, as shown above. 
• Click the “setConfigurationValues” step to configure its “Required” properties. Provide a name for the step. Click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description. 

• Click the “setConfigurationValues” step to configure its “Optional” properties. Enter the configuration key and values as shown below. Click the button to add multiple key-value pairs. Click the Save button.    

• Click the button to enter multiple key-value pairs. A pop-up window appears for configuration. Click the Add Row (+) button to insert an empty row. Enter the “config key and value”. Click the Save button. You can add multiple configuration key-value pairs using the Add Row button. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved 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 Process Instance and execute it. When the workflow reaches the Set Configuration Settings step, FlowWright updates the specified configuration key/value pair or processes the configured list of multiple configuration settings. If the operation completes successfully, the workflow follows the True return path. If one or more configuration settings cannot be updated because of invalid keys, insufficient permissions, or internal processing errors, the workflow follows the False return path. Click the process step to view its properties. The step should successfully update the configured FlowWright settings and return True upon completion.

• The system key value has been changed as follows. 

• Navigate to Status > Log > System Log > Audit Log. The change event is recorded here for auditing. 

Tips:

• Use Multiple Config Settings when several related configuration values need to be updated together.
• Use workflow variables to dynamically assign configuration values during execution.
• Verify configuration key names before deployment to prevent updating unintended settings.
• Consider executing this step during maintenance windows if configuration changes affect active users.
• Audit configuration changes as part of administrative workflows.
• Test configuration updates in a non-production environment before deploying them to production.
• Use the True and False return paths to implement appropriate success and exception handling.
• Combine this step with Get Configuration Settings, Restart Service, Send Email, Create Audit Record, or Conditional Routing workflow steps to automate configuration management workflows.

Notes:

• Configuration updates affect the FlowWright environment according to the configured keys.
• Either a single configuration key/value pair or multiple configuration settings can be specified.
• Workflow variables may be used for both configuration keys and values.
• Invalid configuration keys or insufficient administrative permissions may cause the step to return False.
• Some configuration changes may require service or application restarts before taking effect.
• This step updates the system configuration but does not validate the functional impact of the new values.
• The workflow should include appropriate handling for both True and False return paths.
• Administrative workflows that modify configuration settings should follow your organization's change management and governance policies.

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 page.

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

• Configuration key names
• Configuration values
• Multiple configuration mappings
• Workflow variable definitions
• Administrative permissions
• Environment-specific settings

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

Click here to download the sample file.