Data Lifecycle Policies: Customer defined retention period for transactions

Highlights

• The admins have the ability to define the retention periods of incident and contact transactions.
• A minimum retention period is enforced for each transactions with a default value.
• A minimum retention period of 6 months is enforced for the below transaction types.
  • Incident Transaction Types: TransEdit, TransStatus, TransQueue, TransRead, TransAssigned, TransEscalated, TransSent, TransFAttachPurge
  • Contact Transaction Types: TransEdit, TransRead, TransMove, TransOptIn, TransEmailInvalidChange, TransPassword, TransEmailChanged, TransEmailAlt1Changed
• A minimum retention period of 1 month is enforced for the below transaction types.
  • Incident Transaction Types: TransResponse, TransForward, TransFailure, TransRuleForward, TransMentioned
  • Contact Transaction Types: TransCityChanged, TransCountryChanged, TransPostalCodeChanged, TransProvinceChanged, TransStreetChanged

Customer defined retention period

Business Benefits:

• Lean DB: The admins can define the retention periods of Incident and Contact transactions based on the business needs and purge older transactions ensuring a lean DB.
• Regulatory and compliance: The admins can define policies with desired retention period to purge transactions to meet the regulatory and compliance requirements.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The Oracle B2C Service site has to be on 24D version to benefit from this enhancement.