Purge Jobs

Under data protection legislation, an organisation must not retain customer In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement. data any longer than necessary. Information no longer in use should be purged. Purging involves deleting or obfuscating Obfuscating is hiding or masking data with other characters. Field values are replaced by asterisks and numeric fields are replaced by zeros. data. It helps to keep obsolete or unwanted data to a minimum (subject to regulatory constraints) and can improve an application’s performance. CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. offers a suite of routines to facilitate purging.

For detailed information on all CMP purge jobs, see the CMP Purge Guide.

Java A widely used object-oriented programming language that is designed for use in the distributed environment of the internet. It is the most popular programming language for Android smartphone applications batch purge jobs include the following:

• Archive Management

  The Archive Management job is responsible for dropping and optionally archiving customer transaction data partitions for the PrepaidUsage and PrepaidUsageAllowance tables.

  The job drops the partitions that have been created prior to or on the calculated purge date. If the Archive Required property is set to yes, a copy of the partition is transferred to the archive directory on the archive server prior to dropping the partition. This copy is stored on the archive server as a CSV Comma Separated Values. A simple file format used to store tabular data, such as a spreadsheet or database. CSV files can collect the data from tables so that it can be input to another table-oriented application such as a relational database application. file. The archive server hostname, username, password and port are set as properties for the job in the Administration Console An operations web console that allows batch jobs to be scheduled, run manually and monitored. The console also provides for viewing and modification of business and user applicable system configuration..

  This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. The calculated purge date is worked out by deducting this number of months from the current date. This parameter is optional. If you do not provide a value, a default value of six month is used. This is a scheduled job.

• Comms Purge

  This job is responsible for removing customer communication information stored in CMP.

  The job derives a calculated purge date based on how long data should be retained before it can be purged. Only communications related data that were generated on or before the calculated purge date will be considered by the job.

  The job accepts a single parameter - Months to Retain. This represents the number of months worth of data to retain. The job subtracts this parameter from the current date to calculate a purge date. The months to retain can be entered manually when the job is run. If no value is provided then the value configured for the module property comms.purge.default.noofmonths will be used.

  A creationDate attribute enables partitions to be created to support the Comms Purge job. Partitions are created daily; any partitions with a creation date prior to the calculated purge date are removed.

• Consumer Purge

  This job removes personal customer information, such as contact names or account In the Cloud Monetisation Platform, a billing entity that can be used to manage payments on one or more subscriptions or payments for services. An account can hold details such as payments or invoices. passwords for terminated single subscription A billing entity that incurs a charge. Examples include a network attached device whose usage you want to measure and charge for, or a monthly software subscription accounts and handles subscription anonymity requests. The job considers only records where anonymity request status = P (Pending) on the Subscription Anonymity Request table and only subscriptions who have terminated on or before the calculated purge date.

  The job deletes records where possible and obfuscates data where it is not possible to delete records. Certain data cannot be deleted (e.g. usage The consumption of services, for example a subscriber using call minutes.) as legally there is a requirement for store this a certain period of time.

  This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. The calculated purge date is worked out by deducting this number of months from the current date. This parameter is optional. If you do not provide a value, a default value of six month is used.

  This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions will be sufficient.

• Interface Purge Job

  This job purges transaction data that has been successfully committed to CMP. The job accepts a parameter for number of Days to Retain. The calculated purge date is worked out by deducting this number of days from the current date. Only data dated on or before the calculated purge date is purged. Any transaction data prior to the retention period will be permanently removed.

  This job also drops additional partitions for other child tables associated with the Interface Batch Detail table namely:

  • WholesaleUsageBatchDetail_discard_date

  • PaymentBatchDetail_discard_date

  • PaymentCardBatchDetail_discard_date

  • PaymentUploadBatchDetail_discard_date

  • BankPaymentBatchDetail_discard_date

  • PrePayBatchDetail_discard_date

  • DRAExtractBatchDetail_discard_date

  • DRAResponseBatchDetail_discard_date

  • CreditReferenceExtractBatchDetail_discard_date

  • CreditControlInterfaceBatchDetail_discard_date

  • InterfaceBatchDetailBreakdown_discard_date

  • InterfaceBatchDetailEnvelope_discard_date

  • LedgerBatchDetail_discard_date

  • BulkActionInterfaceBatchDetail_discard_date

  • ExternalReferenceBatchDetail_discard_date

  • GeneralLedgerPaymentBatchDetail_discard_date

  • BondRedemptionBatchDetail_discard_date

  • GeneralLedgerPurchaseBatchDetail_discard_date

  Each invocation of the job produces a summary audit of transaction data removed. This is a scheduled job.

• System Activity Purge

  This job is responsible for the purge of CMP system activity data, for example, records generated by the batch job framework, records of AgentView The graphical user interface of the CMP that is typically used by Customer Service Agents to access CMP customer and billing data. In versions prior to CMP 8.0, this was called the CMP GUI. activity and records of provisioning In telecommunications, the setup of equipment, wiring and transmission to deliver services to a customer. activity. This job purges system activity records from the following:

  • Activity table

  • NetworkRequestLog table, along with their associated 'child' records in the following tables

    • NetworkRequestLogHistory

    • NetworkActivityLog

  • AuditHeader table

  • AuditDetail table

  • Spring batch framework records

  Each invocation of the job produces a summary audit of system activity data removed.

  The job accepts a single parameter - number of days. This represents the number of days worth of data to retain. The job subtracts this parameter from the current date to calculate a purge date. Only system activity data dated on or before the calculated purge date is purged. Any system activity data prior to the retention period will be permanently removed. This is a scheduled job.

The following probes can be run against Purge jobs:

Name			Type	Description
Interface Purge Batch Completed			Alert	Alert probe that returns the number of workflows that have ended up with a processing error today. If the value returned by this query is above the threshold, then an alert is sent to the recipients configured on this probe.
System Activity Batch Completed			Alert	This alert probe returns the number of times the System Activity job has run today. A value of zero indicates the job has not run today and an alert will be sent to the recipients configured for this probe.
Consumer Purge Batch Completed			Alert	This alert probe returns the number of times the Consumer Purge job has run today. A value of zero indicates the job has not run today and an alert will be sent to the recipients configured for this probe.

Relevant JSON schema A specification for JSON based format for defining the structure of JSON data.(s):

• Not applicable. The purge jobs operate on CMP tables; they do not consume or produce data from/for third parties.