Jump to: navigation, search

CCAdv Bulk Configuration – Independent Mode

This section describes the bulk configuration of CCAdv objects; the bulk configuration tool configures CCAdv outside of the Advisors Administration module.

You can use the tool to rapidly configure WA based on the lists of objects you define and export from other systems and load into temporary structures in the Advisors Platform database. The bulk configuration tool retrieves the data from the temporary structures, validates it, and transforms it into CCAdv rollup configuration. This tool is designed for use in independent configuration mode. For information about the configuration modes and how to set the mode, see Contact Center Advisor and Workforce Advisor Administrator User's Guide. You must select the configuration mode before you perform bulk configuration.

An object creation script, blkObjectsCre.sql, is supplied as a temporary addition to the installation package in the sql\oracle\bulkconfig\independent\ccadv-bulkload folder. You must execute blkObjectsCre.sql as a script – not as a statement – if opened and executed from the SQL Developer SQL Worksheet. You must apply the blkObjectsCre.sql script to the Platform schema to create the following tables; the tables are required for CCAdv bulk configuration:

  • blkAppNames
  • RepRegionName
  • blkAppAgntGr
  • blkAgntGrNames
  • blkAppLog

You must create all of the preceding tables, but the content is optional. Any or all tables can remain empty. Empty tables do not impact the configuration in any way.

Objects already present in CCAdv configuration, but absent from these tables, remain in the CCAdv configuration after you perform the bulk configuration procedure.

Stored Procedure for Bulk Configuration

You implement the bulk configuration by running a stored procedure, spblkConfigCCAdvIndependent, which is also created when you run the blkObjectsCre.sql script. You execute the procedure against the Platform schema after all base data is prepared in the tables created by running the blkObjectsCre.sql script.

Script to Remove Objects Used in Bulk Configuration Process

The blkObjectsDrop.sql script removes all objects used in the bulk configuration (such as the tables that the blkObjectsCre.sql script creates). You can execute this script whenever necessary. There is no negative impact because of the presence of these objects; they can be retained. The blkObjectsDrop.sql script does not remove any configuration. You must execute the blkObjectsDrop.sql script before you switch to another configuration mode and use bulk configuration tools for that mode.

Stored Procedure for Removing Configuration

You can quickly and completely remove all CCAdv applications, agent groups, and agent group contact centers configured in CCAdv inside or outside the bulk configuration tool. To remove CCAdv configuration, run the spblkRemoveConfigCCAdv stored procedure, which is created when you run the blkObjectsCre.sql script. Run the spblkRemoveConfigCCAdv stored procedure against the Platform schema.

Important

The procedure will remove all data left from previous configurations that may have a negative impact on the new configurations. It can be very useful when the configuration mode must be changed.

In order to be able to restore the configuration, you must have a reliable set of bulk configuration files or blk tables that you can use to re-load the configuration. Before you execute the procedure, make sure that such data exists.

You also can execute the bulk configuration removal procedure if you are comfortable with the current configuration loss and want to re-configure the applications from the beginning.

The configuration removal procedure does not remove the data from blk files. Those are always preserved unless the tables are dropped by running the blkObjectsDrop.sql script.

  • The application server and XML Generator service must be up and successfully running until the required data (see the following two bullets) displays on the pages of the Advisors Administration module. To ensure that the import runs successfully, check the XML Generator log for import-related errors.
  • Log in to the Advisors application; Advisors automatically imports all relevant aggregated objects (regions, operating units, contact centers, and application groups) from the Genesys Configuration Server.
  • All relevant applications and agent groups have been automatically imported by XML Generator, and are available for configuration.
  • Prior to bulk configuration, ensure that all relevant application groups, reporting regions, geographic regions, operating units, and network contact centers are configured. You configure these manually using Advisors administration module.

No existing configuration is removed when using the CCAdv bulk configuration tool. If any objects are already configured, or any application-to-agent group relationships are added manually, they are not removed by the bulk configuration tool. The tool adds to the configuration or changes the mappings of the existing configured objects based on the data contained in the temporary structures.

If an AGCC does not already exist, one is created by the bulk configuration procedure under every network call center (NCC) where each application mapped to it (that is, to the NCC) is also mapped to an agent group and that agent group is mapped to an AGCC.

Genesys recommends that all aggregated objects participating in CCAdv configuration are activated in Advisors administration module prior to performing bulk configuration. Optionally, you can complete this step after bulk configuration. In either case, it is required to make the objects visible on the dashboard view.

The following procedure summarizes the steps to perform bulk configuration of CCAdv when you use the application in independent configuration mode. The information following this procedure provides additional information to assist you. 

1. Start Advisors Application Server and XML Generator.
2. Watch the XML Generator and Geronimo logs.

The logs must be free of any import-related errors.

