Revision as of 16:56, October 15, 2019 by Tanyai (talk | contribs) (Tanyai used the OptionEdit action.)
Jump to: navigation, search

Genesys Info Mart ETL:gim-transformation:ocs-chain-history-limit


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

ocs-chain-history-limit

Default Value: 5000
Valid Values: 0 or any positive integer, where 0 means there is no limit imposed
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.014.14

If positive, the value imposes a limit on the number of GIDB_GO_FIELDHIST or GIDB_GO_CHAINREC_HIST records that can be associated with a particular CHAINGUID. If the actual number of records exceeds the configured limit, error message 55-20176 is logged, and the chain is ignored.

The option was introduced to prevent OutOfMemory errors during transformation in scenarios where suboptimal SCXML logic results in an excessive number of redial attempts. For example, when an internal case gets reopened from the closed state and the result of the dialed call to the customer is NO_ANSWER, if SCXML keeps adding a record to the calling list and Outbound Contact Server (OCS) keeps dialing the number until the customer answers the call, there can be a very large number of GIDB_GO_FIELDHIST and GIDB_GO_CHAINREC_HIST records for this one CHAINGUID.

Consider setting an alarm on log message 55-20176, so that you can correct problematic scenario logic if necessary.

Draft Option

No draft option


Comments or questions about this documentation? Contact us for support!