When an in-life asset is changed in The Layer, associated records on third party billing systems may also need to be changed.

The Change Queue feature is a way to quickly and easily set up tracking for changes to specific fields within asset records, where a direct API link doesn't exist.

Before you start using this feature, it's important to understand that changes are tracked by Billing Platform, so it's important to create and link Billing Platforms to your assets before you begin.

Billing Route can be set as early as product inventory, or at the last minute, once an asset has been created. However you decide to implement this, changes will be traced centrally.

It's important to note that the Change Queue tracks services only.


So what's the workflow for tracking asset changes?

As illustrated below, we track changes on:

  1. Asset Edit via Customer Record

  2. Asset Upgrade via Data Capture

  3. Asset Updated via Data Manager

Workflow for change tracking

How is it configured?

Firstly, ask an administrator to enable the App - Change Queue role for your user account.

Next, create the Billing Platform for the provider you wish to track changes for, and decide which properties you wish to track.

You can select the tracking operation from the menu. Currently only "update" operations are supported.

Please note that the Change Queue is not able to track changes where a field is set to or from a null value, with the exception of Case Date and Expiry Date, All changes to these two fields will be tracked.

For example, the below change in either direction will not be picked up.

Changing the site from one to another will show an entry in the Change Queue.


How can I see the changes?

Within apps, you'll see the Change Queue application

The queue is comprehensive and allows users to mark the items processed, or ignore if the change isn't relevant.

You'll see a full breakdown of all tracked fields which have changed:

Confirm the action:

Select a reason for the update:

This will apply the selected reason to all checked changes.

You can also include completed changes in your view:

Did this answer your question?