Jump to: navigation, search

column-name

Section: gim-etl-mapping
Default Value: No default value
Valid Values: Any valid column name in the table specified by the table-name option
Changes Take Effect: On the next ETL cycle
Dependencies: table-name

Specifies the name of the column in the selected Info Mart table in which the ETL should store the value of this field. The option value is case insensitive.

Refer to the Mapping OCS Record Fields Worksheet in the Genesys Info Mart Deployment Guide for the list of column names.

The type of the OCS field must match the data type of the column.

Note: Configure this option only for the nonmandatory Field objects that you want to store in the Info Mart database.

more...

table-name

Section: gim-etl-mapping
Default Value: No default value
Valid Values: CONTACT_ATTEMPT_FACT, RECORD_FIELD_GROUP_1, RECORD_FIELD_GROUP_2
Changes Take Effect: On the next ETL cycle
Dependencies: The icon_attribute option has been set in the [default] section.

Specifies the name of the Info Mart table in which the ETL should store the value of this field. The option value is case insensitive.

You can specify storage in one of the following tables:

  • CONTACT_ATTEMPT_FACT
  • RECORD_FIELD_GROUP_1
  • RECORD_FIELD_GROUP_2

Note: Configure this option only for the nonmandatory Field objects that you want to store in the Info Mart database.

conversion
Default Value: " "
Valid Values: Any value that can be stored in the field for which this option is configured
Changes take effect:
  OCS: Immediately
  ICON: After restart of the ICON application
  Genesys Info Mart: On the next ETL cycle following the ICON restart

Marks the field that indicates that the answered call was a successful transaction. If the field is updated with a value that equals the value that is configured for this option, Genesys Info Mart recognizes it as a conversion indicator.

right_person
Default Value: " "
Valid Values: Any value that can be stored in the field for which this option is configured
Changes take effect:
  OCS: Immediately
  ICON: After restart of the ICON application
  Genesys Info Mart: On the next ETL cycle following the ICON restart

Specifies the value of the record field when the right person was contacted. If the value of the Right Person Contacted field matches this option value (case-insensitive), Genesys Info Mart sets the RPC_FLAG in the CONTACT_ATTEMPT_FACT table to 1.

icon_attribute
Default Value: 0
Valid Values: 0,1,2
Changes take effect:
  OCS: Immediately
  ICON: After restart of the ICON application
  Genesys Info Mart: On the next ETL cycle following the ICON restart

Instructs ICON as to whether or not to report on this field and which tables to use to store the record field data.

Configuring Field Objects

This page provides instructions for configuring Field objects for Genesys Info Mart reporting.

To enable Genesys Info Mart to report on Outbound Contact activity, you must:

  1. Configure Field objects so that Outbound Contact Server (OCS) will send the required data and ICON will store it. For more information, see Configuring the storage of OCS record field data.
  2. Map Field objects to columns in the Info Mart database. For more information, see Configuring the mapping of OCS record fields.

For more information about Outbound Contact data in Genesys Info Mart, see Outbound Contact Data.


Configuring the storage of OCS record field data

Purpose: To enable the Field object settings that are required for ICON to store mandatory and nonmandatory field data in IDB.

Prerequisites

  • You are logged in to the interface you use to configure your Genesys applications.
  • You have the required access privileges to modify properties for Field objects in the Genesys Configuration Layer.
  • You have opened the Annex for the Field object that requires configuration.

Steps

  1. Review the configuration options in the Field Object–Annex–[default] Section table that you should configure on the Annex of the Record Field object. In the table, click an option name to see a short description of the option.
  2. Add the icon_attribute option to the [default] section on the Annex of the Field object:
    • For each mandatory field that is listed in the Mandatory Record Field Data table
    • For each nonmandatory (custom) field that you want Genesys Info Mart to store in its database
    For more information about mandatory and nonmandatory fields in Genesys Info Mart, see Outbound Contact Data.
  3. If you want to use a field to indicate that the answered call was with the proper contact, add the right_person option to the [default] section on the Annex of that Field object.
  4. If you want to use a field to indicate that the answered call was a successful transaction, add the conversion option to the [default] section on the Annex of that Field object.
    Tip
    You do not have to configure the send_attribute option for any fields. See send_attribute for a description of the option.
    Field Object—Annex—[default] Section
    Option Name Recommended Value

    icon_attribute

    • For nonsensitive data, set this option to 1 to store the data in the IDB GO_CUSTOM_FIELDS and GO_FIELDHIST tables.
    • For sensitive data, set this option to 2 to store the data in the IDB GO_SECURE_FIELDS and GO_SEC_FIELDHIST tables.

    For more information, see Configuring for Outbound Contact Data in the Interaction Concentrator Deployment Guide.

    right_person

    (Optional) Specify a value that indicates that the right person was contacted — for example: TRUE, YES, or 1.

    Do not specify this option for more than one field within a calling list.

    For more information, see Right Person Contacted Record Field.

    conversion

    (Optional) Specify a value that indicates that a transaction was successful.

    Do not specify this option for more than one field within a calling list.

    For more information, see Conversion Record Field.

Next Steps

Configuring the mapping of OCS record fields



Configuring the mapping of OCS record fields

Purpose: To enable the Field object settings that are required for mapping to the Genesys Info Mart database.

To determine what fields you need to map, see the Mapping OCS Record Fields Worksheet. Configure the mapping only for those nonmandatory Field objects that you want to store in the Info Mart database. Follow this procedure to configure the Annex of the corresponding Field object, to indicate the Info Mart table name and column name to which it will be mapped.

Prerequisites

Steps

  1. For each nonmandatory (custom) field that you want Genesys Info Mart to store in its database, add a section named gim-etl-mapping on the Annex of the Field object.
    Important
    When you configure options in the [gim-etl-mapping] section:
    • Do not map more than one field to the same Info Mart table and column.
    • Do not configure options for extra Info Mart table columns that will not store Field object data.
  2. In the [gim-etl-mapping] section, add an option named table-name, and set its value to the name of the Info Mart table in which you want the ETL to store this field.
  3. In the [gim-etl-mapping] section, add an option named column-name, and set its value to the name of the column in the Info Mart table in which you want the ETL to store this field.
  4. In addition, Genesys Info Mart supports the designation of nonmandatory fields to indicate right party contacted and conversion:
    • For a field to indicate that the correct party was contacted, add the right_person option to the [default] section on the Annex of the Field object, and set its value to the field value that you want to indicate that the right party has been contacted (for example, TRUE).
    • For a field to indicate conversion, add the conversion option to the [default] section on the Annex of the Field object, and set its value to the field value that you want to indicate that a conversion has taken place (for example, TRUE).

Next Steps


Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 28 July 2017, at 14:53.