I can restrict in CA so that a case can not be saved if the analyst and category do not belong to the same group.
Are you referring that only Analyst belonging to that group which is assigned in ticket and category mapped to that group should only be able to make any changes.
If yes, try creating data partitions.
Below link is the sample data partition FYR implemented on workflow.
An Update data partition constraint for a Workflow task attached to a Change Order does not implement the restriction an…
Please try creating similar data partition on call_req table.
Hello kalsw01,No, I mean that the categoria that is assigned on the ticket should assigned a an group for example an ticket assigned with network category Should only be solved by the group of networks and if I want to transfer it to another group should ask me to change the category
I would suggest that you would have to create a trigger and write some SPEL code to handle that.
how i do create an data partition on call_req table for Validate that the category group and assignee are the same and do not allow the assignee to another group analyst
I don't think this is possible by data partition.
How do you think it is possible to do it?
As I said before, create a trigger and write some SPEL code to do the validation.
Yes, but you a manual a guide on how to do this, is I have not work with trigger
There are numerous examples on the forum for specifying triggers (in this case, a POST_VALIDATE trigger) such as https://communities.ca.com/thread/241693499
and reference material for SPEL such as https://communities.ca.com/docs/DOC-231158970-spel-api-methods
If you are looking for someone to develop this for you please send me a message with your contact information and I respond.
CA SDM Data partition::. call_req cr