Data Import/Bulk Update Quarantine

Update Quarantine in Bulk

For service providers with large numbers of records in Quarantine, cleansing or writing off usage via Cumulus may not be practical. Due to performance reasons, Cumulus restricts users from being able to display and take action on more than 1,000 records at a time. If you need to update more records, this feature provides an easy and fast way to achieve that objective.

The system utilises the Bulk upload processing notification event to send a notification with the results of the bulk approval attempt. You must set up a template for this event and enable it before you can use this tool. If the bulk update is successful, the email notification will advise you when the process is complete. If the bulk approval is not successful, the email notification will send details of the records that failed to be approved and why.

Preparing your data

You will need to create a CSV data file containing a list of records you want to update. To assist with this task, the following reports will contain data with values that are accepted by the import tool.

Nav Reports > List > Quarantine

• Quarantine - BMS Data Quarantine Report (Detail)
• Quarantine - BMS Telephony Quarantine Report (Detail)
• Quarantine - BMS Misc Quarantine Report (Detail)

You must ensure the data meets all validation requirements. These are contained in the data definition table below. When you submit the data file for import, the system will parse the file looking for errors. If the system finds no errors, the system will import the notes into the system. The file needs to be error-free in order to import the data. In the event errors are found, no data will be imported into Emersion. Review the bulk upload processing notification email, correct the file and try again.

Importing your Data

To access the bulk quarantine cleanse tool:

1. Log into Cumulus.
2. Nav: Admin > Bulk Import > xxxxxxx.
3. Click the Browse button and select the csv file containing the list of records you want to update.
4. If you want the bulk upload processing notification email to be sent to a different email address than the address defined in the event template, tick the Override? checkbox and enter an alternative email address. This will only apply for this upload. To change the email address for all future imports or approvals, you will need to change the recipient defined in the event template.
5. Press Submit

The system will validate the data and if no errors are found, the system will approve the invoices. When the notification email is received, the process has been completed.

There is a hard limit of 20,000 records that can be updated using this import tool. If you need to update more than 2,000 accounts, please create multiple import files. A single import file can have up to 1,999 rows of data plus the header row.

It is strongly recommended that you check a few random records to ensure that bulk update was a success. If you find an problem, you cannot roll back the bulk approval.Should this occur, and you wish for Emersion to correct the data, you will need to submit a request to Emersion to fix the errors for you. This request can be submitted via work order ticket. Please include a new csv data file with the records that need to be corrected. Do not include any records that do not need correcting.

Bulk Update Quarantine Data Definition

This section contains a list of the required fields and a definition of what the system considers as valid data.

Bulk Update Quarantine Data Definition table

Data field	Description
QUARANTINE_ID	The ID of the record to be updated. (optional)
USAGE_TYPE	Valid entries are: * telephony * misc or * data. These are not case sensitive. E.g Telephony, telephony and TELEPHONY are all valid data entries. (mandatory)
SERVICE_IDENTIFIER	The service identifier the usage record is for.
TARIFF_KEY	The tariff key. (optional)
CONNECTOR_ID	The id of the Connector. This can be retrieved using any of the reports listed above. (mandatory)
USAGE_ACTION	Valid entries are: * cleansed * writeoff. These are not case sensitive. E.g. Writeoff, writeoff and WRITEOFF are all valid data entries. (mandatory)