Revision as of 19:34, October 25, 2021 by Tony.gilchrist@genesys.com (talk | contribs) (Species how long Genesys Info Mart waits for late-arriving outbound data. Outbound data (such as GO_METRICS) that arrives late, but within the specified limit, is considered during transformation.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

GIM:gim-transformation:ocs-allowed-lateness

View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

ocs-allowed-lateness

Default Value: PT0S
Valid Values: ISO 8601 duration format
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.116.20

Specifies how long Genesys Info Mart waits for late-arriving Outbound Contact data. Outbound Contact data (such as GO_METRICS) that arrives late, but within the specified limit, is processed during transformation.

Draft Option

ocs-allowed-lateness_Draft

Default Value: PT0S
Valid Values: ISO 8601 duration format
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.116.20

Specifies how long Genesys Info Mart waits for late-arriving Outbound Contact data. Outbound Contact data (such as GO_METRICS) that arrives late, but within the specified limit, is processed during transformation. The default value (PT0S), which preserves legacy behavior, provides for no delay.



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