Process Step Details - Other Functions

Plan: Not Available: Intermediate Available: Pro or Elite

Users: Not Available: All users Available: FYI Admins or User Group permissions

Practice Management Source: Available: All sources

This article gives details and examples of the other steps that are available in steps to perform other functions in Automation Processes.

Delay

A Delay step can be added to an Automation Process to set a delay in the process. This delays the next step in the process from running until that delay is over. For example, this could be used so that on completion of a Task that is created in the process, there is then a delay of the selected hours, days or weeks and then an email is sent.

The Delay can be set to:

  • Hours,
  • Days, or 
  • Weeks. 

Note: Days can be entered as whole numbers only. If a part day is required, we recommend using the Hours instead.

The delay starts from the date the previous step was completed, or in the case where the delay is the first step, from the date the automation process starts. For example, if the previous step was run on the 1st of January, a delay of 5 days means that the process will resume from the 6th of January.

The Automation - History displays the date and time that each step was completed.  Refer to Automation History.

1231_Automation_Step_Delay.gif

Block Initiating Process

When Block Initiating Process is enabled, this blocks the initiating automation Process from completing until the Process in the Execute Process step has been completed. For example,

  • If the Execute Process contains a blocking or an autocomplete Task, the initiating Process does not get processed until the Task is complete.
  • If the Execute Process contains a Delay step, the initiating Process does not get processed until the Execute Process has been completed.
  • If the Execute Process fails, the initiating Process will not continue and remains "In Progress".

myprosperity Share Document

For practices that have the integration with myprosperity, when a Custom Process is filtered on a Document View, the Share Document step can be added from the myprosperity Application.

Note: The client will need to have been created in myprosperity before the document can be sent. For details on how to create a client, refer to Integration with myprosperity.

The process takes the document(s) triggered from the Document view selected in the Filter and shares them directly with myprosperity. Ensure that the Filter is set with Run Only Once Per Document check-marked so that the document is only shared once.

This would commonly be used to share Client Signed documents with myprosperity using a Documents view with a filter applied to the Workflow column of "Client Signed".

This function is the same as using the Share function for a selected document and selecting Send via as "myprosperity" (refer to Sharing Documents via myprosperity) but no email is sent when the document is shared via the Custom Process.

1855_Process_myprosperity_Share_Document.gif

Was this article helpful?
0 out of 1 found this helpful

Stay Up-To-Date

  • Events

    We host a range of product demos, training webinars, workshops and more.

  • Service Status

    Check for updates on the FYI Platform

  • What's New

    Round-up of new features, fixes, and other important announcements.