Process Step Details and Examples

This article gives details and examples of the functions that are available in steps.

• Create Email
• Create Word, Spreadsheet and Presentation
• Adding Details to the Steps
  • Filing in Steps
  • Workflow in Steps
  • Task in Steps
  • Comment in Steps
• Including Merge Fields in the Filing Details
  • Merge Fields that do not work in the Name or Comments in Processes Steps
  • Including Merge fields in the Name
  • Merge Fields for Year
• Create Phone, Create Note, Create Meeting
• Delay
• Create Job
• Update Client
• Update Job
• Execute Process
• Stop
• Summary Notification
• myprosperity Share Document

Create Email

The following is an example of a Create Email step.

Recipients - The Recipients is initially set as the "Client Email' as the To recipient. This will use the email address held for the Client selected for the Process and this can be changed, if relevant. Additional Recipients can be added as the To, CC or BCC recipient(s). These are added in a similar way to when creating an email directly in FYI (refer to Adding and Changing Recipients when Creating an Email).

You can include recipients in the following ways. All or any of these can be used to add recipients.

• Search for internal user
• Enter a new email
• Client Email (to re-select the email for the client)

Click the drop-down under the Recipients field and select which of these you want to do. If you delete the default selection of "Client Email", this can be re-selected from the bottom of the drop-down.

Use the drop-down next to To to select this as To, CC or BCC.

Template - this selects the Email Template that will be used. The template can include merge fields to create the email text

Attachments - you can add an attachment to the email. This must be a document that has been created by a preceding step within that process. Clicking the drop-down for Attachments in the email step displays a list of all the relevant preceding steps that generate a document, that is, any Create Word, Create Spreadsheet, Create Presentation, Create PDF steps.

Attachments as PDFs - set the Attachments as PDFs switch to "On" to send the attachments as PDF files, or "Off" to send in their original file format.

Sender - This can be set to a specific person in your user list. Or it can be set as "Manager" to set the owner as the relative client's manager, or as "Partner" to set the Sender as the relative client or job's partner (as held in Xero Practice Manager).

• For a process that is run for a Client, the Manager or Partner is taken from the Client Details (refer to Client Summary).
• For a process that is run in the context of a Job, the Manager or Partner is taken from the Job Details (refer to Job Summary tab in Job Workspace).

Send attachment(s) - determines how an attachment to the email is sent, by email or sent to the client's OneDrive. When this is set as OneDrive, and Attachments as PDFs is set as "Off" you can select Co-edit with client (refer to Co-editing an External Document).

Save or Send - whether to save as "Draft in FYI", "Draft in Outlook" or Send Immediately".

Create Word, Spreadsheet and Presentation

The steps for Create Word, Spreadsheet or Presentation allow you to select settings for Filing, Workflow, Task and Comment.

You can select a Template that will be applied, and for Word, you can also select a Stationery. The Template and Stationery can include merge fields to create the text.

If you want to include merge fields in the filing details such as the document name, these are added to the Filing section in the step (refer below to Including Merge Fields in Filing Details).

The following is an example of a Create Word step. In the Action section, select the Template to use and, if relevant, the Stationery.

Adding Details to the Steps

Details are added to the steps in the same way as when creating emails and documents, using the sections in the drawer.

Filing in Steps

The Filing section controls how the document is named and where it is filed.

The follow is an example of creating a Word document.

Name is the name of the document that will be created in FYI.
If a Template has been selected, this can be set as "Default from template" to use the name of the template for the document that is created, or this can be changed to any text as required.

Autofile can be "Disabled" or "Enabled".

• When AutoFile is "Disabled", the document will be filed using the settings for Cabinet and Category in the process step.
• When AutoFile is "Enabled", the Filing Defaults for the client are used, if available.
  These settings are taken from the specific client the step is processed for. Where the client is part of a Client Group, the process ignores whether there is a client for the group set with the Include in Autofile setting (refer to Setting Filing Defaults for a Client).

Cabinet and Categories in the process step are only available if Autofile is "Disabled" and can be set as relevant for the type of document being created by the step.

Filing defaults to "Filed". If this is set as "Unfiled" it will appear in the owner's In Tray ready for filing. If the Owner is set in the Workflow section this is used (refer below to Workflow in Steps), otherwise it is set as the Owner of the Process.

