Contents x
Flows Step Glossary
  • 14 Dec 2021
  • 2 Minutes to read
  • Print
  • Dark
    Light
Contents
  This documentation version is deprecated, please click here for the latest version.

Flows Step Glossary

  • Updated on 14 Dec 2021
  • 2 Minutes to read
  • Print
  • Dark
    Light
Article summary

Overview 

The following article details all steps found in the Flows category in the Step Toolbox.


Step NameDescriptionLocation Inputs/Outputs
[Pick or Create Flow]

Also referred to as a subflow or linked Flow. This step allows a user to define a child Flow to be initiated when it reaches it in the parent Flow and it will wait for the child Flow to complete before moving forward in the parent Flow. It separates the business logic so it can easily be reused and/or permissioned to different users.


Designer Entities > Flows		Inputs:
Run Flow Async and Wait (Boolean)

Outputs:
None
Run Flows For List

The Run Flows For List step is a Batch Processing step that processes a mapped in Input List, and Outputs it in the desired Output Data Type (Output Type), using individual external Processing Flow instances for each Item in the List. Moreover, with this step, a designer is able to pick Run Behavior: Synchronous, Thread Job, Thread Job Async or Work Queue. This is a huge advantage for processing large sets of Data.


Flow Management > Iteration		Inputs:
Input List (List of DATATYPE [System]), Remove Null Results (Boolean [System])

Outputs: Result List (List of DATATYPE [System])
Send Report

This step operates as a subflow that sends a report to the listed email. The subflow requires the recipient's email, as well as the Report Id.


Designer Entities > Flows		Inputs:
EmailTo (String), Report Id (String).

Outputs:
"Sent"
Email Is Not ExistDetermines whether or not an email exists by detecting if the email is Null or not.
Flows > Wizards		Inputs:
Email (String)

Outputs:
Is Not Exists (Boolean)
Convert String To Date

Converts a listed String, such as July 31, into a proper date, such as 2021-07-31. The conversion defaults to the current year, even if the appointed date has already passed.


Designer Entities > Flows		Inputs:
String To Convert (String)

Outputs:
Converted Date (DateTime)
Total Results NumberRuns a subflow that pulls the Folder Id provided to determine the number of results listed.
Flows > System Defaults > Rule Set		Inputs:
None

Outputs:
Tile Data (TileReturn)
Is Number MatchDetermines if a password matches. To do this, the subflow runs the password through a Rule that checks if it matches.
Flows > Wizards		Inputs:
Password (String)

Outputs:
Is Match (Boolean)
Assign Approval Form Flow

Determines if the expiration date is Null, and if so, assigns an approval Form for the task. If the expiration date is not Null, then the subflow assigns an approval Form with with an expiration date that can either be accepted, rejected, or set to expired.


Designer Entities > Flows		Inputs:
All Approvals for Level Deadline (DateTime), Approval Request (ApprovalRequest), Require Comments On Approve (Boolean), Require Comments On Reject (Boolean).

Outputs:
None
Is Item In Module

Runs a subflow that takes the input Entity Id and determines if the item shows up in the named module. The subflow returns a True/False value.


Flows > System Defaults > Export Wizard		Inputs:
Entity Id (String), Module Name (String).

Outputs:
In Module (Boolean)
Export CSV Entities

Subflow that grabs entity names and then compiles them so they can be downloaded. The fields are then validated and checked for warnings. If any warnings appear, then a separate Form is opened allowing a user to edit the fields and redownload the entities. After this, a user is prompted to finish exporting the file in a separate Form.



Database		Inputs:
Type Name (String)

Outputs:
None
Was this article helpful?
What's Next
Decisions
Resources
Organization
Connect