As a Nimbus session gets transferred between multiple Services and Users, related System Fields and Parameters automatically carry over. In addition to this, a separate Setting allows to steer if additional Custom Context Parameters should be kept during a transfer from this Service to Users as well.
☝Note that the “Keep Custom Context Parameters on transfer” option is enabled by default for both Services (currently fixed) and Users (optional).
🔎 Custom Context Parameter Transfer Settings
The following Diagram is meant to illustrate the effects of context-related Service settings.
- Each Service can steer these settings individually. This means that Session Data storage and handover settings from a Service A are in effect until a new (receiving) Service B decides to handle the (received and potentially updated) data differently.
- Assuming your starting point is a Service A:
- Call Data & System Data will always transfer to Services and User.
- Custom Context Parameters will always transfer to Services.
- Custom Context Parameters will only transfer to Users if enabled on the originating Service. If toggled off, they will be nulled/reset to defaults.
-
The Nimbus Power Automate Connector can react to various Trigger Events (e.g. Workflow Started, Parameter Updated, Connected to User).
- By doing so, parameters within a specific scope (Service Session or User Session) can be updated, anonymized, or cleared.
- In the Sessions List this may result in different parameter values being shown for each interaction, as each session can have their context updated via separate Flow Actions.
