Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


cdtj last won the day on February 22

cdtj had the most liked content!

Community Reputation

25 Excellent

About cdtj

  • Rank
    Level 7 Contributor
  • Birthday 01/01/1970

Contact Methods

  • Skype

Profile Information

  • Location
  • Interests
    looking for the fulltime job or remote one

Recent Profile Visitors

1,096 profile views
  1. URGENT !! Blank Notification Issue!!

    if youre triggering notification from Activity you should access fields through related object, eg: @{call_req_id.description} (or change_id, or issue_id) but if youre triggering from Event, it populating notification directly from itself, so you can access attributes directly: @{description} @{summary}, etc.
  2. Cab Approval

    you need to know: - spel basics; - vanilla javascript, jquery basics. I have list of tasks like Approval, Implementation, User testing, etc. Then I have registered trigger for that tasks, once task switch status from WAIT to PEND, trigger fires some activity to change chg's status. Whole logic contains ~2000 lines of spel and js code.
  3. Cab Approval

    hi, in our env we have implemented behaviour when Change's status can't be changed manually and depends by current tasks. So chg will not go furthur until all tasks for specified status will be completed. Regards, cdtj
  4. sound like a huge security issue and would be better if CA fix it globally, could you open a CA Support ticket about this? ca sdm uses javascript to generate inputs, so you can manually modify form generating script (detail_form.js or something like that) and replace unwanted tags with spaces using RegEx.
  5. you can redefine create button using sfStart pdm_macro: https://docops.ca.com/ca-service-management/14-1/en/building/building-ca-service-desk-manager/using-the-web-screen-painter-wsp/pdm-macro-definitions#PDMMacroDefinitions-sfStartas I remember you need to pass own javascript function as extraCreateURL, ex: <PDM_MACRO name=sfStart extraCreateURL="zCreateBREL"> function zCreateBREL() { create_new('z_table', <few attrs like window height/width>, 'PRESET=z_chg:$args.KEEP.chg_id'); } Its a good practice to use KEEP array to pass through id from main form to tab: <PDM_MACRO NAME=tab SRC="OP=SEARCH+FACTORY=z_table+KEEP.chg_id=$args.id...<some_other_params>">
  6. yeah, arrays in spel are very limited
  7. hi, ref_num can be update on insert (new ticket creation) only. If you share your code and error message I can review it. Regards, cdtj
  8. might be obvious but do have repository that marked as default? (Admin tab > Attachments > Repos)
  9. Hi, have you tried to escalate backslashes (c:\\path\\file) or use forward slashes? Regards, cdtj
  10. oh, if I misunderstood you and you want to predefine chg on your custom form you can use PRESET functionallity: // in URL: +PRESET=<attr_name>:<rel_attr> // example, where 12345 is id and z_chg is your attr name: +PRESET=z_chg:12345 // or if you want to predefine chg using chg_ref_num, where 54321 is ref num: +PRESET_REL=z_chg:chg.id:chg_ref_num:54321
  11. hi, there is out-of-the-box thing called notification method, more information could be found here: https://docops.ca.com/ca-service-management/14-1/en/administering/configuring-ca-service-desk-manager/how-to-configure-notifications https://docops.ca.com/ca-service-management/14-1/en/building/building-ca-service-desk-manager/modify-notification-methods#ModifyNotificationMethods-TheNotificationProcess
  12. change means chg (Change Order), feels like there should be nothing special and simple dtlLookup macro without any other params should trigger autocompletion. <PDM_MACRO name=dtlLookup hdr="Change Order" attr="chg">
  13. Hi, chg's outer key is id (type integer), so you need to fill it with change id, and then refer as: <change_attribute>.chg_ref_num How do you creating an entry in your custom table? Regards, cdtj
  14. check browser console (hotkey F12) for errors
  15. hi, i think you can avoid spell in this scenario, you can simply define zbgt_summary_check on form level. if you're creating activity (alg) using OP=UPDATE+FACTORY=cr (used in transfer, status change, escalate, etc) you can specify attr as: docWriteln('<input name="SET.zbgt_summary_check" id="zbgt_summary_check" value="${args.zbgt_summary_check}">'); and if you're using OP=CREATE_NEW+FACTORY=alg like it used in log comment, code will be: docWriteln('<input name="SET.call_req_id.zbgt_summary_check" id="zbgt_summary_check" value="${args.call_req_id.zbgt_summary_check}">'); js part: function preSaveTrigger() { if (someErrorStatement) { alert("some error message"); return false; } else { alert("DEBUG: Setting 400001 to zbgt_summary_check"); jq("#zbgt_summary_check").val(400001); return true; } } preSaveTrigger triggers when user click Save button. Regards, cdtj