Difference between revisions of "Automatically Remove Attached Events"

Revision as of 20:04, 28 October 2008

Overview

This article provides instructions for having attached Events automatically removed.

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 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues cr::zmyscript(...){ object atev_dob, atev_list, group_leader; string wc; int atev_count, i;

       // Identify the persids of the events to be deleted.

wc = format("(event_tmpl = 'evt:400001' OR event_tmpl = 'evt:400002') AND obj_id = '%s'", persistent_id);

send_wait(0, top_object(), "call_attr", "atev", "sync_fetch", "STATIC", wc, -1, 0); atev_list = msg[0]; atev_count = msg[1];

if (atev_count > 0) { for (i=0;i<atev_count;i++) { send_wait(0, top_object(), "get_co_group"); group_leader = msg[0];

send_wait(0, atev_list, "dob_by_index", "DEFAULT", i, i); atev_dob = msg[0];

send_wait(0, group_leader, "checkout", atev_dob); send_wait(0, atev_dob, "cancel_me"); send_wait(0, group_leader, "checkin"); if (msg_error()) { logf(ERROR, "error cancelling event for %s %s - %s", type.sym, ref_num, msg[0]); // logf(ERROR, "error cancelling event for CO %s - %s", chg_ref_num, msg[0]); // logf(ERROR, "error cancelling event for Issue %s - %s", ref_num, msg[0]); } else { logf(SIGNIFICANT, "successfully canceled event for %s %s", type.sym, ref_num); // logf(SIGNIFICANT, "successfully canceled event for CO %s", chg_ref_num); // logf(SIGNIFICANT, "successfully canceled event for Issue %s", ref_num); } } } }</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 trigger is designed to fire if the Status is being changed to 'Resolved'. Use whatever filter you like for attaching your event.

For r11.x releases triggers are created via the Schema Designer utility. Simply add the following code as a Site-Defined Trigger to the cr (Request), chg (Change Order), or iss (Issue) table.

POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{'RE'->} && active != 0);

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">// Use OBJECT cr for Requests, Incidents & Problems // Use OBJECT chg for Change Orders // Use OBJECT iss for Issues OBJECT cr {

 TRIGGERS {
   POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{'RE'->} && active != 0);
 };

};</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 (Applicable if you made changes via WSP)
4. Start the Service Desk service

For older releases recycle the Service Desk service.

See Also

Conditionally Attach an Event