3. Allow the Advisors application to run for approximately 10 minutes.
4. Open the Administration module in the browser.
5. When the aggregated objects are available, configure all those that you plan to use in CCAdv rollups (see Prerequisites and Preparations).
6. Open each of the following pages and ensure that you can see objects among the available and/or configured object lists, as applicable:
  1. Application Configuration page
  2. Agent Group Configuration page
  3. Contact Group Configuration page
7. Connect to the Oracle instance as platform user.
8. Execute the blkObjectsCre.sql script.

You must execute blkObjectsCre.sql as a script – not as a statement – if opened and executed from the SQL Developer SQL Worksheet.

9. Populate the database tables with your contact group data.
  • For information about preparing your data, see Prerequisites and Preparations and Data Preparation for Application names, Application Display names, and Aggregated Object Names.
  • For information about importing the data from spreadsheets to the database, see Loading Data from Spreadsheets into Temporary Database Structures.
10. Execute the spblkConfigCCadvIndependent procedure:

Oracle: 

DECLARE
M VARCHAR2(200); 
R NUMBER;
BEGIN
"spblkConfigCCAdvIndependent"
(
M => M,
R => R
);
END;

MSSQL: 

USE <name of Advisors platform database>
GO

DECLARE
          @r int,
          @m varchar(255)

EXEC   spblkConfigCCAdvIndependent
          @r = @r OUTPUT,
          @m = @m OUTPUT

SELECT    @r as N'@r',
          @m as N'@m'

GO
11. Verify the log stored in the blkAppLog table.

For information about logs related to the bulk configuration, see Bulk Configuration Validation and Logs.

12. Correct the data, if necessary, and go back to Step 10.

If no correction is necessary, go to Step 13.

13. Examine all relevant configuration pages in the Advisors Administration module to verify the configuration.
14. Examine the CCAdv dashboard to verify the configuration.
15. Do one of the following:
  1. If you are satisfied with the resulting configuration, and you do not plan to use the WA independent configuration tool, connect to the Oracle instance as platform user and execute the blkObjectsDrop.sql script to remove all temporary structures and bulk load procedures.
  2. If you are not satisfied with the resulting configuration, go to Step 12. Alternatively, if you see unpredictable results, and you have a reliable set of bulk configuration data loaded into blk tables, you can remove the whole CCAdv configuration by executing the CCAdv configuration removal procedure. After that you can reload the configuration as described in Step 10.
    Oracle:
    DECLARE
M VARCHAR2(200); 
R NUMBER;
BEGIN
"spblkRemoveConfigCCAdv"
(
M => M,
R => R
);
END;

    MSSQL:

    USE <name of Advisors platform database>
GO

DECLARE@m varchar(255),
               @r int

EXEC   spblkRemoveConfigCCAdv
               @m = @m OUTPUT,
               @r = @r OUTPUT

SELECT @m as N'@m',
               @r as N'@r'


GO

You can use spreadsheets or CSV files to collect the CCAdv configuration information into a simple file structure that can be loaded into a database table. Alternatively, you can omit the file preparation and load the data directly into the database table from the sources available through your relational database management system (RDBMS). If you use spreadsheets or CSV files to collect your CCAdv configuration data, use the following sections as guides.

Object Names

Your spreadsheet or CSV file contains the list of all the application names that need to be configured, as well as the corresponding application display names, contact center names, application group names, reporting region, and operating unit names. Your file must contain six columns with headers (headers are mandatory), and provide the following information:

  • Application Name
  • Application Display Name
  • Contact Center Name
  • Application Group Name
  • Reporting Region Name
  • Operating Unit Name

Add relevant data to the spreadsheet or file under the corresponding column headers. You then import this data into the blkAppNames database table. To expedite the import of the data from the file into the database table, use the column names exactly as they are used in the blkAppNames database table.

Guidelines

Use the following guidelines when you create the spreadsheets to import information about object names to be used for CCAdv bulk configuration:

  • If a display name, reporting region, or operating unit is not defined, you must leave the related cell empty (that is, do not populate the cell with N/A or any other identifier). Where used, the reporting region or the operating unit must have a valid name – both cells cannot be empty. The whole content of the data row is rejected if any incomplete configuration is detected or there are names that cannot be resolved (objects with those names are not found among the imported objects and, therefore, their IDs cannot be located through associations and assignments).
  • Each application name (that is, the application name shown on the Application rollup page in the Administration module) must match the name contained in the tmpImportCallType.PeripheralName, tmpImportInteractionQueue.PeripheralName, or tmpImportApp.PeripheralName column of the Platform database.
  • Each application group name must match the name contained in the APPLICATION.NAME column of the Platform database.
  • Each reporting region name must match the name contained in the REGION.NAME column of the Platform database, where TYPE='R'.
  • Each operating unit name must match the name contained in the REGION.NAME column of the Platform database, where TYPE='O'.

Applications and Agent Group Relationships

