Difference between revisions of "Automatically Set System Generated Activities to Internal"
(→Step 2. Create the trigger) |
m |
||
| (18 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | __NOTOC__ | ||
| + | [[Category:Change Orders]] | ||
[[Category:Customizations]] | [[Category:Customizations]] | ||
| − | + | [[Category:Incidents]] | |
| + | [[Category:Issues]] | ||
| + | [[Category:Problems]] | ||
| + | [[Category:r6]] | ||
| + | [[Category:r11]] | ||
| + | [[Category:Requests]] | ||
| + | [[Category:Schema Changes]] | ||
| + | {{Global Header}} | ||
| + | {{Global Announcement}} | ||
| − | == | + | == 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 == | |
| − | + | === Step 1. Create the script === | |
| + | {{Create Spell Script}} | ||
| − | == Step 2. Create the trigger == | + | <source lang="javascript">// Use 'alg' for Requests, Incidents & Problems, 'chgalg' for Changes, and 'issalg' for Issues |
| + | alg::zmyscript(...) { | ||
| + | send_wait(0, this, "call_attr", "internal", "set_val", "1", "SURE_SET"); | ||
| + | if (msg_error()) { | ||
| + | logf(ERROR, "error updating alg internal with 1: '%s'", msg[0]); | ||
| + | } | ||
| + | }</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. | 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 '''[[Act Log Table|alg (Request Activity Log)]]''', '''[[Change Act Log Table|chgalg (Change Order Activity Log)]]''', or '''[[Issue Act Log Table|issalg (Issue Activity Log)]]''' tables. | |
| − | + | POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'}); | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | '' | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | < | + | ''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 alg for Requests, Incidents & Problems | |
| − | + | // Use OBJECT chgalg for Change Orders | |
| − | + | // Use OBJECT issalg for IssuesOBJECT alg { | |
| − | + | TRIGGERS { | |
| + | POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'}); | ||
| + | }; | ||
| + | };</source> | ||
| − | + | === Step 3. Publish the Schema changes === | |
| − | + | {{Publish Schema Change}} | |
Latest revision as of 17:58, 13 August 2008
To discuss or ask questions about this article, select the discussion tab above.
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
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">// Use 'alg' for Requests, Incidents & Problems, 'chgalg' for Changes, and 'issalg' for Issues alg::zmyscript(...) { send_wait(0, this, "call_attr", "internal", "set_val", "1", "SURE_SET"); if (msg_error()) { logf(ERROR, "error updating alg internal with 1: '%s'", msg[0]); } }</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 alg (Request Activity Log), chgalg (Change Order Activity Log), or issalg (Issue Activity Log) tables.
POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});
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'. <source lang="javascript">// Use OBJECT alg for Requests, Incidents & Problems // Use OBJECT chgalg for Change Orders // Use OBJECT issalg for IssuesOBJECT alg {
TRIGGERS {
POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});
};
};</source>
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 (Applicable if you made changes via WSP)
- Start the Service Desk service
For older releases recycle the Service Desk service.
