Clarity Service Management

Expand all | Collapse all

How restrict in CA so that a case can not be saved if the analyst

  • 1.  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-04-2017 03:30 PM

    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.



  • 2.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-05-2017 12:25 AM

    Hi John,

     

    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.



  • 3.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-05-2017 10:26 AM

    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



  • 4.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-09-2017 12:15 AM

    I would suggest that you would have to create a trigger and write some SPEL code to handle that.



  • 5.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-09-2017 12:06 PM

    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



  • 6.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-11-2017 01:14 AM

    I don't think this is possible by data partition.



  • 7.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-22-2017 05:42 PM

    How do you think it is possible to do it?



  • 8.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-22-2017 05:57 PM

    As I said before, create a trigger and write some SPEL code to do the validation.



  • 9.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-22-2017 06:04 PM

    Yes, but you a manual a guide on how to do this, is I have not work with trigger



  • 10.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-22-2017 07:39 PM

    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

    and

    https://communities.ca.com/docs/DOC-231156196-where-can-i-find-spel-functions-documentation

    If you are looking for someone to develop this for you please send me a message with your contact information and I respond.



  • 11.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-09-2017 12:06 PM

    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



  • 12.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-09-2017 12:07 PM

    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



  • 13.  Re:  How restrict in CA so that a case can not be saved if the analyst

    Posted 05-29-2017 05:56 PM