Flows
30 Minutes - Add New Calendar record based on Location
This flow monitors Contacts with the Digital Contact client type who have an associated Location record.
It triggers when a contact’s Country, State, or City field has been updated today or yesterday, and when the contact has an existing Calendar record.
If the Country, State, or City field was updated between 3 hours and 3 hours 30 minutes ago, the flow automatically generates a new Calendar record for that contact.
The Calendar record’s contents are dynamically generated based on:
- The time of day
- Whether it is a weekday or weekend
- The contact’s location data
Trigger
- Schedule: Every 30 Minutes
none
Output
none
Related
Related Entities: Calendar
Related Flows: Util - Create Calendar Record , Hourly - Import Calendar Data from Template
Create Multiple Calendar Records
Daily - Generate Prior Days Calendar Record
This flow processes Contacts with the Digital Contact client type.
It identifies yesterday as the target date, then reviews the calendar data from the day before yesterday to verify that it represents a completed day.
A completed day must include at least one of the following combinations:
- A Full Day Working record
- A Non-Working record
- Both an AM Working and a PM Working record
If the previous day is not complete (for example, an AM record exists but no PM record), the flow completes the missing entry using the most recent calendar information:
If a PM record is missing, the AM record’s location for the same day is used.
If an AM record is missing, the location from the last record of the previous day is used.
Once the previous day is validated and completed, the flow generates records for the target date (yesterday) using the same completion and validation logic.
Trigger
- Schedule: Every day at 10:00
none
Output
none
Related
Related Entities: Calendar
Related Flows:
Flow 1-5 - Import Calendar Data from Template
Grant Contact Access to Calendar when Residency Questions are Enabled
Hourly - Import Calendar Data from Template
Check Status of Adobe Agreement
Check the status of all outstanding agreements within Adobe Sign
Trigger
- Schedule: Every 15 Minutes
none
Output
none
Related
Related Entities: Document Approval
Related Flows:
On Completed Agreement Update Document Approvals
Check the status of all outstanding agreements within Adobe Sign
Trigger
- Type: Automated
- Connector: Adobe Sign
- Action Type: When an agreement workflow is completed successfully
- Parameters:
- Include Agreement Info?: Yes
- Include Agreement Participant Info?: Yes
- Include Agreement Document Info?: Yes
- Include Agreement Signed Document Info?: Yes
none
Output
none
Related
Related Entities: Document Approval
Related Flows:
On Submitted Calendar Record Send Email to Users
PDF Signing - Create Individual Agreement from Document Approval
Create Adobe Sign agreements for an individual contact
Trigger
- Type: Automated
- Action Type: When a HTTP request is received
- Parameters:
- Request Doby JSON Schema :
{
"type": "object",
"properties": {
"documentApprovalID": {
"type": "string"
}
}
}
Output
none
Related
Related Entities: Document Approval
Related Flows:
PDF Signing - Create Individual Agreements from List
Create Adobe Sign agreements for an individual contact
Trigger
- Automated
none
</details>
<details>
<summary>Output</summary>
``` json title="Output"
none
Related
Related Entities: Document Approval
Related Flows:
PDF Signing - Create Joint Agreement for Data Approvers
- Replaced Per Service Line FetchXMLs with a single Fetch to return Document Approval - Document Signers
<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="true">
<entity name="contact">
<attribute name="fullname" />
<attribute name="emailaddress1" />
<attribute name="tt_clientcode" />
<attribute name="tt_managername" />
<attribute name="ownerid" />
<attribute name="contactid" />
<order attribute="fullname" descending="false" />
<link-entity name="tt_documentapprovaldocumentsigners" from="tt_contact" to="contactid" link-type="inner" alias="ao">
<filter type="and">
<condition attribute="tt_documentapproval" operator="eq" uitype="tt_documentapproval" value="@{outputs('Get_Document_Approval_by_ID')?['body/tt_documentapprovalid']}" />
<condition attribute="statuscode" operator="eq" value="1" />
</filter>
</link-entity>
</entity>
</fetch>