Workflow in Steps

You can use the Workflow section in the step  for information purposes, to set the approval of an email or document, or to set it as read-only. This is the same as the Workflow section when creating emails and documents. Refer to the section Workflows.

Owner can be used to select the owner of the document/email.

This can be set to a specific person in your user list. Or it can be set as "Manager" to set the owner as the relative client or job's manager, or as "Partner" to set the owner as the relative client or job's partner (as held in Xero Practice Manager).

• For a process that is run for a Client, the Manager or Partner is taken from the Client Details.
• For a process that is run in the context of a Job, the Manager or Partner is taken from the Job Details.

If there is no Partner/Manager assigned to the client and the process is creating an email, it will add the Process Owner as the Owner of the email created in the step. When a Word document or Meeting is created by the process step, it adds the user running the process as Owner of the document created.

Approver can be used to set the Approver of the document/email. This can be set to a specific person or it can be set as "Manager" to set the owner as the relative client or job's manager, or as "Partner" to set the owner as the relative client or job's partner.

• For a process that is run for a Client, the Manager or Partner is taken from the Client Details.
• For a process that is run in the context of a Job, the Manager or Partner is taken from the Job Details.

Workflow Status can be set for information purposes, to set the approval of an email or document, or to set it as read-only. This is set as default to "Not Started".

Task in Steps

Task is used to create a task for the document/email when the process runs. In the following example, the task is created for an email.

Create a Task - click to set this as "Yes" to create a task.

Subject - enter a brief subject for the task. This displays in the lists in FYI.

Assignee - can be set as a specific person in your user list. Or this can be set as "Manager" to assign the task to the relative client or job's manager, or as "Partner" to assign it to the relative client' or job's partner (as held in Xero Practice Manager).

• For a process that is run for a Client, the Manager or Partner is taken from the Client Details.
• For a process that is run in the context of a Job, the Manager or Partner is taken from the Job Details.
• If there is no Partner/Manager assigned to the client/job, the Assignee is set as "Unassigned".

Due Date - select when the task needs to be completed as the number of days. You can also set this as 0 (zero) days to make the task immediate.

Status - this defaults to "Not started". The Status can be changed to "In Progress", so when the task is created, nothing needs to be actioned on it.

Cabinet - if Task Security is set in your Practice Settings, a Cabinet can be selected to add the Cabinet security to the task. This ensures that only users with access to that Cabinet can see the task, for example, for sensitive areas such as HR or performance management. When creating a task, you can select the cabinet. Where a task is automatically created as linked to a document, the task cabinet is inherited from the document created and displays in the task details. Refer to Managing Practice Settings.

Blocking - when creating a task, you can set Blocking as "On" so that the process stops until a Task created in the automation process is set as "Completed". This could be used, for example, for a Task created in the process to ensure that an email, word or any other document created in the previous step(s) has been checked before any other actions in the process are done. When the Task is set as "Completed", the process could then be set up to continue and send the checked email or send an email with a checked document attached.

Note: If the process only holds one step, ensure you do not set a task that is created with Blocking as "On" as the process will show as outstanding until the status of the task is set as "Complete".

Details - type the brief details of the task. The assignee can easily display the email to see what the task relates to.

Comment in Steps

Automatic notifications can be defined and triggered as part of process automations using Comments. This ensures that you are aware of documents that have been imported, filed or changed automatically in FYI. Refer to Automation Notifications.

Including Merge Fields in the Filing Details

Certain fields in the Filing section in Process Steps, such as Name and Year, and you can use relative Merge Fields.

The example below is for the Tax Assessment. In the example below, the from and to tax periods are included in the document Name as NOA Agree {{ TaxPeriodFrom }} - {{ TaxPeriodTo }}.

To include the Client Name this would be added to the document name in the Filing section for example, as NOA {{ ClientName }}.

Merge Fields that do not work in the Name or Comments in Processes Steps

Note: The following Merge Fields do not work in the Name field or in the Comments in Processes.

• Created Date
• Original File Name (except in the Alter Document step)
• Reference Number
• Upload Folder
• Share Folder

Including Merge fields in the Name

1. Click the ellipsis (…) next to the Name
   
   to display the pop-up with the relevant merge fields that can be used. Click the down arrow next to a category to expand it and display the merge fields in that group.
   
   
