Automatically Set Assignee to Closing Analyst - Revision history

Gityerfix at 04:10, 27 July 2008

2008-07-27T04:10:51Z

Gityerfix at 05:18, 26 July 2008

2008-07-26T05:18:01Z

Gityerfix at 04:59, 26 July 2008

2008-07-26T04:59:43Z

Gityerfix at 16:32, 18 July 2008

2008-07-18T16:32:40Z

Gityerfix at 16:06, 18 July 2008

2008-07-18T16:06:10Z

Gityerfix at 14:59, 18 July 2008

2008-07-18T14:59:11Z

Gityerfix at 17:34, 30 June 2008

2008-06-30T17:34:19Z

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

2008-03-18T17:38:13Z

‎Step 1. Create the script

Gityerfix: Modified links

2008-03-08T19:44:33Z

Modified links

Gityerfix: Reverted edits by Jessie.dore (Talk); changed back to last version by Gityerfix

2008-03-01T03:11:52Z

Reverted edits by Jessie.dore (Talk); changed back to last version by Gityerfix

@@ 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 6: / Line 6: @@
 == Overview ==
 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.
 == Procedures ==
@@ Line 24: / Line 23: @@
 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.
 === Step 2. Create the trigger ===
@@ Line 42: / Line 40: @@
    };
 };</source>
 === 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.
 == 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).
@@ Line 17: / Line 25: @@
 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.
 == 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{->'CL'});
 ''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 36: / Line 43: @@
 };</source>
 == Step 3. Publish the Schema changes ==
 The methods used to publish schema changes vary based on the Service Desk release.
@@ Line 46: / Line 54: @@
 ''For older releases'' recycle the Service Desk service.

← Older revision		Revision as of 16:32, 18 July 2008
Line 1:		Line 1:
−	This article provides instructions for having system generated [[~~Activity\|~~Activities]] set to ''Internal'' so it cannot be viewed by users of the Employee or Customer Interfaces.	+	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 ==		== Step 1. Create the script ==

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

	== 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 21: / Line 21: @@
-<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{->'CL'});
-<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 39: / Line 39: @@
 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 and Publish your Schema changes (under File menu of Schema Designer)
 #Stop the Service Desk service
@@ Line 45: / Line 45: @@
 #Start the Service Desk service
-<font color="blue">For older release</font> recycle the Service Desk service.
+''For older releases'' 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]]

@@ 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">// Use 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
@@ Line 18: / Line 18: @@
 == 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 25: / Line 25: @@
-<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 15: / Line 15: @@
 }</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.
+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.
-−
 == Step 2. Create the trigger ==

← Older revision		Revision as of 19:44, 8 March 2008
Line 22:		Line 22:


−	<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 '''[[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{->'CL'});		POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'});

← Older revision		Revision as of 03:11, 1 March 2008
Line 17:		Line 17:
	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.		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.

−	~~pppp~~

	== Step 2. Create the trigger ==		== Step 2. Create the trigger ==