Skip to main content
Selecting an Action in Data Capture

Data capture Actions determine what happens to new and existing assets

R
Written by Raymond Carrel
Updated over a week ago

Before a product or service can be fully processed and converted to asset, an action must be selected in Data Capture.

The action informs the behaviour of any new assets created. This is especially important for renewals, upgrades, or anything else that involves an existing asset record, and is much more important for services, as opposed to products.

The classification of your services will likely inform the action you choose.

New

Selecting New will simply create a new asset for the product or service. No existing assets will be affected. This will generally be used for products, and services with a new (or equivalent) classification.

You will not be able to select a Target Asset with this selection, as no existing asset is affected.

Update

Processing a line with the Update action will cause the existing asset selected in the Target Asset to be updated with the values of the new asset.

You may prefer to use this when processing upgrades, renewals etc.

New & Cease

This action triggers two main events:

  1. The creation of a new asset

  2. The ceasing of the asset selected in the Target Asset field

This action is also intended for use with upgrades, renewals etc.

A new asset will be created. The selected target asset will be changed to non-live, and the Cease Date field will be populated.

The date used will be the connection date of the new asset minus one day:

The New & Cease option allows for older asset data to be retained, without the need to manually cease the records.

You can set a default cease reason for assets ceased via this action.


Making actions available

You may need to enable the New & Cease action from Settings - Company Setup - Customisations.

If your organisation is using the New & Cease action, then you may wish to remove the ability to select Update, using the Exclude Update in Data Capture option.

Both of these options are system-wide and will therefore affect all users, so changes should not be made without notifying all affected users.

Did this answer your question?