Jump to content

thiago23oliveira

Members
  • Content count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thiago23oliveira

  • Rank
    Level 2 Contributor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. thiago23oliveira

    Action macro for Request WF tasks

    To do this, I've created a topic on CA Communities: https://communities.ca.com/docs/DOC-231179890-how-to-skip-request-workflow-task-automatically
  2. 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
  3. thiago23oliveira

    Action macro for Classic Workflow

    Hi Mynhardt, Do you have the action macro to execute this action? =) I have the same scenario on my enviroment.
  4. Hi guys, I have this scenario on my enviroment: On the task 1, if the status is APP then the two next tasks should be canceled or skipped. If the status on the 1st task is APP2 then the next task should be pending and the third one should be waiting. How can I create a action macro to this behavior? (Object = Request Workflow Task).
  5. Hi guys, I have this scenario on my enviroment: On the task 1, if the status is APP then the two next tasks should be canceled or skipped. If the status on the 1st task is APP2 then the next task should be pending and the third one should be waiting. How can I create a action macro to this behavior? (Object = Request Workflow Task).
  6. thiago23oliveira

    Skipping Workflow Tasks In Classic Workflow

    Hi guys, I have this scenario on my enviroment: On the task 1, if the status is APP then the two next tasks should be canceled. If the status on the 1st task is APP2 then the next task should be pending. How can I create a action macro to this behavior? (Object = Request Workflow Task).
  7. Hi guys, I have this scenario on my enviroment: On the task 1, if the status is APP then the two next tasks should be canceled. If the status on the 1st task is APP2 then the next task should be pending. How can I create a action macro to this behavior? (Object = Request Workflow Task).
  8. thiago23oliveira

    Cancel Workflow Tasks on New Status

    Hi guys, I have this scenario on my enviroment: On the task 1, if the status is APP then the two next tasks should be canceled. If the status on the 1st task is APP2 then the next task should be pending. How can I create a action macro to this behavior?
  9. thiago23oliveira

    Update Workflow Task From Another Task

    Hi guys, I have this scenario on my enviroment: On the task 1, if the status is APP then the two next tasks should be canceled. If the status on the 1st task is APP2 then the next task should be pending. How can I create a action macro to this behavior?
  10. Hi BrianM, I want to use without the comma, just like this: James Smith. How the factory code is?
  11. thiago23oliveira

    Root Cause Filter

    Hi my friend, Can you show how you create this 2 new factorys?
  12. thiago23oliveira

    Root Cause Filter

    Hi guys, Do you guys have the code for dtlHier macro for this case?
  13. Hi guys, I've to create a PreSaveTrigger to control the type of the ticket and the rootcause filled by the analysts. I've created the followed rootcauses: If the ticket is an incident then the rootcause starts with INC.% If the ticket is a request then the rootcause starts with SOL.% What I need to do is create a PreSaveTrigger to prevent the analysts don't save the tickets with wrong rootcause, just like: Request with rootcause starts with INC.% and Incident with rootcause starts with SOL.% I already have on my detail_in.htmpl a PreSaveTrigger created to control the description lenght, code is: function preSaveTrigger() { if ( _dtl.edit) { AlertMsg = ""; var f = document.main_form; //Verifica se a descrição tem mais de 5 caracteres var zs_descricao = "SET.description"; if (typeof f.elements[zs_descricao] != "undefined") { if (f.elements[zs_descricao].value.length < 5) { detailReportValidation(f.elements[zs_descricao], 1, "A descrição deve conter no mínimo 5 caracteres"); } else { detailReportValidation(f.elements[zs_descricao], 0, ""); } } if (AlertMsg != "") { showAlertMsg(false, false); return false; } else { return true; } } } I need to change this code, or create a new one? How can I do to prevent this case?
  14. thiago23oliveira

    Set change order status when all tasks are approved

    Thank you so much, cdtj. It's works. Now I will try to change the code to when one task are rejected, then the CO goes to other status. Is it possible?
  15. thiago23oliveira

    Set change order status when all tasks are approved

    Hi cdtj, Take a look if my steps are correct: 1º) Create the files: z_new_evt.spl / z_status_change.mod / z_status_change.spl 2º) Create an event with 15 secs delay to attach an action macro with the code: evt::z_new_evt('CHG2APP', chg.persistent_id); It's right? I'm so sorry, I'm new on CA SDM, so your help will be very valious for me. Thank you so much again.
×