Overview When a Document is uploaded to the Decisions environment for use, it is typically referenced by the Document ID. The ID is used in configurations for other elements in the platform to reference the related item. An alternate method for providing access to a document in the Decisions environment is via Document URL. This article covers how to locate the Document URL and what occurs when the URL is reached. Example Right-click the name of the document in the environment. When the Action Menu appears, navigate to Other > Get Document URL . When the window appears, copy the document URL. Select DONE once the URL has been copied. Open a new tab or window and paste the URL, then navigate to it. This will keep the user on their current web page, but automatically initiate the document download in the browser download manager.

Overview Module Details Installation Location Core module Step Location  Integration > Azure Key Vault Prerequisites Admin users must configure an Environment Variable for " AzureServicesAuthConnectionString " at the System level. This configuration ensures seamless access to Azure services, including Azure Key Vault. Installation  of the Azure Services module Azure Key Vault is a cloud service that securely stores and manages sensitive information such as keys, secrets, and certificates. Integrating the application with Azure Key Vault  allows the retrieval of these sensitive data securely.  Available Steps Currently, there are two steps under the Azure Key Vault : Related Article: For more information on the following two Steps, refer to the Step Library article on Azure Key Vault . Sr. No. Step Name Description 1 Get Secret Value The "Get Secret Value" step retrieves a secret value from Azure Key Vault. Secrets stored in Azure Key Vault can include connection strings, API keys, or any other sensitive

Overview Users can use the Create  Type  From  Data  feature to recreate or track data from a specific Flow. The Create Type From Data is a feature found in the Data  Definitions  window that compiles the configured Data Definitions and converts them into a singular Defined Data Structure.  Example The following example will demonstrate how to create a Flow Structure data type called "Company" based on pre-existing String data. In a Designer Project   and select CREATE FLOW from the top Action bar. Select Flow , provide a Name, then click CREATE. Click SETUP INPUT DATA, then click DEFINE. Under NAME, enter "EmployeeName" as a String [Text] . Click the pencil icon and enter "Sam Thomson" as a Constant mapping. Enter "EmployeeEmail" under NAME as a String [Text] and Constant map in "example@company.com". Click Save  and close the window. Attach a Create Data step to the Show Form step and

Overview When initially creating a Simple Flow , the Run Rule and Branch Process steps will be available for use.  Functioning similar to their flow step counterparts, these steps can be used to create branching paths in a Flow, allowing for different steps to be executed based on what path the Flow takes. These steps can be found under Flow Control  in the Quick Add Gallery panel. Run Rule The Run Rule step allows Designers to create Statement Rules to be used in the Flow. Selecting Edit SimpleRule will open the Rule Designer , where the inputs and outputs, along with the statement can be defined. Settings Properties Description MergeOutputs Merges the True and False outcome paths into one path. This option is only available if the Run Rule step is the end step for a path Edit SimpleRule Opens the Rule Designer to modify the Rule results in a Flow. Branch

Overview The following article demonstrates how to set up an Azure Kubernetes Service (AKS) cluster in an Azure Cloud. For more information, refer to About Clustering . Prerequisites An active Azure Account . A Database Server. Refer to the installation requirements to know the supported Databases. If using an Azure Database Server, navigate to Security > Networking and enable Allow Azure services and resources to access this server . This action will allow the Kubernetes pods to access the DBs inside the DB server. Refer to the following image. An Azure storage account. Refer to Create a storage account . While creating a new Azure storage account, ensure Performance is set to Premiu m and the Premium account type is set to File Shares; refer to the following image. Create a File share under this Azure storage account. This file share will be used to maintain the persistent storage of the container. Further in

Annotation Step Name Modified in Version Toolbox Location Annotation Shapes --- Annotation Placeholder Step 7.1.0 Annotation Root Annotation Steps --- Annotation Communication Step Name Modified in Version Toolbox Location Send Email 7.2.0 Communication > Email Send Email to Contact Steps 7.2.0 Communication > Email Send Email with Custom Server 7.2.0 Communication > Email Send Notification Step 7.1.0 Communication > Notifications Send Notification To Accounts and Groups 3.2.0 Communication > Notifications Send Notification With Files Step 7.1.0 Communication > Notifications Send Notification With Url Step 7.1.0 Communication > Notifications Send SMS To Contact 7.2.0 Communication > Notifications Show Popup 7.2.0 Communication > Notifications Dashboard Management Step Name Modified in Version Toolbox Location Are Events Being Broadcast Step 7.2.0 Dashboard Management > Events Create Tile Data 4.0.0 Dashboard Management Create Tile Return 4.0.0 Dashboard Management Get Page Variable

the Flow. From the Previous Flow's Flow Designer, Edit Input Mappings for the Run Flows For List step and connect the list of Contacts from the Get All Contacts step to the Input List of the Run Flows For List step.  At this point, the Output from the Run Flows For List step is a list of entities in an easy-to-use form, ready for additional processing. Handling Large Output By default HubSpot only returns 100 Companies and 20 Contacts when asked for Lists of those items. If more than that number is required, then any objects past that limit will NOT  appear in the Output of the HubSpot Module steps.  There are two Properties on those steps which can help manage in retrieving large amounts of data. The Count Property The Count property establishes the number of results that HubSpot will return. In the previous examples, setting

