Layton ServiceDesk - Utilities - Purging
m (Changed hierarchy of section "Life Cycle of an End User") |
m (Removed incorrect text) |
||
| Line 5: | Line 5: | ||
It is highly recommended that you back up your database prior to purging operations, as there no way to restore purged requests. It's also recommended that no-one be using the system during a purging operation in case this causes the database to be modified after the point of last backup. If you purge the wrong item, you can immediately restore the backup without losing any data. | It is highly recommended that you back up your database prior to purging operations, as there no way to restore purged requests. It's also recommended that no-one be using the system during a purging operation in case this causes the database to be modified after the point of last backup. If you purge the wrong item, you can immediately restore the backup without losing any data. | ||
| − | |||
| − | |||
==Life Cycle of an End User== | ==Life Cycle of an End User== | ||
Revision as of 01:31, 9 May 2014
Previous article in this series: Request Export XML
Contents |
Overview
Purging permits the user to purge selected records from the database.
It is highly recommended that you back up your database prior to purging operations, as there no way to restore purged requests. It's also recommended that no-one be using the system during a purging operation in case this causes the database to be modified after the point of last backup. If you purge the wrong item, you can immediately restore the backup without losing any data.
Life Cycle of an End User
- Import from AD.
- End User is used in Requests.
- End User no longer in organisation, disabled in system.
- Purging is done from time to time. The End User cannot be purged if it is still associated with a Request.
- Finally no Requests are left to which the End User is associated.
- Purging removes the End User.
The rule is that if an End User has been specified in the End User field in a Request, you can't purge or delete it. This is because there is a relationship between the data in the End User and Request tables. So purging will only delete End Users that don't appear in Requests.
Purging Options
Purge Requests
If you check the Purge Requests tick box, you may either:
- Purge all Requests Closed before a certain date
- Purge all closed Requests
- Purge a Specific Request ID number.
Purge Tasks
If you check the Purge Tasks tick box, you may either:
- Purge all tasks completed before a certain date
- Purge all completed tasks.
Purge Problems
If you check the Purge Problems tick box, you may either:
- Purge all Problems Closed before a certain date
- Purge all closed Problems
- Purge a Specific Problem ID number.
Purge Change
If you check the Purge Change tick box, you may either:
- Purge all Changes Closed before a certain date
- Purge all closed Changes
- Purge a Specific Change ID number.
Purge Solutions
If you check the Purge Solutions tick box, you may choose Delete Dormant Solution to purge all solutions not in use. A dormant Solution is a Solution that has not been applied or linked to any Requests or Problems.
Purge End Users
If you check the Purge End Users tick box, you may Purge Dormant End Users who have never logged a request.
