Interaction Concentrator:callconcentrator:om-flush-adata

View in ref guide.

Edit this option          Publish this option          Clear draft content

Published Option

om-flush-adata

Default Value: 0
Valid Values: 0,1
Changes Take Effect: Immediately
Introduced: 8.1.514.43
Related Options: calls-in-the-past, om-memory-optimization

This option specifies whether ICON stores in IDB the user data values attached to the event that triggers interaction re-creation in the ICON operational memory. ICON writes to IDB only the user data fields you configured it to store. This compensates for any changes to user data that arrived while the interaction was absent from operational memory. This can happen, for example, if the user data changes arrive attached to an EventPropertiesChanged event, which does not trigger interaction re-creation.

• 1 - ICON stores in IDB the user data from the event triggering interaction re-creation. The user data is tagged as updated (ChangeType = 3), even if the value has not changed since the previous time it was stored.
• 0 - ICON works as in previous releases.

The following tables are affected:

• G_USERDATA_HISTORY
• G_SECURE_USERDATA_HISTORY
• G_CALL_USERDATA_CUST
• G_CALL_USERDATA_CUST1
• G_CALL_USERDATA_CUST2

To use this functionality, you must observe the following conditions:

• This feature works only for events received from Interaction Server.
• You must enable memory optimization in the om-memory-optimization option.
• You must set the calls-in-the-past option to true.
• The ICON Application must have the gud role configured to store attached user data.

Draft Option

No draft option