Automatically Remove Attached Events - Revision history

Gityerfix: Added status_flag to query for improved efficiency.

2008-12-05T22:40:21Z

Added status_flag to query for improved efficiency.

Gityerfix at 20:04, 28 October 2008

2008-10-28T20:04:49Z

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

2008-10-28T20:02:15Z

‎Step 1. Create the script

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

2008-10-28T20:00:24Z

‎Step 1. Create the script

Gityerfix at 14:04, 27 July 2008

2008-07-27T14:04:40Z

Gityerfix at 04:10, 27 July 2008

2008-07-27T04:10:09Z

Gityerfix at 06:51, 26 July 2008

2008-07-26T06:51:15Z

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

2008-07-18T16:06:52Z

‎Step 2. Create the trigger

Gityerfix at 16:04, 18 July 2008

2008-07-18T16:04:50Z

Gityerfix at 15:55, 18 July 2008

2008-07-18T15:55:44Z

@@ Line 26: / Line 26: @@
          // 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);
+	wc = format("(event_tmpl = 'evt:400001' OR event_tmpl = 'evt:400002') AND obj_id = '%s' AND status_flag = 2", persistent_id);
 	send_wait(0, top_object(), "call_attr", "atev", "sync_fetch", "STATIC", wc, -1, 0);

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

@@ Line 24: / Line 24: @@
 	atev_count = msg[1];
