Difference between revisions of "Prevent Update to Past Activities"
From SDU
(New page: This article provides instructions for restricting Contacts from updating Activity Log entires generated by other Contacts. In the steps that follow, the example code is used to prevent C...) |
|||
| Line 9: | Line 9: | ||
Then run the following command: | Then run the following command: | ||
| − | pdm_load -f yourfile.txt -i -v | + | '''pdm_load -f yourfile.txt -i -v''' |
| − | + | ||
| − | Create a PRE-UPDATE Constraint as needed for each of the Act_Log, Change_Act_Log, and Issue_Act_Log tables. | + | == 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: | The Constraint syntax is: | ||
analyst = @root.id | 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." | + | ''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== | == 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 22:53, 12 January 2008
This article provides instructions for restricting Contacts from updating Activity Log entires generated by other Contacts.
In the steps that follow, the example code is used to prevent Contacts from updated Activity Log entries by other Contacts.
Step 1. Add Controlled Tables
Create a text file using the following syntax:
CODE
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" }
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
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.
