Jump to content

Search the Community

Showing results for tags 'customizations'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • CA Service Desk Manager
    • General Discussions
    • Customizations / Modifications
    • Bugs / Errors / Patches
    • Knowledge Tools / Keyword Search
    • Support Automation
    • CMDB
    • Install / Migrate / Configure
    • Product Integration
    • Reporting
    • Workflow
  • Nimsoft Service Desk
    • General
  • General
    • Wiki Article Discussions
    • ITIL & Best Practices
    • Speak Out
    • Employment Opportunities


  • Getting Started
  • Installation
  • Configuration
  • Customization
  • Integration
    • CA Applications
    • Non-CA Applications
    • Custom Integrations
  • Reporting
  • Miscellaneous

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 5 results

  1. Hi my friends, At these days I have a need to force all the analysts to register the solution in all tickets that he's working with. So I made this customization below, maybe this should help someone. _____________________________________________________________________________________________ 1. Create a file "zcr_force_soln.spl" (put on $NXROOT/site/mods/majic) cr::zcr_force_soln(...){ send_wait( 0, this, "get_attr_vals",1,"soln_log.length"); if (msg_error()) { logf(ERROR, "Erro no campo soln_log.length de %s %s - %s", type, ref_num, msg[0]); return; } int zsoln_length; zsoln_length = msg[3]; if (zsoln_length == 0) { string zmsg; zmsg=format("Preencha a 'Solução' antes de mudar este %s para fechado.", type.sym); set_error(1); set_return_data(zmsg); } } 2. Open WSP > Schema Designer - Search for table CR > Advanced > Site defined trigger PRE_VALIDATE zcr_force_soln() 111 FILTER(status{-> 'RE'}); At this case, the solution is mandatory to status "Resolved" 3. Save and publish; 4. Restart the CA SDM services;
  2. This document will show how to create new hiersel, hierload and new factories to table rootcause (rc). On this example I'm using the rootcause categorys to request and incidents on detail_in.htmpl. 1º) Create 2 new columns on table rootcause (z_cr_flag and z_in_flag - INTEGER); 2º) Create 2 new factorys with .mod files just like below: <After install this files, you must restart the CA SDM services> File: rc_cr.mod OBJECT rc { FACTORY rc_cr{ RESTRICT "z_cr_flag = 1 " { z_cr_flag=1}; STANDARD_LISTS { MLIST OFF; RLIST OFF; SORT_BY "sym"; }; REL_ATTR persistent_id; COMMON_NAME sym; }; }; File: rc_in.mod OBJECT rc { FACTORY rc_cr{ RESTRICT "z_in_flag = 1 " { z_in_flag=1}; STANDARD_LISTS { MLIST OFF; RLIST OFF; SORT_BY "sym"; }; REL_ATTR persistent_id; COMMON_NAME sym; }; }; 3º) Create new files: hiersel_rc_cr.htmpl and hierload_rc_cr.htmpl ||| hiersel_rc_in.htmpl and hierload_rc_in.htmpl <You can copy the default files of rc -- hiersel_rc.htmpl and hierload_rc.htmpl -- this files could be located at $NXROOT\bopcfg\www\htmpl\default > After copy the files and rename them, put the new files at $NXROOT\site\mods\www\htmpl\default You must change the factory on each one of them, effectly the change must be applied on this part of the code: hiersel_rc_cr.htmpl and hierload_rc_cr.htmpl <PDM_LIST PREFIX=list FACTORY=rc_cr WHERE="${args.KEEP.HierWc:}" hiersel_rc_in.htmpl and hierload_rc_in.htmpl <PDM_LIST PREFIX=list FACTORY=rc_in WHERE="${args.KEEP.HierWc:}" 4º) On detail_in.htmpl you must add the follow code to separate each factories: <PDM_IF "$args.zType2" == "I"> <PDM_MACRO name=dtlHier hdr="Categoria de fechamento" attr=rootcause factory=rc_in autofill="no"> <PDM_ELIF "$args.zType2" == "R"> <PDM_MACRO name=dtlHier hdr="Categoria de fechamento" attr=rootcause factory=rc_cr autofill="no"> </PDM_IF> zType2 is the attribute that controls the type of the ticket (Incident or Request). all_files.zip
  3. Hello. I've never customized Service Desk Manager web forms before and could use some guidance. My ultimate goal is to ... 1) Detect when the value of the "Need By Date" of a Change Order is updated. 2) Based on the number of days difference between the system date/time and the value of the "Need By Date", set the Priority to a specific value. Pertaining to a copy of the detail.chg.htpml file, here is what I've done so far ... 1) In the section of the code where all the PDM_MACRO lines are, I added the following code to invoke a function when the value of "Need By Date" changes. <PDM_MACRO name=dtlDate hdr="Need By Date" attr=need_by evt="onChange=\\\"set_priority_using_need_by_date()\\\""> 2) Next, in the java script section, I added a new function to test if I could invoke it. Here is my test code. function set_priority_using_need_by_date() { showAlertMessage("Function Invoked", true); } I then backed up the current htpml file in the analyst folder, then copied in the one that I modified. I did a pdm_webcache from a cmd prompt as well. When I access the modified Change Order page from the GUI, I get an error message. AHD04622:Undefined arguments EVT supplied to PDM_MACRO DTLDATE In the std log, it has AHD04622:Undefined arguments EVT supplied to PDM_MACRO DTLDATE at detail_chg.htmpl[503]. I'm a bit lost on this. Can someone advise me on what I might be doing wrong? Much appreciated. Thank You.
  4. Hello, Does anyone know how to show directly the search results without showing the filter first? I am trying to skip the filter when I click on the search tickets menu. Thanks in advance! Ira
  5. I would like to reload the detail form once the tenant value is entered in detail page. Basically, I would like show or hide the form fields depends on the Tenant , On new page before saving the form. any sample examples with the code will help. Thank you!
  • Create New...