![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
👥 Roles and permissions
The following users can create a repeating task:
Anyone who is a member of a control, label, or risk
Repeating tasks are created from a template. Tasks are generated either on a schedule or in response to a triggering event. When you create a repeating task, you can configure the template to integrate tasks into ServiceNow when the repeating task template is triggered.
Repeating tasks can be created via the Automations tab found on controls, labels, and risks. For more information about repeating tasks, see Creating a repeating task.
From the left menu, select the tab that corresponds to the object you want to link the repeating task to. For example, if you want to link the repeating task to a control, select the Controls tab.
Select the specific object. For example, if you want to link the repeating task to control ID 1234, select that control.
Select the Automations tab.
Click New repeating task.
The Repeating task window opens.
From the Template tab, do any or all of the following:
Enter a name for the task (required)
💡 Tip
Task titles have a 250-character limit.
Enter a description
Change any of the following by mousing over and clicking the Edit icon:
From the Assign by drop-down menu, select Individual or Group.
Individual - Assigns a single individual to the task. Select an assignee from the Assignee drop-down menu.
📝 Note
Use the Unassigned option at the top of the list of assignees to leave the task unassigned.
📝 Note
The assignee must be a user in Hyperproof. If the user you need is not in the list, click the Add them to Hyperproof link below the list of user names. You can add the user as a contact if they are not going to do any work in Hyperproof. See Adding users to your organization
Group - Assigns a group to the task. Select a group from the Group drop-down menu. By default, the group lead is designated as the owner. If the group doesn't have a group lead, select an individual from the Assignee drop-down menu.
📝 Note
Assignees in Hyperproof are matched with assignees in ServiceNow based on their email address. To ensure that the task is assigned to the correct person in ServiceNow they must have the same email address in both systems.
Due date (this is the number of days out that you want the task to be due)
Priority
Create a repeating task based on a schedule or an event:
To create a schedule-based repeating task:
Below Repeats, select On a schedule.
Below Schedule, select when the task should repeat.
Below Starts repeating, select the date that the task should start.
💡 Tip
For example, if you have a task that starts repeating on June 22, and it's due 14 days later, the task will be due on July 6.
To create an event-driven repeating task:
Below Repeats, select On an event.
Below Event, select the event that should trigger the task to repeat.
📝 Note
Events vary based on the object selected for the repeating task. For example, the list of control events is not the same as the list of risk events.
Depending on the option you choose, additional drop-down menus may appear.
On the task window, click the ServiceNow icon and select Create a task. For information on the Attach an existing task option, see Attaching an existing ServiceNow task to a Hyperproof task.
In the Ticket type field, select a ServiceNow task type. Types include:
Incident task - Defined in ServiceNow as a way to request action from assigned work groups who are not mentioned in the incident itself. For example, when an incident occurs, a specific team in ServiceNow will be responsible for the initial response. However, they may require support from additional groups and will create an incident task to receive that support.
Catalog task - Defined in ServiceNow as a measurable and repeatable unit of work that needs to be completed to fulfill a requested item. For example, a request for new software or hardware.
Problem task - Defined in ServiceNow as tasks associated with a request to fix an issue. Core teams reviewing the root cause of an issue or solving a problem often rely on support from additional teams. Problem tasks are used to communicate and assign actions to these groups as part of the original problem request.
📝 Note
Your organization may define and use these task types differently. Refer to your internal documentation for recommendations about when to use each task type.
Additional fields display based on the task type selected. These fields are specified in ServiceNow, but they are not required.
Complete the fields associated with the task type you selected.
Click Save to save the repeating task template.