What role is required to change the approval status on tasks?

[studobson]

We are manually adding additional tasks onto requested items. Some of them will require approvals (sometimes multiple approvals). However, the approval state is in "not yet requested" and the ITIL user cannot change it to "requested". Therefore, the request for approval never gets sent out.

Is there a specific role that we need to allow this? I can do it as an admin, but i'd be stupid to give everyone that role!

[Pradeep Sharma]

Hello Stu,

What table are you referring to? You can create a UI action and then limit the role to ITIL. This way user can click on the UI action and update the field.

[studobson]

SC_TASK table, so it's a basic request with one RITM and one SCTSK. We do allow them to add additional tasks, but the approvals are on the SCTSK records.

Like i said, when they add the approver, it stays in the "not requested" status. The ITIL user needs to be able ti change the status of the approval to "requested" so the approval notification email goes out.  

[Pradeep Sharma]

Thanks for the update. There are two options. Depending on how it's setup on your instance, you can navigate to approval table and give ITIL role access to update the field but then hide the other values i.e they should not be able to approve the request.

The other way is to change the default value from not requested to requested at dictionary level. However please note this will be a GLOBAL change. It will impact all other apps on your instance.

[studobson]

I did add the Approval_Admin to one user, but yeah, that gives too much control. I will investigate adding the ITIL role to the update field and restrict it to "requested". I like that idea.

And yeah, i thought about the default value, but no, don't want to do that as we need to control when the approval requests go out.

I'll try the former and see what comes of it. Thanks!