This guide is covering the following:β
Retrieving security details dynamically
β Extracting specific user attributes
β Fetching configuration parameters
β Extracting specific user attributes
β Fetching configuration parameters
Extracting security details
Security details (securityDetails
) store user-related data, including email, username, roles, and permissions. These values are stored in additionalData.securityDetails
and can be accessed dynamically within a process.
Retrieve security details
Use the following business rule to fetch and store security details:

Extract specific owner details
To retrieve specific attributes, such as email, username, first name, and last name, use one of the following scripts (JS or Python):- Owner Email (
securityDetails.Default.owner.details.email
) - Username (
securityDetails.Default.owner.username
) - First Name (
securityDetails.Default.owner.details.firstName
) - Last Name (
securityDetails.Default.owner.details.lastName
)

Dynamic extraction by swimlane
If your application uses multiple swimlanes, retrieve the owner details dynamically:Extracting values from configuration parameters
To make business rules flexible, store configuration values in project configuration parameters instead of hardcoding them.
Retrieve configuration parameters
Use a business rule to fetch and store configuration parameter values dynamically:Example use case: commission calculation
This example shows how to calculate a commission value dynamically using a configuration parameter.
Configuration parameters
Parameter Name | Description | Example Value |
---|---|---|
commissionPercentage | The percentage used to calculate the commission | 0.05 (5%) |
Configuration parameters can be modified in:β‘ FlowX.AI Designer β Your Project β Configuration Parameters
Process flow
1
User Inputs an Amount
In a User task we have an input UI element where the user provides an amount (
userInputAmount
).
2
Retrieve Commission Percentage from Configuration
In the next node, a Service Task fetches the
Business rule used:
commissionPercentage
from the configuration parameters.
3
Calculate Commission
Formula used to calculate the commission:
4
Store and Output the Result
The computed 
commissionValue
is stored for further processing.Final result:
Why Use Configuration Parameters?β
Keep business rules flexible by avoiding hardcoded values.
β Adapt calculations dynamically based on environment settings.
β Simplify updates by modifying values in the project configuration rather than editing business rules.
β Adapt calculations dynamically based on environment settings.
β Simplify updates by modifying values in the project configuration rather than editing business rules.