Creating a Configuration Folder for Native Decisions Data Types
  • Updated on 25 Feb 2020
  • 1 minute to read
  • Print
  • Share
  • Dark
    Light

Creating a Configuration Folder for Native Decisions Data Types

  • Print
  • Share
  • Dark
    Light

Overview

In Decisions, configuration folders are used to house different things such as User Actions and Visibility Rules. These are automatically created when a datatype such as a Case Entity or a Flow Execution Extension is created, but how could someone modify attributes on native Decisions datatypes such as Accounts or the behavior of DefaultFolders? This is where the Configuration Extension comes into play.

A configuration extension lets a user create a configuration folder for an existing datatype. In the following examples, the Accounts group will gain an additional action.

These folders will affect ALL data that is of the selected datatype. For this reason, it’s important to keep these Configuration Extensions in a safe and memorable place. It’s recommended to create a folder to store these configuration extensions.

Example

This example will show how to create a Configuration Folder for a native Decisions Data Type (Account) and then create an action for that data type within that folder.

Please note that this method of adding a configuration folder is not strictly for Account data only! This is a method to hide elements or give actions to users for a multitude of native Decisions data.

Navigate to a Designer Folder. Select Create Datatype/Integrations and go to Configuration Extensions. This is where the two options are available: Add Entity Actions And Configuration and Add Folder Actions And Configuration.

Select Add Entity Actions and Configuration and then select 'Create'.

ENTITYANDFOLDERACTIONS.png

Type “Account” in the Type Name drop-down then select 'Save'. This creates an Account Configuration Extension folder.

2019-12-30_112539.PNG

Navigate into this Configuration Extension folder and it should be just as similar as any other datatypes configuration regarding creating actions. Select User Actions > Create User Action.

2019-12-30_112911.PNG

Name the User Action Flow and select 'Create'. This will be the name of the action available in reports, name this accordingly.

2019-12-30_113131.PNG

In this Flow, the entity information is accessible and visible in the Data Explorer. Configure this action to do whatever it may need to do, and make sure it’s working properly by using the Debugger. For example purposes, keep the flow simple by connecting the Start step to the End step. Its important to note any logic can be built in this flow to create an action for the data type.

2019-12-30_113251.PNG

To make sure this action is visible, create a report that references the Account Data Source and right-click an entity and see the New Native Action created from this process. Learn how to Create Your First Report.

2019-12-30_1136082.PNG

Was this article helpful?