Conditionally Attach an Event - Revision history

Gityerfix at 22:21, 3 December 2008

2008-12-03T22:21:05Z

Gityerfix: /* Step 1. Create the script */

2008-07-31T02:34:59Z

‎Step 1. Create the script

Gityerfix at 14:02, 27 July 2008

2008-07-27T14:02:07Z

Gityerfix at 03:21, 27 July 2008

2008-07-27T03:21:38Z

Gityerfix at 06:36, 26 July 2008

2008-07-26T06:36:05Z

Gityerfix: /* Step 2. Create the trigger */

2008-07-18T16:03:43Z

‎Step 2. Create the trigger

Gityerfix at 15:34, 18 July 2008

2008-07-18T15:34:31Z

Gityerfix at 17:37, 30 June 2008

2008-06-30T17:37:45Z

Gityerfix: /* Step 1. Create the script */

2008-06-23T21:42:48Z

‎Step 1. Create the script

Gityerfix: /* Step 1. Create the script */

2008-03-18T17:39:01Z

‎Step 1. Create the script

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Customizations]]
 {{Global Header}}
 {{Global Announcement}}

@@ Line 11: / Line 11: @@
 {{Create Spell Script}}
-<source lang="javascript">// User 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
+<source lang="javascript">// Use 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
 cr::zmyscript(...){
 object group_leader;

@@ Line 9: / Line 9: @@
 == 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).
+{{Create Spell Script}}
 <source lang="javascript">// User 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
@@ Line 54: / Line 54: @@
 === Step 3. Publish the Schema changes ===
-The methods used to publish schema changes vary based on the Service Desk release.
+{{Publish Schema Change}}
-''For r11.x releases'', follow these steps:
+== See Also ==
-#Save your Schema changes
+[[Automatically Remove Attached Events]]
-#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.

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Customizations]]
-<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
+{{Global Header}}
-To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>
+{{Global Announcement}}
 == Overview ==

@@ Line 1: / Line 1: @@
 This article provides instructions for having an event conditionally attached to a ticket.
-== Step 1. Create the script ==
+== Procedures ==
 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).
@@ Line 29: / Line 36: @@
 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 ==
+=== 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 [[Events and Macros|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 '''[[Call Req Table|cr (Request)]]''', '''[[Change Request Table|chg (Change Order)]]''', or '''[[Issue Table|iss (Issue)]]''' table.
   POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});
 ''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 file|.mod]] anything you like, but it is recommended that it be preceded with a 'z'.
@@ Line 48: / Line 53: @@
 };</source>
-== Step 3. Publish the Schema changes ==
+=== Step 3. Publish the Schema changes ===
 The methods used to publish schema changes vary based on the Service Desk release.
@@ Line 58: / Line 63: @@
 ''For older release'' recycle the Service Desk service.

← Older revision		Revision as of 16:03, 18 July 2008
Line 30:		Line 30:

	== Step 2. Create the trigger ==		== 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~~\|~~event~~]].	+	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 [[Events and Macros\|Event]].

@@ Line 2: / Line 2: @@
 == 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).
+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">// User 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
@@ Line 27: / Line 27: @@
 }</source>
-The trigger that will be created in step 2 is the first level filtering. If you need further filtering then utilize an [[If|if statement]] in the [[spel code]] above.
+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|event]].
+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|event]].
@@ Line 37: / Line 37: @@
-<font color="blue">For older releases</font> triggers are made by creating a [[.mod file]] and placing it in the [[NX_ROOT]]/site/mods/majic directory. Name the [[.mod file|.mod]] anything you like, but it is recommended that it be preceded with a 'z'.
+<font color="blue">For older releases</font> triggers are made by creating a [[.mod file]] and placing it in the [[$NX_ROOT]]/site/mods/majic directory. Name the [[.mod file|.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

@@ Line 6: / Line 6: @@
 <source lang="javascript">// User 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
 cr::zmyscript(...){
-object group_leader1;
+object group_leader;
-object attached_events_table_record1;
+object attached_events_table_record;
 send_wait(0, top_object(), "get_co_group");
 if (msg_error()) {
 logf(ERROR, "%s - %s", ref_num, msg[0]);
+}
-group_leader1 = msg[0];
+group_leader = msg[0];
-send_wait( 0, top_object(), "call_attr", "atev", "get_new_dob", NULL, NULL, group_leader1);
+send_wait( 0, top_object(), "call_attr", "atev", "get_new_dob", NULL, NULL, group_leader);
 if (msg_error()) {
 logf(ERROR, "%s - %s", ref_num, msg[0]);
+}
-attached_events_table_record1 = msg[0];
+attached_events_table_record = msg[0];
-attached_events_table_record1.obj_id = persistent_id;
+attached_events_table_record.obj_id = persistent_id;
 // Enter the persid of the event
-attached_events_table_record1.event_tmpl = "evt:400001";
+attached_events_table_record.event_tmpl = "evt:400001";
-send_wait(0, group_leader1, "checkin");
+send_wait(0, group_leader, "checkin");
 if (msg_error()) {
 logf(ERROR, "%s - %s", ref_num, msg[0]);