1. Content Management System Integration Guide
  2. Storage Lifetime Management

Storage Lifetime Management

For many implementations, the lifetime of document content is generally managed by the CMS. This allows important documents to exist long past the lifecycle of their transactional owners in Oracle Transportation and Global Trade Management Cloud. For example, it may be critical for commercial invoices to be stored and queried years after their shipments have been removed. Using Oracle Transportation and Global Trade Management Cloud’s schema to store the invoice, it would be deleted when the shipment is deleted. Using an external CMS, the invoice can be stored based on business rules independent of immediate transportation needs.

There are use cases, however, where maintaining documents in the CMS can add unnecessary overhead. For example, assume you have a PICKUP RECEIPT document type associated with shipments. A user may upload a PICKUP RECEIPT to the system and realize it is incorrect. He then uploads an updated copy of the same receipt. Depending on the versioning support and setup of the CMS, both versions of the PICKUP RECEIPT may be stored in the CMS for an extended period when only the latest version is useful.

When removing content links from the system, Oracle Transportation and Global Trade Management Cloud categorizes the activity by use case. If the use case is managed by the CMS, the link is removed but the content remains in the CMS; if not, the content is removed from the CMS. These use cases include:

  • preview: the link was used for a temporary, asynchronous preview.
  • overlay: the link was intentionally overlaid by a user (e.g. a user uploads new content into a document).
  • revision: the link was to a revision explicitly removed by the user. Revisions are available for Standard Documents in Oracle Transportation and Global Trade Management Cloud.
  • user: the link was explicitly removed by the user from the Document finder.
  • owner: the link was removed indirectly when its owner was removed.

A property controls the system responsible for content removal. Its format is:

glog.document.external.persistRemoveCases=<comma-delimited list of use cases>

where the default setting is:

glog.document.external.persistRemoveCases=preview,overlay,revision,user

This means that content is removed from the CMS when it was 1) used for a temporary preview or 2) manually deleted or overlaid by a user. When a shipment is removed, the shipment documents are not removed from the CMS. It is the responsibility of each CMS to manage document content rules, ensuring scalability as the number and size of documents grow.