Difference between revisions of "Prevent Update to Past Activities"

Revision as of 19:51, 8 March 2008

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.
Option Two: This option restricts all updating.

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: <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.