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 

If I created a ACL, this will restrict the workflow also to create the change tasks in scheduled, implemented, Review. Right?

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

Chaitanya naram
Kilo Sage

If the tasks has been created from the Workflow with the Run script, system will consider mostly as a non-system activity. In this case, if you enable the workflow activity field, you can see that was empty for that specific change task created through the Run script.

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

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.