Toolbox Customization With Element RulesLast Updated: 12/03/2015 Introduced in Verision: 2.0 |
There are some cases when Portal administrator in Decisions wants to customize Toolbox categories and elements in various Designers for different reasons. For such cases Toolbox Customization Rules were implemented in Decisions 3.2.0. By creating Rules for Toolbox it is possible to make visible only desirable elements in Toolbox.
Example:
In this example we will create a Toolbox Customization Element Rule for the Flow Designer to show only Data > Text category and only steps that contain “String” in their name.
We begin with navigating to System > Designers > Toolbox Customization > Element Rules Folder and clicking Add Toolbox Rule button on Folder Actions Panel.
In the pop-up window we Name our Rule and click Ok to save it.
The Rule is created. We navigate to the Rule’s thumbnail and click Edit.
In the Rule Designer we make sure that Enabled checkbox is checked in the Rule Settings. Then, we click Add New Rule Step button from the Start Rule window. Note: These Rules “Filter Out” Toolbox Elements. This means that all Toolbox elements that will be evaluated as True by this Rule will be invisible.
First, we need to define which Designer this Rule will be applied to. In the first Rule Phrase we pick type [ToolboxFilterType] and click Next.
In the Verb definition window we pick Is. Click Next to continue.
In the last Rule Phrase Builder window we leave Inputs Mapping Type Constant, and from the Value dropdown list we select Flow. Click Done when finished.
Next, we need to define which Toolbox Elements in the Flow Designer we want to Rule Out. Because our scenario in this example requires to rule out Categories and Steps in the Flow Designer Toolbox, we click Add Either/Or Group. With this group of Conditions we will be able to build separate conditions for Categories and Step Elements.
We navigate to the Either part of Group, click (Add) link and select Add Condition option.
Rule Phrase Builder opens and we pick isCategory field and click Next.
In the resulting Rule Phrase Builder window we select Is True and click Done.
We can close next Rule Phrase Builder window.
Then, we navigate to the or part of the Group and in the similar manner we Add Condition.
We pick isCategory field, click Next…
… define Is False and click Done.
Again, we can close Rule Phrase Builder window. Next, we are going to define which Categories to rule out in the Either group of conditions and which Step elements to rule out in the or group of conditions.
We navigate to the Either group and Add Condition.
In the Rule Phrase Builder we check Not checkbox for this Rule Phrase. In this way if the Category we define in this condition will be evaluated as True, it will be the only visible Category in the Toolbox. Then, we pick name [String] field and click Next.
In the Verb definition window we select Is and click Next to continue.
In the last Rule Phrase Builder window we configure Value Input with Constant Mapping Type and “Data” as its Value. We click Done when finished.
Because we want Text category to be visible too, we click Add New Step button for this Group.
We are going to build this Rule Phrase in the same manner we built previous condition. We check Not checkbox, pick name [String] field and click Next.
In the Verb definition we pick Is. Then, click Next.
In the last Rule Phrase Builder window we define Constant Value for the Input to this Rule Phrase as “Text”. Click Done to continue.
We are finished building Either group conditions and Close Rule Phrase Builder.
Next, we Add Condition to the or group of conditions.
Again, in the Rule Phrase Builder we check Not checkbox, pick name [String] field and click Next.
In the Verb definition we select Contains from Text Rules category. Click Next to continue.
Finally, in the Inputs configuration window we leave Case Insensitive checkbox checked, and configure Constant input with Value “string”. Then, we click Done.
Next, we can Close Rule Phrase Builder window.
Our Rule design is completed. It should look as following… We can save the Rule and close Rule Designer.
To test our Toolbox Rule we locate any Flow and edit it to open Flow Designer…
When Flow Designer opens, we can confirm that only Steps that contain “String” in the name and that are in Data > Text category are visible for the user as per our scenario design.