Overview Decisions installations can be done using the command line. This allows for silent automated installations.  Please Note: A secondary database connection CANNOT be set up for silent installations.  A secondary database MUST be set up AFTER a silent installation by editing the settings.xml file. Please navigate to the Setting a Fail-over Connection String article for more details on setting up the secondary database after the silent installation. Version 7.x .NET Architecture Change: Versions 7.0.1 - 7.1 require .NET Core 3.1 Versions 7.2 - 7.9 require .NET 5 Versions 7.10+ require .NET 6 Impact on Upgrades:  ALL custom libraries will need to be recompiled for the new .NET architecture. Custom assemblies will need to be re-written. Modules may require reinstallation or design refactoring. Example Before performing a silent installation create an InstallerSetup.xml file. This is done using the DecisionsInstaller

Overview Decisions Cannot Analyze Every CSS Framework! While Decisions UI possesses its own HTML structure, incompatibility issues tend to occur with CSS frameworks that demand a specific HTML structure, such as Bootstrap. The majority of opinionated CSS frameworks are incompatible with Decisions UI; however, atomic CSS frameworks are easier to apply in Forms and Pages. In addition, CSS frameworks implementing CSS resets or styles to native HTML tabs may also affect the entire Decisions Portal, so p lease proceed with caution. Users may upload their custom CSS documents for customization of elements in Decisions to easily fit the branding and image of any company or enterprise.  CSS in Decisions is implemented by using a CSS document and manually mapping the custom-defined classes to each Form component or a CSS document with Decisions' predefined classes for automatic mapping to their respective Form components. To apply a custom CSS file, navigate

Overview Module Details Core or Github Module Core Restart Required  No Step Location  Toolbox > Docker Steps Settings Location  System > Designers > Data Structures > Decisions > Docker Prerequisites N/A The  Docker Module is an application that allows users to implement certain Rules and Flows to run in managed containers. The Docker Module is currently considered restricted use, and users will be required to contact   support@decisions.com in order to enable the Module.  Configuration/Properties Both the  Docker Settings and the Docker Folder Data  can be found by navigating to System > Designers > Data Structures > Decisions > Docker. From this page, users have the options to either ADD NEW SUBFOLDER or REGISTER.NET DATATYPE from the Action Bar at the top of the page. Available Steps Once the Docker Module is installed, there will be an additional step that becomes visible in the Flow Designer Toolbox. This step can be found by navigating to

Overview The validation Rule ensures the data integrity for the objects created within Data Structure. Objects in Data Structure can be created via Folder Actions, Forms, Flows, Page, Dashboards, etc. Validation Rule uses Flows  and Rules to trigger custom Validations. Purpose of Validation Rule Decisions have various methods to validate the data directly at the source (refer to Validations Overview ), But when the data comes from any external source, has not interacted with any user, and has not been validated at the source, Validation Rules can be used to validate the data before saving the data in the Data Structures. Actions to create Validation Rules can be found on the top Actions bar of a Configuration Folder. Note: Validation Rules can only be created on the Configuration Folder with the following Data Structure, Database Structure   Database Structure Leased Entity External Entity Folder Extension Case Entity Defined Data Structure . Types of

Users with the necessary permissions may edit a Designer Folder to customize the appearance in the Folder Tree. Customizing Folder Appearance Using the Context Menu Right-click on a Designer Folder in the Folder Tree to open the Context Menu.  Selecting the Add as Favorite action pins this folder to the Favorites   section of the sidebar for quick access to its contents. This is especially useful for designer folders containing a dashboard. To change how the Folder looks outside the Favorites menu , utilize the other bulleted actions with settings that, while named the same, affect how the Folder looks in the Folders menu instead. The following configurations are available upon selecting this action: Setting Name Default Value Function Name The current name of the Designer Folder This prompts for the name of the Designer Folder in the Favorites menu. It does not change the name of the Designer Folder

Note: Changing the Name or Type of a data field can significantly impact the data structure. It is necessary to have a backup of the data before making such changes. Overview A Data Structure represents real or abstract objects through data fields, which are basic units of information that are variables of the represented object. An example is a Data Structure called Person with data fields such as HairColor , ShoeSize , and DateofBirth . The data fields and their types can be edited after initially creating the Data Structure. This article demonstrates the outcome of changing the Name or Type of a data field.   Default Text Length The default setting for all text stored in the database is 255 characters. However, creating a Data Structure can modify this using the Text Length setting. Data Field Name Changes Data Field Naming Rules Data Types cannot have some special characters and database-reserved

Overview A Form can be auto-generated to include fields from a Data Structure. This quickens build time while ensuring no missing data fields during data submission. Example In the Designer Project, click CREATE DATATYPES/INTEGRATION   and select  Flow Structure. In the Flow Structure window, enter a name in the Structure Type Name field and create two String [Text] data fields (FirstName, LastName) and one Int32 (Number) data field (Age). Click SAVE. Right-click on the Flow Structure and click Generate Form . In the Create Form window, select GridLabelLeft  under Layout Style . For the Cancel Outcome Name field, enter "Cancel". Click GENERATE FORM. In the Designer Project, click CREATE FLOW to create a new Flow .  Attach a Show Form step to the Start  step. On the Properties panel, click PICK OR CREATE FORM and pick the existing Form that was created "PersonStructureForForm Form". With the step selected, click Unknown  next

