Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Measurements objects

A measurement object is a point in the collection point that can be measured such as an extension or an ACD group. It is important that the type of measurement object matches the underlying data otherwise the system will not be able to find any data for that measurement object e.g. an extension cannot be configured as an ACD group because the system will then try to find the data for that extension in the ACD database where it will not exist.
It will also not be visible when trying to make extension reports since the system thinks that it's an ACD group and should therefore not be measured as an extension.
Besides a valid id which is not necessarily the same id as the actual number you call (please consult your collection point administrator if you don't know what ids to use) you also need to associate the measurement object with the collection point where it resides. You can also have a text for each measurement object that describes it, this value can be whatever you like but usually, it's the name of the owner e.g. if the extension 1111 exists in the London collection point and is used by John Doe the measurement objects looks like this: 1111 – John Doe – London.

Collection points

Collection points are mapped against a user-defined id that is set when the data collection is set up in Meridix Import Service. Systems that contain several physical collection points can map all collection points to the same collection point if the numbers in the collection point do not overlap.

  • No labels