Require a Solution in Order to Resolve - Revision history

Gityerfix at 05:02, 10 August 2008

2008-08-10T05:02:00Z

Gityerfix at 05:01, 10 August 2008

2008-08-10T05:01:30Z

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

2008-08-04T17:02:53Z

‎Step 3. Publish the Schema changes

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

2008-08-04T17:02:23Z

‎Step 1. Create the script

Gityerfix at 00:57, 27 July 2008

2008-07-27T00:57:38Z

Gityerfix at 05:41, 26 July 2008

2008-07-26T05:41:56Z

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

2008-07-18T14:19:01Z

‎Step 3. Publish the Schema changes

Gregg at 05:25, 7 July 2008

2008-07-07T05:25:16Z

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

2008-06-30T17:24:12Z

‎Step 1. Create the script

Gityerfix: New page: This article provides instructions for requiring that a solution be provided prior to setting a ticket to the 'Resolved' Status, This customization works only in r11.x releases. == Step 1...

2008-05-15T17:18:37Z

New page: This article provides instructions for requiring that a solution be provided prior to setting a ticket to the 'Resolved' Status, This customization works only in r11.x releases. == Step 1...

New page

This article provides instructions for requiring that a solution be provided prior to setting a ticket to the 'Resolved' Status, This customization works only in r11.x releases.

== 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">cr::zmyscript(...){
send_wait( 0, this, "get_attr_vals",1,"soln_log.length");
if (msg_error()) {
logf(ERROR, "error getting soln_log.length for %s %s - %s", type, ref_num, msg[0]);
return;
}
int zsoln_length;
zsoln_length = msg[3];
if (zsoln_length == 0) {
string zmsg;
zmsg=format("Provide a 'Solution' before setting this %s to Resolved.", type.sym);
set_error(1);
set_return_data(zmsg);
}
}</source>

== Step 2. Create the trigger ==
This step is to create the trigger that will initiate the script. Use the [[Schema Designer]] utility to add the following code as a [[Site-Defined Trigger]] to the '''[[Call Req Table|cr (Request)]]''' table.
<source lang="javascript">PRE_VALIDATE zmyscript() 111 FILTER(status{-> 'RE'});</source>

== Step 3. Publish the Schema changes ==
Follow these steps for publishing the schema changes:
#Save your Schema changes
#Stop the Service Desk service
#Run [[pdm_publish]] from a command line
#Start 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]]

@@ Line 3: / Line 3: @@
 [[Category:Incidents]]
 [[Category:Problems]]
 [[Category:Requests]]
 [[Category:Schema Changes]]

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

@@ 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">cr::zmyscript(...){
 	send_wait( 0, this, "get_attr_vals",1,"soln_log.length");

@@ 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 ==

← Older revision		Revision as of 05:25, 7 July 2008
Line 1:		Line 1:
−	This article provides instructions for requiring that a solution be provided prior to setting a ticket to the 'Resolved' Status, This customization works only in r11.x releases.	+	This article provides instructions for requiring that a solution be provided prior to setting a ticket to the 'Resolved' Status. This customization works only in r11.x releases.

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

@@ Line 31: / Line 31: @@
 === Step 3. Publish the Schema changes ===
-Follow these steps for publishing the schema changes:
+{{R11 Publish Schema Change}}
-#Save your Schema changes
-#Stop the Service Desk service
-#Run [[pdm_publish]] from a command line
-#Start the Service Desk service

@@ 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">cr::zmyscript(...){
@@ Line 19: / Line 19: @@
+	}
 }</source>
 == Step 2. Create the trigger ==