Automatically Attach an Event - Revision history

Gityerfix: Redirecting to Conditionally Attach an Event

2008-03-04T00:53:21Z

Redirecting to Conditionally Attach an Event

Gityerfix at 00:49, 4 March 2008

2008-03-04T00:49:34Z

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

2008-02-23T23:05:41Z

‎Step 2. Create the trigger

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

2008-02-13T18:39:07Z

‎Step 2. Create the trigger

Gityerfix at 14:57, 27 January 2008

2008-01-27T14:57:54Z

Gityerfix at 14:54, 27 January 2008

2008-01-27T14:54:44Z

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

2008-01-27T14:53:43Z

‎Step 2. Create the trigger

Gityerfix: /* Step 3. Publish the Schema changes */

2008-01-17T03:34:19Z

‎Step 3. Publish the Schema changes

Gityerfix at 03:33, 17 January 2008

2008-01-17T03:33:58Z

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

2008-01-17T03:32:38Z

‎Step 2. Create the trigger

@@ Line 1: / Line 1: @@
-This article provides instructions for having an event conditionally attached to a ticket.
+#REDIRECT [[Conditionally Attach an Event]]
-−
-== 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">// User 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
-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]);
-−
-}</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|event]].
-−
-−
-<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 '''[[cr|cr (Request)]]''', '''[[chg|chg (Change Order)]]''', or '''[[iss|iss (Issue)]]''' table.
- POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});
-−
-−
-<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
-// Use OBJECT chg for Change Orders
-// Use OBJECT iss for Issues
-OBJECT cr {
-  TRIGGERS {
-    POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});
-  };
-};</source>
-−
-== Step 3. Publish the Schema changes ==
-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:
-#Save your Schema changes
-#Stop the Service Desk service
-#Run [[pdm_publish]] from a command line
-#Start the Service Desk service
-−
-<font color="blue">For older release</font> 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>
-To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>
-−
-[[Category:Customizations]]

← Older revision		Revision as of 00:49, 4 March 2008
Line 1:		Line 1:
−	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~~.	+	This article provides instructions for having an event conditionally attached to a ticket.

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

@@ Line 40: / Line 40: @@
 <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">OBJECT cr {
+<source lang="javascript">// Use OBJECT cr for Requests, Incidents & Problems
-  TRIGGERS {
+// Use OBJECT chg for Change Orders
-    POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});
+// Use OBJECT iss for Issues
-  };
+OBJECT cr {
-};
-OBJECT chg {
-  TRIGGERS {
-    POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});
-  };
-};
-OBJECT iss {
    TRIGGERS {
      POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});

@@ Line 32: / Line 32: @@
 == 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]].
 <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 '''[[cr|cr (Request)]]''', '''[[chg|chg (Change Order)]]''', or '''[[iss|iss (Issue)]]''' table.
   POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});
- MODIFY cr POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});
+<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'.
- MODIFY chg POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});
- MODIFY iss POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});
 == Step 3. Publish the Schema changes ==

@@ Line 1: / Line 1: @@
 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.
@@ Line 54: / Line 53: @@
 <font color="blue">For older release</font> recycle the Service Desk service.
 <br>

@@ Line 13: / Line 13: @@
 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]].
-<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 '''[[cr|cr (Request)''', '''[[chg|chg (Change Order)''', or '''[[iss|iss (Issue]])''' table.
+<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 '''[[cr|cr (Request)]]''', '''[[chg|chg (Change Order)]]''', or '''[[iss|iss (Issue)]]''' table.
 <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->POST_VALIDATE zmyscript&#40;&#41; 111 FILTER&#40;status{-&#62;&#39;RE&#39;}&#41;&#59;<!--c2--></div><!--ec2-->