You can change the default tab or panel that is presented to the agent when Click-to-Call presents a new call. The following section describes the components and configurations for this feature.

The landing page configuration consists of the LandingPageManager, the LandingPageHandler, and the LandingPage components.

The LandingPageManager Component

The /atg/svc/clicktoconnect/LandingPageManager component contains the configurations for all of the LandingPageHandlers and executes them to determine the correct landing page for the Click-to-Call request. It polls all LandingPageHandlers until one of them returns a LandingPage object. If no landing page is returned, the defaultLandingPageHandler is used.

These LandingPageManager properties are configurable as follows. If the LandingPageManager does not successfully determine a LandingPage, the agent’s normal login landing page will be the default landing page:

For example:

landingPageHandlers+=
  /atg/commerce/custsvc/clicktoconnect/ProductViewLandingPageHandler,\
  /atg/commerce/custsvc/clicktoconnect/OrderViewLandingPageHandler,\
  /atg/commerce/custsvc/clicktoconnect/CategoryViewLandingPageHandler

defaultLandingPageHandler=/atg/commerce/custsvc/clicktoconnect/
    DefaultLandingPageHandler
The LandingPageHandler Components

The LandingPageHandler components, which are integrated with LandingPageManager, return a LandingPage based on the values of the Click-to-CallRequestData object.

The following LandingPageHandler properties are configurable:

  • landingPage – the landingPage object that is returned by the
    LandingPageHandler

  • URIMatches – this property is available to LandingPageHandlers that determine the landing page based on the current storefront URL

    Note: When configuring the URIMatches property, you must supply the full file path, for example /commerce2/myaccount/profile.jsp.

    Component

    Description

    /atg/svc/clicktoconnect/
    ProfileViewLanding
    PageHandler

    This component returns a landing page if the storefront URL starts with any one the strings specified by the URIMatches property. The profile viewed will be the same as the profile saved when initializing the call on the storefront.

    For example:
    URIMatches=/ondemand/myaccount/profile.jsp

    /atg/commerce/custsvc/
    clicktoconnect/CategoryView
    LandingPageHandler

    This component returns a landing page if the storefront URL starts with any one the strings specified by the URIMatches property. This component will land the agent on the catalog browse main page.

    For example:
    URIMatches=/ondemand/subcategory.jsp?categoryId=

    /atg/commerce/custsvc/
    clicktoconnect/OrderView
    LandingPageHandler

    This component returns a landing page if the storefront URL starts with any one the strings specified by the URIMatches property. The order ID is identified by a parameter on the storefront URL with the name specified by the property orderIdParameterName. This component has a LandingPage configuration for standard orders and another for scheduled orders.

    For example:
    URIMatches=/ondemand/myaccount/myOrders.jsp

    /atg/commerce/custsvc/
    clicktoconnect/ProductView
    LandingPageHandler

    This component returns a landing page if the storefront URL starts with any one the strings specified by the URIMatches property. The product ID is identified by a parameter on the storefront URL with the name specified by the property productIdParameterName.

    For example:
    URIMatches=/ondemand/productDetailWithPicker.jsp?
    productId=

    /atg/commerce/custsvc/
    clicktoconnect/
    DefaultLandingPageHandler

    This component returns a landing page when no other landing page is provided. If the order is modifiable, the cart view page is used, otherwise the order view page is used.

    For example:
    scheduledOrderViewLandingPage=
    ScheduledOrderViewLandingPage

    orderViewLandingPage=OrderViewLandingPage
    cartViewLandingPage=CartViewLandingPage

The LandingPage Component

A LandingPage object provides all of the information required for the LandinPageManager to initialize the agent UI on a specific view. Commerce Service Center provides a number of pre-configuration LandingPage components that are used by the LandingPageHandlers. However, LandingPage objects can be constructed dynamically at runtime.

The following properties are configurable in the LandingPage component:

The following LandingPage components can be configured:

Component

Description

/atg/svc/clicktoconnect/
ProfileViewLandingPage

Identifies the values required to land on the customer tab’s profile view page.

/atg/commerce/custsvc/clicktoconnect/
CategoryViewLandingPage

Identifies the values required to land on the commerce tab’s catalog view page.

/atg/commerce/custsvc/clicktoconnect/
ProductViewLandingPage

Identifies the values required to land on the commerce tab’s product view page.

/atg/commerce/custsvc/clicktoconnect/
OrderViewLandingPage

Provides the values needed to land on the commerce tab’s order view page.

/atg/commerce/custsvc/clicktoconnect/
ScheduledOrderViewLandingPage

Identifies the values needed to land on the commerce tab’s scheduled order view page.

/atg/commerce/custsvc/clicktoconnect/
CartViewLandingPage

Provides the values required to land on the commerce tab’s cart page.


Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices