Only Assignee can Close - Revision history

Kowy at 16:42, 26 February 2009

2009-02-26T16:42:56Z

Gityerfix at 04:09, 27 July 2008

2008-07-27T04:09:05Z

Gityerfix at 11:14, 26 July 2008

2008-07-26T11:14:26Z

Gityerfix at 16:58, 18 July 2008

2008-07-18T16:58:37Z

Gityerfix at 17:28, 30 June 2008

2008-06-30T17:28:11Z

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

2008-06-30T17:27:46Z

‎Step 1. Create the script

Gityerfix: Changed a few links

2008-03-08T18:17:08Z

Changed a few links

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

2008-02-20T15:55:07Z

‎Step 2. Create the trigger

Gityerfix at 19:46, 18 February 2008

2008-02-18T19:46:03Z

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

2008-02-14T17:39:00Z

‎Step 1. Create the script

@@ Line 36: / Line 36: @@
 ''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.
-  PRE_VALIDATE zmyscript() 111 FILTER(active==0);
+  POST_VALIDATE zmyscript() 111 FILTER(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 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: @@
 [[Category:Customizations]]
 This article provides instructions for implementing custom functionality that prevents anyone but the Assignee of a ticket from closing it.
-== 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 25: / Line 31: @@
 }</source>
-== 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.
@@ Line 31: / Line 37: @@
 ''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.
   PRE_VALIDATE zmyscript() 111 FILTER(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'.
 <source lang="javascript">// Use OBJECT cr for Requests, Incidents & Problems
 // Use OBJECT chg for Change Orders
@@ Line 44: / Line 48: @@
 };</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 54: / Line 58: @@
 ''For older releases'' recycle the Service Desk service.

@@ Line 1: / Line 1: @@
 This article provides instructions for implementing custom functionality that prevents anyone but the Assignee of a ticket from closing it.
@@ Line 28: / Line 29: @@
-<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.
   PRE_VALIDATE zmyscript() 111 FILTER(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 46: / Line 47: @@
 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 52: / Line 53: @@
 #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>

@@ Line 1: / Line 1: @@
-This article provides instructions for implementing custom functionality that prevents anyone but the [[Assignee]] of a ticket from closing it.
+This article provides instructions for implementing custom functionality that prevents anyone but the Assignee of a ticket from closing it.
 == Step 1. Create the script ==
@@ Line 32: / Line 32: @@
-<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 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

← Older revision		Revision as of 18:17, 8 March 2008
Line 28:		Line 28:


−	<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.
	PRE_VALIDATE zmyscript() 111 FILTER(active==0);		PRE_VALIDATE zmyscript() 111 FILTER(active==0);

@@ Line 34: / Line 34: @@
 <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(active==0);
+// Use OBJECT iss for Issues
-  };
+OBJECT cr {
-};
-OBJECT chg {
-  TRIGGERS {
-    POST_VALIDATE zmyscript() 111 FILTER(active==0);
-  };
-};
-OBJECT iss {
    TRIGGERS {
      POST_VALIDATE zmyscript() 111 FILTER(active==0);

@@ Line 4: / Line 4: @@
 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 Change Orders, and 'iss' for Issues
+<source lang="javascript">// Use 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
-cr::zmyscript(...) {
+cr::zmyscript(...){
 string zmsg;
-if(assignee.userid != cst.userid) {
+// Use 'int' in place of 'uuid' in the line below if for pre-r11 releases
 //Enter your alert message that appears when the if statement is fulfilled
-zmsg=format(" Assignee must be the same as the logged in user in order to close %s", ref_num);
+zmsg=format(" Assignee must be the same as the logged in user in order to close %s %s", type.sym, ref_num);
 set_error(1);
 set_return_data(zmsg);