Restrict Users to create change tasks when change is one of Scheduled, Implemented, Review

Chaitanya naram
Kilo Sage

Hi All,

 

I have a requirement to restrict the users from creating a change task for a change request when change request state is one of scheduled, implemented, review.

 

What I have Done:

1) I restrict the NEW Button on change task related list using List Control with a condition and it works fine.

2) Created a business rule (Before Insert) on the Change task with state condition and Workflow Activity is empty (to allow creation of tasks through workflow) to abort the action in case the end users manually creating the tasks from change_task table.

 

Issue Facing:

 

Business rule is not allowing the workflow to create the change tasks.

 

Can anyone help me on this issue or how to achieve this functionality?

 

Thanks & Regards | Chiranjeevi Chaitanya Naram
Kindly mark the answer Correct and Helpful if it helps to resolve your issue.
1 ACCEPTED SOLUTION

Chaitanya naram
Kilo Sage

ACL did not work in this case.

 

I have achieved this through a Business Rule, Client Script and a flag variable.

 

A flag variable with values "Old", "NEW" and empty values. I am setting this flag as "old" for all the existing tasks and "new" for new tasks created after this functionality implemented.

 

Now i am writing a client script (onsubmit) with variety of conditions and restricting the users to create records.

 

Thanks & Regards | Chiranjeevi Chaitanya Naram
Kindly mark the answer Correct and Helpful if it helps to resolve your issue.

View solution in original post

12 REPLIES 12

@shyamkumar VK @The Machine 

 

I have tried creating ACL in below way.

 

ACL 
Type: Record

Opearation: Create

Name: Change_task

Role: ITIL

Condition: Change_request.stateINNEW,ASSESS,PENDINGAPPROVAL

It didn't work. With this i can't able to create the change tasks now even in NEW, ASSESS, PENDING APPROVAL stages whereas earlier i can do.

Thanks & Regards | Chiranjeevi Chaitanya Naram
Kindly mark the answer Correct and Helpful if it helps to resolve your issue.

@Chaitanya naram  , Refer to this 

 

shyamkumarVK_0-1708441205227.png

 

Please mark this as helpful and accept as a solution if this resolves your Ask.
Regards,

Shyamkumar

@shyamkumar VK No, It didn't work.

Thanks & Regards | Chiranjeevi Chaitanya Naram
Kindly mark the answer Correct and Helpful if it helps to resolve your issue.

It shouldn't.  If its a Flow (using Flow Designer) and you have that running as the user who initiated it and not the system, then you'll have an issue with the ACL.

The ACL should do the trick but you might need to add additional scripting to your conditions to allow users to create Change Tasks at specific times.  Such as if the Assignment Group of the Change is "my group" I'm allowed to create change tasks for that change.

You'd need to provide more details of what you want to allow, when and to who.  Then build the script logic accordingly.

Good luck.

shyamkumar VK
Kilo Patron

@Chaitanya naram ,  Instead of BR why cant you Create an "Create ACL" and add Condition as State is One of 

 

let me know if you need any help here

 

Regards,

Shyamkumar

 

Please mark this as helpful and accept as a solution if this resolves your Ask.
Regards,

Shyamkumar