Difference between revisions of "Automatically Set Assignee to Closing Analyst"
(New page: Category:Customizations This article provides instructions for having system generated Activities set to ''Internal'' so it cannot be viewed by users of the Employee or Customer Interf...) |
(No difference)
|
Revision as of 23:55, 15 January 2008
This article provides instructions for having system generated Activities set to Internal so it cannot be viewed by users of the Employee or Customer Interfaces.
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).
cr::zmyscript(...){
object group_leader1;
object attached_events_table_record1;
send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf(ERROR, "%s - %s", ref_num, msg[0]);
}
group_leader1 = msg[0];
send_wait( 0, top_object(), "call_attr", "atev", "get_new_dob", NULL, NULL, group_leader1);
if (msg_error()) {
logf(ERROR, "%s - %s", ref_num, msg[0]);
}
attached_events_table_record1 = msg[0];
attached_events_table_record1.obj_id = persistent_id;
// Enter the persid of the event
attached_events_table_record1.event_tmpl = "evt:400001";
send_wait(0, group_leader1, "checkin");
if (msg_error()) {
logf(ERROR, "%s - %s", ref_num, msg[0]);
}
}
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.
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'.
MODIFY chg POST_VALIDATE zmyscript() 113 FILTER (status { -> 'RE' } );
MODIFY iss POST_VALIDATE zmyscript() 113 FILTER (status { -> 'RE' } );
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:
- Save your Schema changes
- Stop the Service Desk service
- Run pdm_publish from a command line
- Start the Service Desk service
For older release recycle the Service Desk service.
