open id 

joel@decisions.com

all messages by user

1/10/2019
Topic:
Using Input Data & Data Flows Internally in a Form

joel@decisions.com
joel@decisions.com
Administrator
Overview: This example illustrates how to take in data to a form while still updating that data from a flow kicked off inside the form. This project consists of a flow inputting accounts into a form, a form with a data grid, and a data flow in the form. This flow allows the addition of a new account and repopulates the data grid with the updated list of accounts.
Flow: The Accounts in Data Grid flow uses the Get All step to get all accounts and then inputs them into the data grid in the form from the Accounts input.

Form: The form has two user inputs, an event button, data grid, continue button, data flow, and input data that is specified in the form. The data grid is originally populated from the external flow. The user can input new account information and click the event button to start the data flow that inputs the name and email of the new account and adds it to the list of accounts. The continue button takes you out of the form and ends the flow.

Data Flow & Input Data: The Data Flows and Input Data sections can be found in the properties panel of the form under Form Rules and Form Data respectively.

Data Flow: The data flow takes in the New Account Name, New Account Email, and the Accounts list from the data grid. The flow adds the new account information as an item to the original list of accounts to create a new list and outputs that new list, which is used to repopulate the data grid in the form.

Input Data (IMPORTANT): If not specified data grid will only take in data flow output. By specifying the input data in the form, it allows the form to take in data from the external flow while still updating it by the output of the data flow. For this to work properly the Input Data section of the form, the Form Data Name of the Data Flow output, and the Data Name of the form component (data grid) you want to populate must be identical. In this example they are all named Accounts. The Form Data Name output for the data flow can be found by clicking edit on the data flow and edit on the output you want to use under Flow Outputs.


edited by joeln on 1/10/2019
edited by joeln on 1/10/2019
edited by joeln on 1/10/2019
1/18/2019
Topic:
Remove Flows With No Dependencies

joel@decisions.com
joel@decisions.com
Administrator
Overview: This example illustrates how to properly create a flow that removes flows with no dependencies. This project consists of an original folder, holding the flows, a new folder to move any flows with no dependencies, a rule identifying if the entity has dependencies, and a flow that executes this movement of entities.
Folders: The original folder represents the folder where a user would store flows. The new folder is the folder where any flows found without dependencies are moved to.

In order to first find the flows the folder ID’s must be determined. The folder ID’s can be found by right clicking on the folder, selecting manage, and then get designer folder ID. The ID below is the New Folder ID.





The ID can then be copied and used to specify what folder the entities will be moved to in the flow. This ID is entered into the folder Id section of the Move To Folder step seen below.



Rule: The rule used here takes in a list of dependencies and checks to see if the list is empty or not.



Flow: The original folder ID is identified as the flow is started. The entities inside the folder are retrieved and put into a list. By using the for each step each entity in the list has two lists made. One for all the dependencies it has and the other for the components it is a dependent of. The list of dependencies found are compared to see if there are any present for the entity. If there are no dependencies the entity is moved to the new folder and if there are dependencies the entity stays in its original folder.

edited by joeln on 1/18/2019
edited by joeln on 1/18/2019
edited by joeln on 1/18/2019
edited by joeln on 1/18/2019
1/18/2019
Topic:
Formatting an Email (Table)

joel@decisions.com
joel@decisions.com
Administrator
Overview: This example illustrates a way to create a custom email to send only selected data.

In this example a list of accounts is retrieved from the Fetch Entities step. CSS templates are created for the accounts data in the Custom Merge and Set Table Headers steps. These steps determine the format of the table rows to be created.
,
The Create New Table Row step merges previous CSS formatting with additional table formatting and accounts data.

Once the format is determined for each account in the table the final table format on the email is determined. Finally the send email step can be used by inputting the From, To, Subject, and Body of the email. In order to use the table in the body of the email select Merge HTML Text for body.

By selecting show editor it allows you to create an email that would send only selected data by selecting a data name in the left hand window of the editor. In this case MergedEmailTable, our custom table of accounts, is the data name we want to display which was output by the Merge Email Body Step. This would send an email with a body with our custom table of accounts.

edited by joeln on 1/18/2019
edited by joeln on 1/18/2019
1




Powered by Jitbit Forum 8.3.8.0 © 2006-2013 Jitbit Software