‎2020 May 29 1:33 AM - edited ‎2024 Feb 03 5:50 PM
Hi All,
I have business requirement in which the value of "Assigned to " should not be equal system /technical users . In my service cloud tenant , the value for ticket assigned to is taken from fiD which first changes the ticket and later on this values need to be changed manually to user. As the current rules available are for visible, mandatory , there is no validation to check that user cannot be system user.
Can anyone share any pointers on this requirement.
Request clarification before answering.
How did you get the Technical user in the Assigned to Field. The Assigned to takes the employees. The technical users does not have a valid employee.
As a workaround you can do the below.
You can create a Rule modal validation with an error message which will prevent the save of the Ticket.
In the rule modeler , you can write the logic like the Assigned to NE the set of employees.
If you want to prevent creation of tickets with a list of employees, then you can always use PDI validations on Save .
Ideally If you have set up the determinations correctly, the current user will mot be added as Assigned to as it depends on the Member determination in the Involved party fine tuning.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Arun . The Model vlidation rule worked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.