Make a Field Conditionally Required - Revision history

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

2010-06-04T16:26:16Z

‎Step 1. Create the script

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

2009-01-05T20:04:44Z

‎Step 2. Create the trigger

Gityerfix at 22:20, 3 December 2008

2008-12-03T22:20:01Z

Gityerfix at 04:13, 27 July 2008

2008-07-27T04:13:35Z

Gityerfix at 05:14, 26 July 2008

2008-07-26T05:14:16Z

Gityerfix at 04:49, 26 July 2008

2008-07-26T04:49:01Z

Gityerfix at 17:00, 18 July 2008

2008-07-18T17:00:56Z

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

2008-06-30T17:27:23Z

‎Step 1. Create the script

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

2008-06-30T17:11:48Z

‎Step 2. Create the trigger

Gityerfix: Changed a few links

2008-03-08T18:15:51Z

Changed a few links

@@ Line 17: / Line 17: @@
 cr::zmyscript(...) {
 string zmsg;
-// Enter an if statement
+// Enter an if statement, the string1 value should be replaced with the field you want required, for example "impact" for a change order
 if(is_null(string1)) {
 // Enter an alert message that appears when the if statement is fulfilled

@@ Line 40: / Line 40: @@
 OBJECT cr {
    TRIGGERS {
-     POST_VALIDATE zmyscript() 111 FILTER(active==0);
+     PRE_VALIDATE zmyscript() 111 FILTER(active==0);
    };
 };</source>

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

@@ 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 making a field conditionally required. The example that follows makes a field conditionally required when a ticket is being closed. However, the concept of this customization could be expanded to make a field required only if the condition has been fulfilled.
 == Procedures ==
@@ Line 24: / Line 23: @@
+}
 }</source>
 === Step 2. Create the trigger ===
@@ Line 42: / Line 40: @@
    };
 };</source>
 === Step 3. Publish the Schema changes ===

@@ Line 1: / Line 1: @@
 [[Category:Customizations]]
 This article provides instructions for making a field conditionally required. The example that follows makes a field conditionally required when a ticket is being closed. However, the concept of this customization could be expanded to make a field required only if the condition has been fulfilled.
 == 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 18: / Line 25: @@
 }</source>
 == 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.
 ''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'.
@@ Line 37: / Line 43: @@
 };</source>
 == Step 3. Publish the Schema changes ==
 The methods used to publish schema changes vary based on the Service Desk release.
@@ Line 47: / Line 54: @@
 ''For older release'' recycle the Service Desk service.

@@ Line 1: / Line 1: @@
 This article provides instructions for making a field conditionally required. The example that follows makes a field conditionally required when a ticket is being closed. However, the concept of this customization could be expanded to make a field required only if the condition has been fulfilled.
@@ Line 21: / 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 '''[[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 39: / Line 40: @@
 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 45: / Line 46: @@
 #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>

← Older revision		Revision as of 17:11, 30 June 2008
Line 26:		Line 26:


−	<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		<source lang="javascript">// Use OBJECT cr for Requests, Incidents & Problems

← Older revision		Revision as of 18:15, 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.
	PRE_VALIDATE zmyscript() 111 FILTER(active==0);		PRE_VALIDATE zmyscript() 111 FILTER(active==0);