Difference between revisions of "Prevent Update to Past Activities"
m |
Agegeleruvy (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://olitudyxej.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]= | ||
| + | ---- | ||
| + | =[http://olitudyxej.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
__NOTOC__ | __NOTOC__ | ||
[[Category:Customizations]] | [[Category:Customizations]] | ||
| Line 7: | Line 15: | ||
This article contains the instructions to restrict updating of past [[activities]]. | This article contains the instructions to restrict updating of past [[activities]]. | ||
| − | '''Option One:''' This option restricts Contacts from editing entries to the [[Activity Log|Activity Logs]] generated by other Contacts. In other words, you will only be able to update items in the [[Activities]] tab that were generated by you. | + | '''Option One:''' This option restricts Contacts from editing entries to the [[Activity Log|Activity Logs]] generated by other Contacts. In other words, you will only be able to update items in the [[Activities]] tab that were generated by you. <br> |
'''Option Two:''' This option restricts all updating. | '''Option Two:''' This option restricts all updating. | ||
| Line 17: | Line 25: | ||
Create a text file using the following syntax: | Create a text file using the following syntax: | ||
| − | + | <source lang="text">TABLE Controlled_Table | |
del desc obj_name sym | del desc obj_name sym | ||
| − | { | + | { "0" ,"Activity Log tables" ,"alg" ,"Act_Log" } |
| − | { | + | { "0" ,"Change Activity Log tables" ,"chgalg" ,"Change_Act_Log" } |
| − | { | + | { "0" ,"Issue Activity Log tables" ,"issalg" ,"Issue_Act_Log" }</source> |
Then run the following command: | Then run the following command: | ||
| Line 35: | Line 43: | ||
The Constraint syntax for Option Two is: '''id=1''' | The Constraint syntax for Option Two is: '''id=1''' | ||
| − | Be sure to provide an Error Message for your [[Data Partitions|Constraint]] (eg | + | Be sure to provide an Error Message for your [[Data Partitions|Constraint]] (eg "You must be the originator of this Activity in order to update it" or "Updating of Activities is not permitted"). |
=== Step 3. Recycle the Service Desk Service === | === Step 3. Recycle the Service Desk Service === | ||
After recycling the Services, your Constraint will be active. | After recycling the Services, your Constraint will be active. | ||
Revision as of 03:16, 24 November 2010
To discuss or ask questions about this article, select the discussion tab above.
Overview
This article contains the instructions to restrict updating of past activities.
Option One: This option restricts Contacts from editing entries to the Activity Logs generated by other Contacts. In other words, you will only be able to update items in the Activities tab that were generated by you. <br> Option Two: This option restricts all updating.
This customization is known to work in all currently supported releases of Service Desk.
Procedures
Step 1. Add to the Controlled Tables list
The first step is to add new tables to the Controlled Tables list. This will allow us to create Data Partition Constraints against those tables. The tables we will be adding are those associated with the Activity Logs.
Create a text file using the following syntax: <source lang="text">TABLE Controlled_Table
del desc obj_name sym
{ "0" ,"Activity Log tables" ,"alg" ,"Act_Log" }
{ "0" ,"Change Activity Log tables" ,"chgalg" ,"Change_Act_Log" }
{ "0" ,"Issue Activity Log tables" ,"issalg" ,"Issue_Act_Log" }</source>
Then run the following command:
pdm_load -f yourfile.txt -i -v
This process will add three new tables to the Controlled Tables list which account for all the ticket activity logs in Service Desk.
Step 2. Create the Data Partition Constraint
Create a PRE-UPDATE Constraint, as needed, for each of the Act_Log, Change_Act_Log, and Issue_Act_Log tables.
The Constraint syntax for Option One is: analyst = @root.id
The Constraint syntax for Option Two is: id=1
Be sure to provide an Error Message for your Constraint (eg "You must be the originator of this Activity in order to update it" or "Updating of Activities is not permitted").
Step 3. Recycle the Service Desk Service
After recycling the Services, your Constraint will be active.
