Templates provide workflow foundations, searchable in Arbor Workflows, with preconfigured steps and dynamic data. After adding one, review and assign owners, tailor steps to your school’s context, resolve issues, and test before publishing; templates are not ready-made solutions.
Using a template is often the fastest way to turn a manual process into an automated one. Templates are designed to save you time by providing pre-built skeleton drafts for common processes. They are not designed to be ready to go or an out of the box solution.
How to use a Template
To use a template you will need to have permissions to enable you to build and edit a workflow. If you can see the Workflows tab on your Arbor Workflows homepage, this is a good indicator that you will be able to do this. If you need to check the permissions that relate by default to Arbor Workflows, take a look at this article: School MIS and MAT MIS Business Roles and Arbor Workflow Permissions
Select a Template
Once in Arbor Workflows, select the Workflows title of the left side. This will open the workflows tab with some popular ways to get started. These are from our high use templates.
Select 'Browse all templates' to open the full template library.
From here, you can search the suggested templates, use the search function to help find what you are looking for or 'Filter by category'. You will see a list of available templates and a short description of the template.
Choose your Template to see a preview of the workflow steps before you add this to your account.
To add this template to your account to continue building you can select 'Set up workflow', or select 'back to templates' to continue browsing.
Once you select 'Set up workflow' it will be deposited into your account. From here you will be navigated to the workflow builder to view and edit the steps to fit your context and own process. The first step will be to review the template and decide who should own each step. The builder will suggest who from the template played this role but this role might not be appropriate for your context. The issue checker will identify these for you and you will not be able to publish the workflow without completing this.
After you have done this, a good next step may be to test the workflow as it is to get a sense of the current build.
Why build from a template?
While you can build any workflow from scratch, our templates offer several key advantages:
-
Templates are built based on best-practice school processes. They provide the "bones" of the workflow so you don’t have to start from scratch.
-
It is much easier to delete or tweak a step that already exists than to build one from the ground up. You can take a standard template and iterate on it to fit your school’s unique context. Actions that you can take to tailor your workflow include:
Templates come with pre-configured Dynamic data on steps (like Arbor Data steps with automate communication with the MIS to complete an action), saving you the time of setting up data mappings.
Remember, a template is a great way to get started but is not an out of the box and ready to go solution.
We always recommend reviewing each step, recipient and task carefully to ensure these are what your school and context need.
Comments
Article is closed for comments.