Difference between revisions of "Automatically Set Assignee to Closing Analyst"
From SDU
(→Step 2. Create the trigger) |
|||
| Line 1: | Line 1: | ||
[[Category:Customizations]] | [[Category:Customizations]] | ||
| − | 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 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 == | ||
| − | 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). |
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->// Use 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues<br>cr::zmyscript(...){<br>if(is_null(assignee)){<br>// Use 'int' in place of 'uuid' in the line below if for pre-r11 releases<br>uuid userid;<br>send_wait(0, top_object(), "call_attr", "cr", "current_user_id");<br>userid = msg[0];<br>assignee = userid;<br>}<br>};<!--c2--></div><!--ec2--> | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->// Use 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues<br>cr::zmyscript(...){<br>if(is_null(assignee)){<br>// Use 'int' in place of 'uuid' in the line below if for pre-r11 releases<br>uuid userid;<br>send_wait(0, top_object(), "call_attr", "cr", "current_user_id");<br>userid = msg[0];<br>assignee = userid;<br>}<br>};<!--c2--></div><!--ec2--> | ||
| − | 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. |
<br> | <br> | ||
== 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. | + | 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. |
<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 (Request)''', '''chg (Change Order)''', or '''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 (Request)''', '''chg (Change Order)''', or '''iss (Issue)''' table. | ||
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};<!--c2--></div><!--ec2--> | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};<!--c2--></div><!--ec2--> | ||
<br> | <br> | ||
| − | <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 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'. |
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->MODIFY cr POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};<br><br>MODIFY chg status POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};<br><br>MODIFY iss status POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};<!--c2--></div><!--ec2--> | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->MODIFY cr POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};<br><br>MODIFY chg status POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};<br><br>MODIFY iss status POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};<!--c2--></div><!--ec2--> | ||
| Line 28: | Line 28: | ||
#Save your Schema changes | #Save your Schema changes | ||
#Stop the Service Desk service | #Stop the Service Desk service | ||
| − | #Run pdm_publish from a command line | + | #Run [[pdm_publish]] from a command line |
#Start the Service Desk service | #Start the Service Desk service | ||
<font color="blue">For older release</font> recycle the Service Desk service. | <font color="blue">For older release</font> recycle the Service Desk service. | ||
<br> | <br> | ||
Revision as of 03:42, 17 January 2008
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).
CODE
// Use 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
cr::zmyscript(...){
if(is_null(assignee)){
// Use 'int' in place of 'uuid' in the line below if for pre-r11 releases
uuid userid;
send_wait(0, top_object(), "call_attr", "cr", "current_user_id");
userid = msg[0];
assignee = userid;
}
};
cr::zmyscript(...){
if(is_null(assignee)){
// Use 'int' in place of 'uuid' in the line below if for pre-r11 releases
uuid userid;
send_wait(0, top_object(), "call_attr", "cr", "current_user_id");
userid = msg[0];
assignee = userid;
}
};
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.
For r11.x releases triggers are created via the Schema Designer utility. Simply add the following code as a Site-Defined Trigger to the cr (Request), chg (Change Order), or iss (Issue) table.
CODE
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 anything you like, but it is recommended that it be preceded with a 'z'.
CODE
MODIFY cr POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};
MODIFY chg status POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};
MODIFY iss status POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};
MODIFY chg status POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};
MODIFY iss status POST_VALIDATE zmyscript() 111 FILTER(EVENT("UPDATE") && status{->'CL'};
Step 3. Publish the Schema changes
The methods used to publish schema changes vary based on the Service Desk release.
For r11.x releases, follow these steps:
- Save your Schema changes
- Stop the Service Desk service
- Run pdm_publish from a command line
- Start the Service Desk service
For older release recycle the Service Desk service.
