Check Parameter
| Description | Allows to check and react on system Fields and custom Parameters. | ||||||
| Required Predecessor | None - responds to parameters updated during Trigger Events. | ||||||
| License |
|
||||||
| Modalities | Audio / Video | Instant Messaging | External Task | ||||
Common Properties
| Configurable Properties | Description |
|---|---|
| Parameter Type | Offers a choice between:
|
| Custom Type |
🔍 Dependent on the "parameter type" selected:
|
| Name |
✅ Only shown when "parameter type" = Custom is selected. Allows you to define the a name used for the parameter. This name must match the dynamic value when using the Nimbus Power Automate Connector. |
Checks (Regex Validation)
Allows to define one or many Regular Expressions checks on the "parameter type / name" chosen above.
☝ Checks will be performed in your defined order. The first valid check will determine the activity exit. Any further matching expressions are ignored.
Regular Expressions cannot be empty. By default ".*" will allow anything as a parameter content = Parameter is present.
Parameter values are treated case-insensitive (ignoring capitalization) during validation and comparison for the “CheckParameter” workflow activity (e.g., "UserID", "userid", "USERid" are all treated the same).
| No Match | Taken when none of the provided Regular Expressions matches. |
| Not Set |
Taken when either criteria applies:
|
| Check 1.....n |
Check if the value of the parameter matches one of the Regex validations. 💡 By default 1 "Check 1" exit is defined and required. Up to 10 can be defined each with individual node exits.
The following criteria applies:
|
💡Tip: If you need to handle more parameters, You can also chain several "Check Parameter" activities.