Background ripple steps

With the background ripple, your users don't interact directly with it. Instead, you use a combination of emails and tasks to alert employees, assign documents with mail merge and so on.

📌Note: All steps happen instantly after each other unless you use the Wait step.

Check out the steps available for background ripple in the table below.

Step	Details
Check document signed	Configure which document to check and confirm what to do if the document was signed: Has not been signed: The next chronologic step will then occur. Has been signed: Specify in the GoTo Step what should happen next.
Check logbook actioned	This is useful if you want employees to update emails or tasks or documents to be triggered. This can check if a logbook has been updated: Updated: You can either exit or go to another step. Not updated: It automatically goes to the next step.
Check task actioned	This checks the tasks you have created previously. From here, you can specify what happens if it has been completed. Task has not been actioned: The next chronologic step will then occur. Task has been actioned: Specify in the GoTo step what should happen next. If the person has completed the task, define the next step, such as a Thank you email, or exit the workflow from there. If you wish to jump to the next step, create this first. Once done, add the Check Task Actioned step. You can then re-order the steps from there.
Email	You can create a ripple and send an email to either an employee within your company or an external email address. This, like the tasks, allows you to put the tag fields in. Specify the recipient: Employee: Use the list to select their name. Email: Specify their name and the email address you wish to send to. Click Tag List for all the available tags you can use. 📌Note: You can add multiple attachments to this email. We recommend you use a generic one as this attachment is added to the email every time this workflow runs.
Exit	This exits the whole workflow, put this at the end to stop the workflow looping.
Give Thanks	This sends a Thanks badge to the employee who the ripple has been triggered for.
Go to	Use this to jump back or forward to another step. For example, send a follow-up email after a task hasn’t been completed, then chaser email and then go back to the original wait to loop again.
Launch Ripple	This triggers an interactive ripple to start for the employee in question. Note: Firstly, create an interactive ripple and set it to Active. For example, the interactive ripple may prompt an employee to create a new logbook record, which the background workflow would then check to see if this has been actioned before moving on to the next background step.
Mail Merge	This is where you can merge a template that you have already created in the system. When setting this up you can choose if an employee or their manager has access, or if a signature is required from the employee. Note: This won’t trigger an email to the employee.
Push notification	Send a notification to the employee, manager or specific employee outside the employee query.
Task	Create a task for an employee. You can use mail merge tags to make this more specific to that employee. Give the task a name, assign it to someone and put the description in. The Date Offset is the number of days from when the task was assigned that it becomes overdue if not completed.
Wait	This allows you to wait a number of full days or make it wait until Monday - Friday. The first wait day begins a day after the previous step. Example of a two-day wait step after a task was assigned: Day 1: Assign Task. Day 2: Wait day 1. Day 3: Wait day 2. Day 3: Check Task actioned.

Interactive ripple steps

Ripple Check logbook step not working for actions that already happened

Create an interactive ripple to add logbooks to all users

Ripple emails still sending after completing Logbook

Create a ripple to check driving license logbook

Step

Details