Search the Community
Showing results for tags 'ca service management'.
Found 3 results
Hi my friends, I'm trying to update the model information of my CI's using the ID lookup option on the GRLOADER, but I'm receiving an error mensage as bellow. Did you guys ever see the kind of error before? Of course, the model ID is correct on MDB. Error Mensage: <!--WARNING: Ignoring model(9936A046EFCF0445A3394F5EA75E3E83). Its definition may not exists (or) manufacturer associated with it is different in mdb.Unable to find unique Model for mfrmod.sym=(9936A046EFCF0445A3394F5EA75E3E83). Unable to find unique Manufacturer for ca_cmpny.sym=(PHILIPS). --> <id>081F23B26BB75843BAD29386918C7EFA</id> <name>TESTE_10</name> <serial_number>7OIDFA9837498340</serial_number> <tenant>MEU TENANT</tenant> <class>PC Laptop</class> <family>Hardware.Workstation</family> <!--WARNING: Unable to find unique Model for mfrmod.sym=(9936A046EFCF0445A3394F5EA75E3E83). --> <model lookup="id">9936A046EFCF0445A3394F5EA75E3E83</model> <!--WARNING: Unable to find unique Manufacturer for ca_cmpny.sym=(PHILIPS). --> <manufacturer>PHILIPS</manufacturer> <status>Spare</status> <service_org lookup="id">B682CD1F31C88141B67417E8D694A689</service_org> <repair_org lookup="id">B682CD1F31C88141B67417E8D694A689</repair_org> </ci> -<ci>
Hi, I want to configure SLA based on business days. For example, Today If I create two incident at different time. The SLA will start calculation from next business day, not in from ticket creation time. The P1 ticket having one business day means, It will will expire on second business day. Is it possible to configure, please suggest me. Thanks, Bala.
Hi guys, Consider this scenario: I have a request category with 3 classic workflow task attached: Request category Task 10 If the status of this task is APP then the task 20 and 30 most be skipped. If the status of this task is APP2 then the task 20 most be Pending and the task 30 most be Waiting. Task 20 Task 30 So to do this I've followed this steps: 1) Put the file upd_val.spl in the folder $NXROOT/site/mods/majic; 2) Recycle spel_srvr or restart the ca sdm services; 3) Create an action macro using this code: macro::upd_val("cr_wf", format("cr = '%s' AND sequence IN (20, 30)", cr.persistent_id), // search over other tasks in the same parent request with seq 20, 30 1, 0, // delays "status", "SKIP" // new status ); 4) Add this action macro to the status on task 10 that most be completed to skip the task 20 and 30; Reference: https://communities.ca.com/docs/DOC-231155346 by @cdtj upd_val.spl