-	if (c_count > 0) {
+	if (atev_count > 0) {
 		for (i=0;i<atev_count;i++) {
 			send_wait(0, top_object(), "get_co_group");

@@ Line 13: / Line 13: @@
 <source lang="javascript">// Use 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
 cr::zmyscript(...){
-// Add additional event_tmpl arguments to the following line if needed.
+	object atev_dob, atev_list, group_leader;
-send_wait(0, top_object(), "call_attr", "atev", "sync_fetch", "STATIC", format("(event_tmpl = 'evt:400001' OR event_tmpl = 'evt:400002') AND obj_id = '%s'", persistent_id), -1, 0);
+	string wc;
-if (msg_error()) {
+	int atev_count, i;
-set_error(msg_error());
-set_return_data(msg[0]);
-logf(ERROR, "Cannot get attached events for %s %s - %s", type.sym, ref_num, msg[0]);
-//logf(ERROR, "Cannot get attached events for Change Order %s - %s", chg_ref_num, msg[0]);
-//logf(ERROR, "Cannot get attached events for Issue %s - %s", ref_num, msg[0]);
-return;
-} else {
-logf(SIGNIFICANT, "Got atev list for %s %s", type.sym, ref_num);
-//logf(SIGNIFICANT, "Got atev list for Change Order %s", chg_ref_num);
-//logf(SIGNIFICANT, "Got atev list for Issue %s", ref_num);
-−
-// Building attached event list from query results
+        // Identify the persids of the events to be deleted.
-object atev_list;
+	wc = format("(event_tmpl = 'evt:400001' OR event_tmpl = 'evt:400002') AND obj_id = '%s'", persistent_id);
-atev_list = msg[0];
-int thelength;
-thelength = 0;
-thelength = msg[1];
-if (msg_error()) {
-logf(ERROR, "error getting length of atev list for %s %s - %s", type.sym, ref_num, msg[0]);
-//logf(ERROR, "error getting length of atev list for Change Order %s - %s", chg_ref_num, msg[0]);
-//logf(ERROR, "error getting length of atev list for Issue %s - %s", ref_num, msg[0]);
-return;
-} else {
-logf(SIGNIFICANT, "event list length = %d for %s %s", thelength, type.sym, ref_num);
-//logf(SIGNIFICANT, "event list length = %d for Change Order %s", thelength, chg_ref_num);
-//logf(SIGNIFICANT, "event list length = %d for Issue %s", thelength, ref_num);
-−
-// Canceling all events from list
+	send_wait(0, top_object(), "call_attr", "atev", "sync_fetch", "STATIC", wc, -1, 0);
-long index;
+	atev_list = msg[0];
-int i;
+	atev_count = msg[1];
-i=0;
-for (i; i<thelength; i++) {
+	if (c_count > 0) {
-send_wait(0, atev_list, "dob_by_index", "DEFAULT", i, i);
+		for (i=0;i<atev_count;i++) {
-if (msg_error()) {
+			send_wait(0, top_object(), "get_co_group");
-logf(ERROR, "error getting dob_by_index for %s %s - %s", type.sym, ref_num, msg[0]);
+			group_leader = msg[0];
-//logf(ERROR, "error getting dob_by_index for Change Order %s - %s", chg_ref_num, msg[0]);
-//logf(ERROR, "error getting dob_by_index for Issue %s - %s", ref_num, msg[0]);
+			send_wait(0, atev_list, "dob_by_index", "DEFAULT", i, i);
-return;
+			atev_dob = msg[0];
-−
-object to_delete;
+			send_wait(0, group_leader, "checkout", atev_dob);
-to_delete = msg[0];
+			send_wait(0, atev_dob, "cancel_me");
-send_wait(0, to_delete, "cancel_me");
+			send_wait(0, group_leader, "checkin");
-if (msg_error()) {
+			if (msg_error()) {
-logf(ERROR, "error deleting event %d for %s %s - %s", i, type.sym, ref_num, msg[0]);
+				logf(ERROR, "error cancelling event for %s %s - %s", type.sym, ref_num, msg[0]);
-//logf(ERROR, "error deleting event %d for Change Order %s - %s", i, chg_ref_num, msg[0]);
+				// logf(ERROR, "error cancelling event for CO %s - %s", chg_ref_num, msg[0]);
-//logf(ERROR, "error deleting event %d for Issue %s - %s", i, ref_num, msg[0]);
+				// logf(ERROR, "error cancelling event for Issue %s - %s", ref_num, msg[0]);
-return;
+			} else {
-} else {
+				logf(SIGNIFICANT, "successfully canceled event for %s %s", type.sym, ref_num);
-logf(SIGNIFICANT, "successfully canceled event %d for %s %s", i, type.sym, ref_num);
+				// logf(SIGNIFICANT, "successfully canceled event for CO %s", chg_ref_num);
-//logf(SIGNIFICANT, "successfully canceled event %d for Change Order %s", i, chg_ref_num);
+				// logf(SIGNIFICANT, "successfully canceled event for Issue %s", ref_num);
-//logf(SIGNIFICANT, "successfully canceled event %d for Issue %s", i, ref_num);
-−
+		}
-−
+	}
 }</source>

@@ 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">// Use 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
@@ Line 94: / Line 94: @@
 === 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
+[[Conditionally Attach an Event]]
-#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: @@
 This article provides instructions for having attached [[Events and Macros|Events]] automatically removed.
-== 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 68: / Line 75: @@
 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(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 file|.mod]] anything you like, but it is recommended that it be preceded with a 'z'.
@@ Line 88: / Line 93: @@
 };</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 98: / Line 103: @@
 ''For older release'' recycle the Service Desk service.

← Older revision		Revision as of 16:06, 18 July 2008
Line 69:		Line 69:

	== 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]].

← Older revision		Revision as of 16:04, 18 July 2008
Line 1:		Line 1:
−	This article provides instructions for having attached [[~~Event~~\|Events]] automatically removed.	+	This article provides instructions for having attached [[Events and Macros\|Events]] automatically removed.

	== Step 1. Create the script ==		== Step 1. Create the script ==

@@ Line 72: / Line 72: @@
-<font color="blue">For r11.x releases</font> 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.
+''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(EVENT("UPDATE") && status{'RE'->} && active != 0);
-<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'.
+''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'.
 <source lang="javascript">// Use OBJECT cr for Requests, Incidents & Problems
@@ Line 91: / Line 91: @@
 The methods used to publish schema changes vary based on the Service Desk release.
-<font color="blue">For r11.x releases</font>, follow these steps:
+''For r11.x releases'', follow these steps:
 #Save your Schema changes
 #Stop the Service Desk service
@@ Line 97: / Line 97: @@
 #Start the Service Desk service
-<font color="blue">For older release</font> recycle the Service Desk service.
+''For older release'' recycle the Service Desk service.
 ----
-<div align='center'><font color="red">To make corrections or additions to this article, select the ''edit'' tab above.<br>
+<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
 To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>
 [[Category:Customizations]]