2. Position the cursor in the Name where you want to include the merge code.
3. Click one of the merge fields that is listed on the right-hand side (for example, you could add NOA Amount, or from the FYI group, Client Name)
4. The correct code for the merge field is added for you in the Name.

Merge Fields for Year

Year, this can include merge fields by selecting "Merge Field" from the drop-down which then displays the  merge field pop-up selections in the same way as for the Name. If this is set, for example, with "TaxYear" as the merge field, the document will be automatically filed in the relevant tax year as the Year category.

Create Phone, Create Note, Create Meeting

You can use the Create Phone, Create Note, Create Meeting steps to create a Phone Call, File Note or Meeting in FYI. You can use Merge Fields for the Name and Year in the same way as for other documents. The following is an example of the Create Meeting step.

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. The Delay can be set to a number of hours, days or weeks. 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 Automation - History displays the date and time that each step completed.  Refer to Automation History.

Create Job

When using a process with a Client View, the Create Job step can be used to create a Job (refer to Custom Processes using Views and Summary Notifications).

The information is the same when using Create Job from the + button (refer to Create Job in FYI) except the Client is not selected and the Job is created for the Client(s) selected from the Client View in the process.

The Job is synced immediately to Xero Practice Manager where the job number will be applied.

Note: There is a known issue that when Jobs that are created in FYI, if a Job Category is selected, this currently does not show in the Job drawer and is not synced to Xero Practice Manager. This will be corrected as soon as possible.

Update Client

The Update Client step can be used to update Client Custom Fields. When the update is made by the automation process to the Client in FYI, the change is synced to Xero Practice Manager.

When the Custom Field has been selected in the step, you are then prompted to enter the value to set it to.

Updating a Client Custom Fields that is a Date
When updating a Client Custom Field that is a Date, this is set as the "Current Date". An example of this would be updating the Engagement Date on the client record as a result of a client signing an engagement letter. An automation can be set up using a view that detects that the engagement letter has been signed by the client and to update a Custom Field such as "Last valid engagement date" in the client record with the current date stamp.

Another example when this could be used is to record the last date that a partner made contact with a client. This can be triggered when a Phone Call or Meeting interaction was created in FYI.

This process step is used to update the record with the current date so this would not be used for a Custom Field date such as a date of birth.

Update Job

In the Action for Update Job, you select the Job State, Manager or Partner to be set by the process.

The Manager or Partner can be set to a specific person in your user list. Any of these can be set as "‘Unchanged’ if the State, Manager or Partner are not going to be changed by the process.

The Update Job step can also be used to update Job Custom Fields. This is currently available for Custom Fields that are dates in the same way as Update Client above. This process step is used to update the record with the current date.

Execute Process

Execute Process sets one process to execute one or more other active processes. You can only use this to execute a "Manual" process .

An example of using Execute Process is for a ‘New Employee onboarding’ process which includes separate business divisions who 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

Where a Process is running for a specific Client, Document, Job or Task and it then runs a separate Process using the Execute Process, the filter from the initiating Process is used.

Stop

The Stop step can be used to stop a process that is running using a filter or a view and where the underlying selector has changed so that the trigger is no longer applicable. This could be where a change has been made manually, or by another automation process.

For example, if a process has been set up to select documents, clients,  jobs or tasks using a specific Status and the Status is changed manually while the process is running, that document, client, job or task would then not be included in the view. Any remaining steps in the process are then stopped for the specific document, client, job or task. The Process will continue to run for any other documents, clients, jobs or tasks that are still included in the view as the Process selection is still applicable.

As an example, if a process is set up to send a reminder email for any jobs with a specific Status. The process is also set up with a Delay step for 1 week, with a Stop step and then another Create Email step to send a second reminder email. The second email is only sent 1 week later if the Status for any of the jobs is still the same. The process is stopped for any jobs that have had the Status updated and the process will only send the second reminder for those jobs that still have the same Status set.

Summary Notification

When a Custom Process is filtered on a Documents, Jobs or Tasks view you can add a Summary Notification step so that the notifications are sent out automatically as a summary instead of as individual notifications. Refer to Custom Processes using Views and Summary Notifications.

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.

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 checkmarked 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.