Automatically Attach an Asset/CI to a Change Order or Issue

To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.

Overview

This article provides instructions for automatically attaching an Asset or Configuration Item to a Change Order or Issue if the desired condition exists.

Procedures

Step 1. Create the script

A script is created as an .spl file and placed in the $NX_ROOT/site/mods/majic directory. When the Service Desk service starts, the contents of the majic directory are processed and cached. You can use any naming scheme you like for your .spl file, but it is recommended that the file be preceded with a 'z' for easy identification as a custom file (eg zMyCompany.spl, zcr_scripts.spl, zMyScripts.spl).

<source lang="javascript">// Use 'chg' for Change Orders and 'iss' for Issues chg::zmyscript(...) { object group_leader_lrel; object lrel; send_wait(0, top_object(), "get_co_group"); group_leader_lrel = msg[0]; send_wait(0, top_object(), "call_attr", "lrel1", "get_new_dob", NULL, NULL, group_leader_lrel); lrel = msg[0]; lrel.lpid = persistent_id; lrel.lattr = "asset"; // Enter the Asset/CI persid lrel.rpid = "nr:987654321"; // Use 'chgnr' for Change Orders and 'issnr' for Issues. lrel.rattr = "chgnr"; send_wait(0, group_leader_lrel, "checkin"); }</source>

The trigger that will be created in step 2 is the first level filtering. If you need further filtering then utilize an if statement in the spel code above.

Step 2. Create the trigger

This step is to create the trigger that will initiate the script. The methods used to implement the trigger vary based on the Service Desk release. In the examples to follow, the script is run when a new record is created or when a specific category is used.

POST_VALIDATE zmyscript() 111 FILTER(EVENT("INSERT"));
POST_VALIDATE zmyscript() 111 FILTER(category=='MYCAT');

For older releases triggers are made by creating a .mod file and placing it in the $NX_ROOT/site/mods/majic directory. Name the .mod anything you like, but it is recommended that it be preceded with a 'z'.

<source lang="javascript">OBJECT chg {

 TRIGGERS {
   POST_VALIDATE zmyscript() 111 FILTER(EVENT("INSERT"));
 };

}; OBJECT iss {

 TRIGGERS {
   POST_VALIDATE zmyscript() 111 FILTER(category=='MYCAT');
 };

};</source>

Step 3. Publish the Schema changes

The methods used to publish schema changes vary based on the Service Desk release.

For r11.x releases, follow these steps:

1. Save your Schema changes
2. Stop the Service Desk service
3. Run pdm_publish from a command line
4. Start the Service Desk service

For older release recycle the Service Desk service.