Process Step Details - Execute Process

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

The Execute Process step is used to execute a "Manual" process that has been enabled to run "From Process Step". Refer to Setting Up Custom Processes.

Execute Process Step

The following is an example of the Execute Process step.

2100_Execute_Process_Step.gif

An example of using the Execute Process step is for a ‘New Employee onboarding’ process which includes separate business divisions that need to complete their ‘checklist’ of onboarding tasks. For example, there could be the following four processes that each division can run separately and also have a top-level process that runs all four of these when needed.

  • Execute process: IT new employee onboarding
  • Execute process: HR new employee onboarding
  • Execute process: Finance new employee onboarding
  • Execute process: Operations new employee onboarding

When the process is run, details of the executions can be viewed from the Process History tab, including the ability to navigate between related initiating processes and the executing process steps.

Process Step Field Details

Field Details
Process

Select the process you want to execute. It is added to the current process in the sequence in which it should be executed. 

If the Process selected for the Execute Process step uses a:

  • Job view as the Filter, that process must have parameters set so that Job(s) are selected.
  • Document view as the filter, document information is available for use as merge fields in Create Document steps and as attachments in Create Email steps.

Note: Automations marked as Inactive or Draft will not be executed, and an error will be displayed in the History tab.

Job Used to select the Job that you wish the execute process to run. For example, when creating a Job Rollover Process, Current Job can be selected. Refer to Job Rollover Process.
Apply Additional Process Filter

The Apply Additional Process Filter option can be used as a way to split a Process. It can avoid duplications in processes, and is used to set up 'master' Processes and then have 'secondary' Processes that run on certain conditions.

  • When Apply Additional Process Filter is set to "No", the filter from the initiating Process is used as the filter for the Execute Process.
     
  • When Apply Additional Process Filter is set to "Yes", the filter from the process to be executed is used, in addition to that from the initiating Process. 

    After running any steps for Clients, Documents, Tasks or Jobs that meet the criteria using the filter from the initiating Process, additional processes can be executed using the filters in the process selected for the Execute Process step, and enabling Apply Additional Process Filter.

Note: The process selected in the Execute Process must apply the same filter criteria as the initiating process, but can have additional parameters. For example, if the filter for the initiating process retrieves Clients for a specific Custom Field, a Client filter must also apply to the process run with the Execute Process step.

For example, if Process A is filtered by Clients - View filter (an email reminding them of their lodgement due date), and Process B is set to the Document - View filter:

  • Apply Additional Process Filter = No: Process B will not run because the filter type does not match the initiating process filter (Clients). 
  • Apply Additional Process Filter = Yes: Process B still won't run because the filter type does not match the initatiation process filter (Clients). 

To run a process with a completely different Filter, this must be run as a separate process, not with the Execute Process step.

Block Initiating Process

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

  • If the Execute Process contains a Blocking or 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 top level process will complete with a warning in Process History.

 

Was this article helpful?
0 out of 0 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.