Overview This article provides the CSS class code templates for 21 different Form controls.  These CSS classes can be uploaded and then applied onto Form controls .  Expand each accordion box below to view the a copy-able CSS template. Within the /* */ markings of the code are bits of plain text that provide configuration information. Label Change border width by 1px and color to green, curve corner border by 10px, padding to increase space inside label, background color to white, text color to blue, font family to Times New Roman, text size to 14px, align text in the center. CSS Class Template .MyLabel { border: 1px solid green; Border-radius: 10px; padding: 5px 10px 5px 10px; Background : white; color: blue; font-family: times new roman; font-size: 14px; text-align: center; } /* OR */ .form-surface-view .silverLabel { border: 1px solid green; Border-radius: 10px; padding: 5px 10px 5px 10px; background: White; color: blue

Overview The Mapping  step lets users map data from one object into another. For example, if a Flow contains empty objects and a user wants to populate attributes to those objects, the Mapping step could be used. The Mapping step is best used when affecting multiple objects or multiple attributes of an object. Example In a Project, click CREATE FLOW   and create a new Flow .  Click SETUP INPUT DATA and click DEFINE . Enter "File" under NAME and select File Data from the TYPE dropdown menu. Click Save  and close the window. Attach a Create Data step from the T oolbox  panel under the FAVORITE STEPS category to the Done  path of the Start  step. On the Properties  panel, click SHOW EDITOR. In the Data to Create window, enter "NewFileName" under NAME and leave the TYPE as String [Text] . Define the Value if Null as "UPDATEDFileName". Click Save and close the

Module Details Installation Location Core module Step Location  Integration > AdobeSign Prerequisites Adobe Sign Application Installation  of the AdobeSign module Project dependency created Overview Adobe Sign is an electronic signature service provided by Adobe Systems . The Adobe Sign Module introduces Flow steps that allow users to create agreements, download signed documents, and retrieve agreement status. These steps use API integration, enabling seamless communication between Adobe Sign and other systems or applications, streamlining the electronic signature process. This integration ensures users can manage agreements, track progress, and access signed documents without manual intervention, saving time and enhancing workflow efficiency. Configuration Add and configure Adobe Application Creating an Adobe application is necessary to obtain API credentials (such as Client ID and Client Secret) that allow the application to authenticate and interact with Adobe Sign services using APIs securely. Navigate to   API > Acrobat Sign API > API Application and create a new application using the

Overview  As of v.8.2 , Multi-Tenancies now support the ability to integrate Active Directory , as well as its capability to manage domains, Accounts , objects, etc, within their environments. By doing so, AD Syncs can be performed first on the Control Instance , and then its subsequent Tenants . Prerequisites The Active Directory Module must be installed on both the Control  and Tenant  Instances .  Setup  After the Active Directory Module has been installed on both the Control  and Tenant  Instances , from the Control Instance, navigate to  System > Settings, and open Active Directory Settings .  In the resulting window, under Servers , click ADD. Under  PORTAL SETTINGS > Default Groups , click ADD NEW and select the desired Default Group ; this selection designates which Group the synced Accounts will be added to.  Under SERVER SETTINGS, configure the settings as follows: Setting  Configuration Domain Name Provide the Domain or IP Address for the AD Server.  Domain Login

Overview A Disaster Recovery ( DR ) Server  is typically a duplicate of the primary server in a different location. In the case of a "disaster" event on the Primary Server , the DR Architecture ensures that the Decisions Server maintains uptime and that the data is protected. Primary vs. Disaster Recovery Database Connections Primary Database Connection The Primary Connection String from the installation will be the Database Connection used for the main server. Disaster Recovery / Secondary Connection The Secondary Connection String operates as a Failover  Connection  if the Primary Connection String fails.  Configure Decisions as a Disaster Recovery server To configure Decisions as a DR Server , at least two Decisions Installations will be needed. One of the installations is kept offline but references an MSSQL Database with Always-On Replication set for the Production Server . The Connection String applied to the Decisions Installer needs to reference the replicated database in the Disaster

Overview Module Details Core or Github Module Core Restart Required  No Steps Exposed None Settings Location  System > Administration > Features > Decisions.UnitTestCore Prerequisites N/A The UnitTestCore Module is a Decisions Module that is used for testing custom code or SDK Extensions. This Module is not necessary for Flow and/or Rule unit testing, as that feature is automatically built into the Decisions platform. The UnitTestCore Module is only used for Developers using SDK Extensions.   Configuration/Properties The UnitTestCore Module Settings can be found by navigating to System > Administration > Features > Decisions.UnitTestCore.  By right clicking on UnitTestInfrastructureService,  users can adjust settings for the UnitTestCore Module.  For further information on Modules, visit the Decisions Forum .