When a user changes data in Customer 360 SaaS, the change might trigger an approval workflow. The workflow might consist of one or multiple approval tasks linked together.
The approvers of the task must review and approve the data before it becomes master data.
As an approver, you might want to sort and find tasks that you want to approve in the workflow inbox. To review a task, an approver must claim the task. For example, to review tasks based on priority or status, you can sort tasks based on priority or status, and then claim the task. You can't sort tasks by creator.
Tasks in the workflow inbox that aren't approved or rejected might expire and become invalid.
Also, approvers can choose to send tasks back to a previous step in the workflow. Tasks that approvers send back move through the approval workflow again.
For example, as the second approver for an updated record, you can either send the task back to the task originator or the first approver. If you send the task back to the originator, the originator can either edit the record details and submit the record for review again or reject the changes. If the originator submits the record for review, the first approver can approve or reject the changes. If the first approver approves the changes, then the second approver can approve or reject the changes.
When you send a new or updated hierarchy task back to the originator, the originator can edit the hierarchy before sending the hierarchy for review again. But when you send new records, updated records, and deleted hierarchy tasks back to the originator, the originator cannot edit the asset before submitting the asset for review again.
Note: If your changes trigger a workflow, you cannot see the approval task and approve your changes, even if you are assigned the approver role.