A Standard Task in Evolve ATS Onboarding is used when creating a custom form or information task, e.g., a form to collect a t-shirt size or a policy notification. When you select this type of task, you will see the HTML editor, which you can use to enhance the look and feel of your task.
Audience
Onboarding Admin
Create Form
Navigate to the Onboard Admin tab, then select Task Templates.
Click + New Task Template.
Complete the fields in the New Task Template pop-up:
- Choose type - Select Standard Task Template
- Choose language – Select the desired language
Click Create.
Use the HTML editor tools to adjust and build your task.
You can insert placeholders to either capture data or show data. To add a placeholder, click Placeholder.
Select a placeholder in the Custom fields pop-up.
Options related to the field will be available:
-
Mode
- Input – Allows the assignee to provide data, which will display as a black text box or the corresponding field type.
- View—Allows you to insert the value of already collected data so that the field shows up as a value, and the assignee cannot edit it.
Click Add.
Complete the additional fields in the New Task Template:
- Name / Internal Name / Task Template Code- Provide your template with a unique name.
- Description – Describe what your new template will be used for.
- Default Assignee – You can set the default assignee as the hiring manager, a new hire, or a specific employee.
- Watchers – Select any users who should be notified about the progress of this task.
- Status—The template is marked Active by default. Active templates can be pulled into any process template and assigned to onboarding.
- Due Date – The date by which the task should be completed.
- Activation Date—When you select Activate with onboarding kickoff, the task is assigned immediately and becomes visible to the assignee. When you choose Delayed activation date, the task is assigned after a specified delay.
- Define Dependencies—This feature allows you to specify the exact set of conditions that must be met for a task to be included in an onboarding process.
- Inclusion Criteria—By default, this is set to Always Include, which means there is no conditionality. If you prefer the task to be included/excluded from a specific process based on a condition, use Include when the criteria are met. Please refer to the Inclusion Criteria Examples for more details.
Click Save.
Inclusion Criteria Examples
When creating conditions for Inclusion Criteria, there are three ways in which you can define a set of conditions:
-
All conditions are met - This option should be used when each of the listed conditions must be true for task inclusion. Even if one of the conditions is not fulfilled, the task will be excluded.
- For example, consider a scenario where you want to provision server room access for all IT engineers working at the San Mateo location only. i.e., if an IT engineer starts working at another location, they should not receive server room access.
-
Any of the conditions are met - This option should be used when there are several possible scenarios in which you want the task to be included. The scenarios are somewhat unrelated, and any of them can lead to task inclusion.
- For example, you want to provide a cell phone to a new employee, whether they are an IT engineer or an OPS support engineer.
-
Advanced - This type of condition should be used when you have a combination of all and any.
- For example, procure a new cell phone for either IT engineers or OPS support engineers only when they are working in San Mateo.