|
|
| (7 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | [[Category:Customizations]] | + | #REDIRECT [[Conditionally Attach an Event]] |
| − | 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).
| + | |
| − | | + | |
| − | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->// User 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues<br>cr::zmyscript(...){<br>object group_leader1;<br>object attached_events_table_record1;<br>send_wait(0, top_object(), "get_co_group");<br>if (msg_error()) {<br>logf(ERROR, "%s - %s", ref_num, msg[0]);<br>}<br>group_leader1 = msg[0];<br>send_wait( 0, top_object(), "call_attr", "atev", "get_new_dob", NULL, NULL, group_leader1);<br>if (msg_error()) {<br>logf(ERROR, "%s - %s", ref_num, msg[0]);<br>}<br>attached_events_table_record1 = msg[0];<br>attached_events_table_record1.obj_id = persistent_id;<br>// Enter the persid of the event<br>attached_events_table_record1.event_tmpl = "evt:400001";<br>send_wait(0, group_leader1, "checkin");<br>if (msg_error()) {<br>logf(ERROR, "%s - %s", ref_num, msg[0]);<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.
| + | |
| − | <br>
| + | |
| − | | + | |
| − | == 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|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|cr (Request)]]''', '''[[chg|chg (Change Order)]]''', or '''[[iss|iss (Issue)]]''' table.
| + | |
| − | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});<!--c2--></div><!--ec2-->
| + | |
| − | | + | |
| − | <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(status{->'RE'});<br><br>MODIFY chg POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});<br><br>MODIFY iss POST_VALIDATE zmyscript() 111 FILTER(status{->'RE'});<!--c2--></div><!--ec2-->
| + | |
| − | <br>
| + | |
| − | | + | |
| − | == Step 3. Publish the Schema changes ==
| + | |
| − | 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:
| + | |
| − | #Save your Schema changes
| + | |
| − | #Stop the Service Desk service
| + | |
| − | #Run pdm_publish from a command line
| + | |
| − | #Start the Service Desk service
| + | |
| − | | + | |
| − | <font color="blue">For older release</font> recycle the Service Desk service.
| + | |
| − | <br>
| + | |