To configure application-to-agent group relationships, your spreadsheet or CSV file contains the list of application names, as well as the agent group names and AGCC names. If the related agent groups must also be assigned to agent group contact centers, the names of these contact centers are specified with the agent groups. If a specified AGCC does not exist, the bulk configuration tool creates it, but only if the related application is already mapped to a contact center (that is, it is listed in the blkAppNames structure). If no AGCC needs to be specified, leave the field empty.Your file must contain three columns:

  • Application Name
  • Agent Group Name
  • Agent Group Contact Center Name

Add relevant data to the spreadsheet or file under the column headers. You then import this data into the blkAllAgntGr database table. To expedite the import of the data from the file into the database table, use the column names exactly as they are used in the blkAppAgntGr database table.

Guidelines

Use the following guidelines when you create the spreadsheets to import configuration information about application and agent group relationships:

  • Each agent group name must match the name contained in the tmpImportSkill.EnterpriseName column of the Platform database.

You can prepare agent group descriptive names in a separate blkAgntGrNames file, if required. This table is shared between CCAdv and WA bulk configuration tools.

Import content from the spreadsheets or files into the relevant columns of the corresponding database tables using the Oracle SQL Developer or the MS SQL import option. Follow the procedure for each table.

Importing Content into Tables (Oracle)

1. Open SQL Developer and register a connection to the Advisors Platform schema.
2. Navigate to the Advisors platform schema, then to each created table.
3. Right-click on a table and select the Import Data ... option from the menu.
4. Navigate to the relevant file and select it.
5. Follow the SqlDeveloper Import Data Wizard instructions; the wizard guides you through the import process.

Ensure that you verify the data for each step of the Data Import Wizard, in particular:

  • Review the data on the Data Preview screen to ensure accuracy.
  • Ensure you exclude any unrelated columns that might be present in the file. It is best if you remove unwanted columns from the file before you start the import, rather than excluding columns each time you run the import wizard.
  • Ensure that you correctly map columns in the database table to columns in the file. Verify each and every column.
  • Verify the parameters before import.

See the SQL Developer documentation if you have questions related to data import using SQL Developer.

Importing Content into Tables (MS SQL)

You must match each spreadsheet with a destination table. Ensure you choose the table that was the created for bulk configuration.

1. Open Microsoft SQL Server Management Studio and register a connection to Advisors Platform database
2. Navigate to the Advisors Platform database and launch the import tool for one of the created tables.
3. Following the import wizard instructions.
4. Import the data from each file that contains prepared configuration data.

With MS SQL Server, data can be loaded in one import session if you use Microsoft Excel and the data is consolidated into one spreadsheet with tabs representing the content of each table.

Ensure that you verify the data for each step of the Data Import Wizard, in particular:

  • Review the data on the Data Preview screen to ensure accuracy.
  • Ensure you exclude any unrelated columns that might be present in the file. It is best if you remove unwanted columns from the file before you start the import, rather than excluding columns each time you run the import wizard.
  • Ensure that you correctly map columns in the database table to columns in the file. Verify each and every column.

See the MS SQL Server documentation if you have questions related to data import using Microsoft SQL Server Management Studio.

MSSQL Server Import is very sensitive to special characters which, if present in the files, can trigger import failure accompanied by a message that may seem completely unrelated and will not explain the actual reason. Make sure that the files are clean. Special characters are often invisible and to avoid import failure, you need to check the files for unnecessary empty trailing spaces, empty rows or formatting and remove them before you proceed with the import. While preparing the data, do not copy it from web pages or forms that may contain such characters.

The bulk configuration procedure (spblkConfigCCAdvIndependent) validates each record in the database blk structures. The procedure does not add any configuration if any data contained in the corresponding tables fails to pass validation or cannot be found (or created) in the database. Instead, the procedure records a message in the blkAppLog table and proceeds to the next record. See Prerequisites and Preparations and Data Preparation for Application names, Application Display names, and Aggregated Object Names for information about correct data preparation.

Examine the log to see if you encountered errors when performing the bulk configuration. If there are errors reported in the log, correct the data in the spreadsheets or files, and reload the content to the related tables and columns. You can also correct the data directly in the tables.

Re-run the procedure to complete or correct the configuration using the updated data. Repeat the process as many times as necessary. The procedure does not reduce the existing configuration. The procedure applies all modifications and additions that occurred in the blk tables after your previous execution of the procedure. Any deletion of data, however, is ignored.

The resulting configuration can be verified from the Advisor Administration module and on the dashboard.

You can export the existing CCAdv configuration into a set of temporary structures compatible with CCAdv bulk configuration. You can then export the structures into delimited files, edit them by adapting to the bulk configuration format, and use those for CCAdv configuration in the current or another environment. You can also use the exported structures to compare the actual CCAdv configuration to your expected configuration. Run the blkCfgExp.sql script in your Oracle or MS SQL Server installation to export the data. The script creates and populates or updates the following tables:

  • blkExpAppNames
  • blkExpAppAgntGr
  • blkExpAgntGrNames

All entries for which there is a problem contain an explanation of the issue in the Message column of each table.

This page was last edited on October 21, 2015, at 16:46.
Comments or questions about this documentation? Contact us for support!