class NumberNormalisation

MtasSupportFunctions

NumberNormalisation

NumNormProfile [0..255]

The NumberNormalisation Managed Object (MO) represents the top level of the Number Normalization application

This MO is created by the system.

Actions
`boolean`	`numberNormalisationTableCommitAction ( );` <p>This action must be triggered to commit any of NUMNORM OAM Table changes.<br>This action is allowed only when numberNormalisationTableSyncState is "Editing"<br>On success this action returns TRUE, changes the numberNormalisationTableSyncState to either of below<br>"Syncing": If syncing is in progress.<br>"Active" : If syncing is completed.</p>
`boolean`	`numberNormalisationTableEditAction ( );` This action must be triggered before updating any of the NUMNORM OAM Tables. This action is allowed only when SyncState is "Active" On success this action returns TRUE, changes the SyncState to "Editing"

Attributes
`string key mandatory noNotification restricted`	`applicationName` The name of the application. The attribute name and value of is used in the applications RDN.
`uint32[0..1] noNotification`	`groupId = 0` Relevant only in TSP. Independently from the permissions, this attribute can always be modified by the MO owner and by the Super Administrator.
`NumNormTableSyncDT`	`numberNormalisationTableSync = PASSIVE` After changes in the NumberNormalisation attribute, the confirmation is made permanent through setting the numberNormalisationTableSync to SYNCHRONIZING. This means the Number Normalization will be notified that new configuration shall be used. The application creates new tables of the configuration and then sets the numberNormalisationTableSync to PASSIVE when it is ready. When numberNormalisationTableSync is SYNCHRONIZING, no configuration is allowed in the Number Normalization. It is not allowed to set the table sync parameter to SYNCHRONIZING more frequently than every 15 seconds. Note that a user cannot set the value to PASSIVE. It can only be set to PASSIVE by the application itself. Deprecated:
`string readOnly`	`numberNormalisationTableSyncState` <p>This value will replicate the Manager Sync State<br>Allowed values are<br>Initial: Initial value on maiden-installation / new deployment<br>Editing: The operator has triggered Edit action. This is only state in which configuration can change and commit action is allowed<br>Syncing: The operator has triggered the commit action, OR one or more processors has recently scaled out<br>Active: The system is stable, and all traffic are using current configuration. This is only state in which Edit is allowed<br><br></p>
`uint32[0..1] noNotification`	`ownerId = 0` Relevant only in TSP. Independently from the permissions, this attribute can always be modified by the MO owner and by the Super Administrator.
`integer[0..1] noNotification`	`permissions = 9` Relevant only in TSP. The operations allowed for the group members and for other administrators are represented as a bitmap: groupRead(1), groupUpdate(2), groupManage(4), otherRead(8), otherUpdate(16), otherManage(32). Read permission means to read the MO attributes and to see the children of the MO; write permission allows to modify the MO attributes and manage permission allows to create and delete children of the MO. The owner of the MO has all the permissions. The attribute can only be modified by the owner of the MO or by the Super Administrator. By default, the MO is created with the permissions determined by the defaultPermissions attribute of the owner administrator.
`DN[0..1] noNotification`	`shareTree = nodeName=jambala` Relevant only in TSP. This attribute refers to a container object and implies that all administrators defined under this shareTree value have the privileges set as share permissions over the container and its leaf object. Obsolete, must not be used.