UCentric Voice Audit Transformation and Blending Guide
- Sean Millar
This guide outlines the various options and rules for transforming an audit of a PBX system. These steps can be followed once a successful audit has been performed either via the UCentric ZT or Web Interface.
Transformation of data can be performed either manually by making changes directly to an LLD or via blending and rulesets.
Adding rulesets
To add a ruleset, browse to click on the “Administration” option on the left hand menu pane and then click “Edit migration rulesets”
Click "Add new ruleset"
Give the ruleset a name and description/notes if needed and click "Add new rule" to add a new rule.
A new row will appear allowing you to choose which field to run the rule against, a condition, value to look for and a second set of options to also match.
The “ACTION”, “ACTION FIELD” and “ACTION VALUE” options allow you to chose the action for the rule should there be matching records in the LLD. Some options allow you to amend, delete the matching LLD row, remove the matching value, move it to another tab or add a warning message for the record on the LLD.
Clicking “Save” will save the rule to allow you to use the ruleset when generating an LLD/Migration Plan.
An explanation of conditions and actions are below.
Conditions | Condition Description | Actions | Action Description |
|---|---|---|---|
Is empty | Will check if field set is empty on LLD and will perform chosen action | Set field value | Action to set the “ACTION FIELD” on the LLD to the “ACTION VALUE” if condition matches. |
Is >x chars | Will check if field value on LLD is over the number of characters in the “VALUE” field and perform the chosen action | Mark as “ignore” | Action to set the set an “IgnoreRecord” column in the LLD to “Yes” if condition matches. |
Is <x chars | Will check if field value on LLD is under the number of characters listed in the “VALUE” field and perform the chosen action | Move to other tab | Action to set the Move the record on the LLD to another tab if condition matches. |
Contains | Will check if the “FIELD” set contains the characters in the “VALUE” Field and perform the chosen action. | Delete record | Action to delete the whole record/row in the LLD if condition matches. |
Every time | Perform the chosen action for every instance of the selected “FIELD” | Add warning message | Action to add a warning message to the LLD for the matching row if condition matches. |
Is duplicate | Will check if “FIELD” contains a duplicate and then performs the chosen action for each duplicate. | Wipe field value | Action to wipe the “ACTION FIELD” to the “ACTION VALUE” if condition matches. |
Is < | Will check if a field value on LLD is less than the number in the “VALUE” field and perform the chosen action |
|
|
Is > | Will check if a field value on LLD is greater than the number in the “VALUE” field and perform the chosen action |
|
|
Is = | Will check if a field value on LLD is equal to the number in the “VALUE” field and perform the chosen action |
|
|
|
|
|
|
Using rulesets during LLD generation
Once you have saved a ruleset you can run an LLD and select that ruleset to use those rules during the generation of the LLD.
Browse to the “Voice Audit” pane of the web interface and click “Sites”
Select the site you wish to run an LLD for.
Click "Export migration plan"
Select the ruleset from the “Use adaptation ruleset” dropdown or edit the existing ruleset if you wish to make further changes to the ruleset before LLD generation. Click “Create Plan” when ready to run the LLD.
The LLD will now generate and any rulesets used will be processed alongside LLD generation
Example rule and LLD results
An example rule and ruleset is shown below which looks to see if the first and last name fields on the LLD are empty and if there is a match the matching fields will be set as “First” and “Last” respectively. This could be useful if a hosted platform requires a username to be set when provisioning.
An image showing the LLD generated when using this rule is shown below.