This documentation supports the 20.02 version of BMC Service Request Management.To view an earlier version, select the version from the Product version menu.

Archiving of service requests and work orders

Service requests and work order records are automatically archived at regular intervals. The Archiving process is enabled by default and runs every 24 hours, however, you can configure the frequency with which it runs. You can also disable the process.

Because the Archiving process is a function of the Remedy AR System platform, you do not need to have the BMC Remedy ITSM suite installed for the Archiving process to run.

Why archive?

Archiving data regularly provides the following benefits:

  • Reduces the size of your production data sets.
  • Improves overall system performance (for example, searches run more quickly, because searches only look at production data, not archived data).
  • Enforces organizational data retention policies.

Related topics

Archiving (describes Archiving concepts in the form of FAQs)

Archiving-architecture

Managing-the-Archiving-process-policies

Preventing-a-record-from-being-archived

Troubleshooting-the-Archiving-process

When an Archiving process takes place, it copies transactional data from a production form and its associated forms to a set of correspondingarchive forms and then deletes the data from the production forms. This work all happens within the same database. Later, you can remove older data from the archive form by performing an export process. Exporting datafrom the archive removes it from the database either by moving it to a .csv file, deleting it, or both. 

Important

  • Archiving is not about backing up data. It’s about maintaining system performance and enabling record retention policies by removing obsolete records from the system. Seehere for more information about what happens to records when they are archived.
  • If you have Archive Admin permissions, you can see a list of the associated forms that are archived along with the main form by opening the main form in BMC Developer Studio (for example, SRM:Request) and then opening the Archiving tab.
    You can exclude individual records from being archived as described inPreventing a record from being archivedin the BMC Remedy ITSM documentation space.


In BMC Service Request Management, the Archiving process archives the following main forms and associated forms:

  • service request ( SRM:Request )

    Click here to see a list of the associated forms that are archived
    • AP:Detail
    • APR:Approval Chain Status
    • NTE:Notifier_Log
    • RBE:Message
    • RBE:Transaction
    • SRD:MultipleQuestionResponse
    • SRM:Request
    • SRM:AppInstanceBridge
    • SRM:AppInstanceFlow
    • SRM:Associations
    • SRM:ConditionInstance
    • SRM:Process
    • SRM:ProcessAOTSummaryData
    • SRM:SR_AuditLog
    • SRM:Survey
    • SRM:Variable
    • SRM:WorkInfo

  • work order ( WOI:WorkOrder)

    Click here to see a list of the associated forms that are archived
    • CFG:Reminders
    • NTE:Notifier_Log
    • TMS:Association
    • TMS:Task
    • TMS:TaskGroup
    • TMS:Variable
    • WOI:Associations
    • WOI:WorkInfo
    • WOI:WorkOrder_AuditLogSystem
    • WOI:WorkOrder_AuditLog

Fulfillment records archived

In addition to archiving service requests and work orders, the Archiving process also archives fulfillment records (such as: work orders, incident requests, change requests, and so on) according to the archiving policies established for those records.

Depending on how the Archiving policies are configured in your environment, it is possible for a fulfillment record to be archived before the related service request is archived. When this situation occurs, you will still see a reference to the fulfillment record in the service request; however, any linking to the fulfillment record is disabled. If you try to access the archived fulfillment record from the service request, the system will display a message telling you that the fulfillment record has been archived. If you need to access the fulfillment record, you will need to contact a system administrator to have a report run against the archive that can pull the record for you.

Depending on how the Archiving policies are configured in your environment, it is possible for a fulfillment record to be archived before the related service request is archived. When this situation occurs, you will still see a reference to the fulfillment record in the Process View; however, the status of the fulfillment record shows as Archived and any linking to the fulfillment record is disabled. If you need to access the fulfillment record, you will need to contact a system administrator to have a report run against the archive that can pull the record for you.

Attachments to Work Info records that are public and associated with fulfillment records are not available in the Service Request Activity log when the fulfillment record is archived before the service request.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*