Using Dynamic Fields in Workflows



Dynamic Fields make it possible to target unique values from across your domain's Connectors, and use them to personalize and scale the actions you take in BetterCloud. This functionality can both broaden the scope of automated workflows and make their results more granular, increasing productivity and efficiency, and making targeted customizations easier to achieve. 

Dynamic Fields in The Workflows Builder

When building a new Workflow, IF conditions and THEN actions must have their properties defined, in order to scope the parameters of your Workflow's purview and define how it will react when a triggering WHEN event is detected.

However, Dynamic Fields can now be used to define the properties of your conditions and actions, making the possible parameters of the Workflow far more broad across data from all of your Connectors. At the same time, Dynamic Fields will also help customize the actions taken by your Workflow, based on the unique qualities of each entity that passes through it.

Workflow definitions can be found in the "Properties" pane of the Workflows Builder, and fields that can accept Dynamic Field entries will be marked with the "{{" Dynamic Field icon. Dynamic Field entries that are applicable to add will be available to select from a dropdown menu, after clicking on this icon. 

Using a Dynamic Field entry in your workflow build will scope the context of the condition or action in which you use it, but neither the amount of time needed for a workflow session to complete, nor the way that the workflow result is recorded in the BetterCloud Audit Logs will be affected by the usage of Dynamic Field entries. 

You can find complete instructions for creating a workflow here:

How to Create a Workflow

Use Cases

Here is an example use case template, in which Dynamic Fields can help you further customize and scope your Workflows:

My organization utilizes multiple Connectors. When I offboard users, I want to ensure that their data is transferred the appropriate manager, and that their accounts are securely disabled. 

For more use cases and Workflow templates, please see here: Workflow Templates

Important / Requirements

Please note the following details about the behavior of Dynamic Fields: 

  • In order to ensure compatibility with all actions in BetterCloud, "Copy User" actions that were previously available have been deprecated. These actions were intended to copy new or existing user accounts from one enabled Connector into another, but would not support Dynamic Field entries. Instead, these actions will be replaced with new "Create User" actions, allowing for the same functionality will including Dynamic Fields. 
    If you have an existing active workflow that includes a "Copy User" action, your workflow will continue to trigger and execute as expected. However, you will not be able to make edits to any other parts of your workflow until this action is removed; therefore, we recommend removing this action from your workflow as soon as possible. Please contact Support if you have any questions. 
  • Please ensure that the syntax of a Dynamic Field entry remains intact and unaltered, within its {{  }} brackets. If the syntax of a Dynamic Field entry is changed, or if any brackets are removed, the entry will either be nullified in the context of your action, or will be converted to plain text and inserted as-is into your field. 
  • If the content being pulled to fill your Dynamic Field entry does not exist yet (for example, if you utilize the {{target.Google.Gsuite.User.Manager}} entry, but the user's "Manager" profile field does not yet contain an entry) an "undefined" entry will be added, instead. 
  • The "Properties" pane now includes a "<<" icon, which can be used to expand or contract the pane, to allow for more comfortable entries into fields.

More Information

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request