Save to Parameter
| Description |
Allows to store Nimbus System Fields and Parameters and/or text into a Custom Parameter of your choice. You can extend this scenario further by including external systems via our Microsoft Power Automate Connector. Refer to our How to use the "Save to Parameter" workflow activity for an example and our Power Automate Use Cases further creative inspiration. |
||||||
| Required Predecessor | None. Relies on call Trigger Events to provide fields with actual content. | ||||||
| License |
|
||||||
| Modalities | Audio / Video | Instant Messaging | External Task | ||||
Common Properties
| Configurable Properties | Description |
|---|---|
| Parameter |
The Parameter of your choice to store a value in. 🔍 Availabiltiy of parameters in the selection depends on the Organization Unit of your current workflow. Note that parameters can have a default value that is overwritten once this activity is reached. |
| Value | A multiline textbox. Contents will be stored in your selected Parameter. TIPSYou can store a combined value of both Custom Parameters and/or System Fields and Parameters. To form complex validation chains you can combine "Save to Paramater" with previous data handling activities. For example:
KNOWN LIMITATION: The values stored in "Save to Parameter" are text-type only. Any relation to previous variables and parameter names to create this saved output is lost after exiting this activity. We are aware that having dynamic nested parameters in other activities would be very useful and are working to extend this functionality with future updates. |