Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Following tasks is an easy way to stay informed of what happens with the tasks you are interested in. With this functionality, users can subscribe to items that are vital to them and unsubscribe from messages that are not relevant anymore.
In SimpleOne, notifications by default are sent to the email specified in the user profile. Also, users can specify other notification channels once (to integrate them with the business solution, use SimpleOne REST API).
How to follow a task
You can follow a task by clicking the Follow button on at the top right of the formcorner.
After this, the follower will start receiving notifications related to this record, and the text on the button will change to Unfollow. To unsubscribe from messages, click the Unfollow button.
Note |
---|
To place the Follow button on the record form, perform the following steps:
You can check if the Follow button is implemented to the table.
|
Followers list
This multiple-choice field contains a list of users subscribed to notifications.
A The user is added to this list after clicking the Follow button. After clicking the Unfollow button, the user is removed from the Followers List.
Following are the related tasks
This functionality is implemented for ITSM objects: Change Requests, Incidents, InquiriesUser Queries, Problems, Service Requests.
If the followed record has one or more related records, then the value of the Followers List values field will be transferred from the parent record to the child.
Transfering logic
To understand the transferring transfer logic between related tasks, see the relationship cascade:
- Inquiry → Incident → Problem → User Query → Incident → Problem → Change Request.
- Inquiry → Incident → Change User Query → Incident → Change Request.
- Inquiry → ProblemUser Query → Problem.
- Inquiry → Problem → Change User Query → Problem → Change Request.
- Inquiry → Change User Query → Change Request.
- Inquiry → Service User Query → Service Request.
Transferring example
The agent was subscribed to the Incident in the system. A Problem problem was raised to deal with the incident causes, and afterward, a Change Request change request is opened to fix all the issues. In this case, the agent following the initial Incident incident will follow the related Problem problem and Change Request change request as well.
Notifications
The notification types implemented for the Following Engine functionality are listed below. In all cases, notifications Notifications are sent to all users from the Followers List related to the record.
In this context, the task is Inquiry a user query or of any other supported task type and is relates to the Task table or its child tables: Incident, InquiryUser Query, Change, Request, Problem.
Notification | Criteria |
---|---|
The followed task has been registered. |
|
The followed task has been commented. |
|
The followed task has been successfully processed. |
|
These notification rules and templates are provided by default. You can customize them to your goals and objectives, depending on your business needs. For more information, please refer to the the Notifications article.
Tip |
---|
Only the user assigned to the task (specified in the Assigned User field) can manage the Followers List related to this the task (add or delete followers). For other users, this list is read-only and unavailable to modifyfor editing. |
Table of Contents | ||||
---|---|---|---|---|
|