Difference between revisions of "Prevent Update to Past Activities"
(→Step 1. Add to the Controlled Tables list) |
|||
| Line 4: | Line 4: | ||
== Step 1. Add to the Controlled Tables list== | == 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: | Create a text file using the following syntax: | ||
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->TABLE Controlled_Table<br> del desc obj_name sym <br> { "0" ,"Activity Log tables" ,"alg" ,"Act_Log" }<br> { "0" ,"Change Activity Log tables" ,"chgalg" ,"Change_Act_Log" }<br> { "0" ,"Issue Activity Log tables" ,"issalg" ,"Issue_Act_Log" }<!--c2--></div><!--ec2--> | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->TABLE Controlled_Table<br> del desc obj_name sym <br> { "0" ,"Activity Log tables" ,"alg" ,"Act_Log" }<br> { "0" ,"Change Activity Log tables" ,"chgalg" ,"Change_Act_Log" }<br> { "0" ,"Issue Activity Log tables" ,"issalg" ,"Issue_Act_Log" }<!--c2--></div><!--ec2--> | ||
| Line 9: | Line 11: | ||
Then run the following command: | Then run the following command: | ||
'''pdm_load -f yourfile.txt -i -v''' | '''pdm_load -f yourfile.txt -i -v''' | ||
| + | |||
| + | This process process will add three new tables to the Controlled Tables list. | ||
== Step 2. Create the Data Partition Constraint == | == Step 2. Create the Data Partition Constraint == | ||
Revision as of 01:47, 13 January 2008
This article contains the instructions for restricting 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.
This customization is known to work in all currently supported releases of Service Desk.
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:
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" }
Then run the following command: pdm_load -f yourfile.txt -i -v
This process process will add three new tables to the Controlled Tables list.
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 is:
analyst = @root.id
Note: Be sure to provide an Error Message for your Constraint. Something like "You must be the originator of this Activity in order to update it."
Step 3. Recycle the Service Desk Service
After recycling the Services, your Constraint will be active.
