Jump to: navigation, search

Genesys Info Mart ETL:gim-etl-populate:populate-mm-workbin-facts


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

populate-mm-workbin-facts

Default Value: true
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Dependencies: populate-workbin-as-hold

Enables or disables the population of eServices/Multimedia Interaction Workbin activity to the MSF table. For workbins that are associated with handling resources of type Agent or Place, this option comes into effect only if Genesys Info Mart has not been configured to consider workbin time as hold (populate-workbin-as-hold=false). For the circumstances under which Genesys Info Mart considers workbin time as hold, see the description of the populate-workbin-as-hold option.

Genesys Info Mart uses this value for all configured eServices/Multimedia Interaction Workbins, unless you configure an option that has the same name on an individual Script object for a specific Interaction Workbin in the interface you use for configuration.

  • false—The placement of an interaction in an Interaction Workbin will not be represented in the MSF table.
  • true—Provided that Genesys Info Mart does not consider the workbin time as hold, the placement of an interaction in an Interaction Workbin will be represented in the MSF table. The MSF record references a WORKBIN dimension that identifies the type of resource that is associated with the workbin and the specific resource that is associated with the mediation. Strategy time is not included in the mediation duration, except for scenarios in which an interaction is bounced between an Interaction Workbin and a strategy, as the strategy retries busy agents repeatedly. For more information, see the description of the MEDIATION_DURATION field in the section about populating MSFs in the Genesys Info Mart User’s Guide.

Draft Option

No draft option

This page was last edited on December 22, 2016, at 01:33.
Comments or questions about this documentation? Contact us for support!