Engagement Center UI Configuration

Overview

The Engagement Center UI Configuration service is a mashup service that is used for handling configuration for the Engagement Center UI.

Using this service, you can handle:

  1. Tiles configuration
  2. The logo and the background image of the Engagement Center home page. The size of uploaded image is limited within 1 MB and only JPG, PNG, and JPEG formats are accepted.
  3. The UI layout of the engagement context in the Engagement Center (action area views, business document types, header area views, and work area views)
  4. Required scopes that enable the Agent Home to acquire an access token
  5. Modules configuration


API Reference

/{tenant}/objectViewExtension

The object view extension can be utilized to extend views of business document types.

/{tenant}/objectViewExtension

get

Get object view configurations of extended business document type views.

Required scope: hybris.cecenteruiconfig_view

put

Update object view extensions.

Required scope: hybris.cecenteruiconfig_manage

post

Create new object view extensions.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete a object view extension.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/tilesConfig

Engagement Center tiles configuration.

/{tenant}/tilesConfig

get

Get configuration information of all tiles that the current user is authorized to see.

Different scopes may be required depending on which tiles need to be retrieved:

  • hybris.cecenteruiconfig_view Provide read-only access to Engagement Center UI configuration
  • hybris.cecenteruiconfig_customer_engage Provide access to the Engagement Context tile
  • hybris.cecenteruiconfig_ticket_backoffice Provide access to the Service Tickets tile
  • hybris.cecenteruiconfig_cctr_analytics_contact Provide access to the Interactions tile
  • hybris.cecenteruiconfig_cctr_analytics_queue Provide access to the Queues tile
  • hybris.cecenteruiconfig_cctr_analytics_agent Provide access to the Agents tile
put

Update tiles configuration.

Required scope: hybris.cecenteruiconfig_manage

post

Create default configuration for SAP pre-delivered tiles.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete the configuration for the tiles.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/tilesConfig/{id}

delete tile configuration by id

delete

Delete the configuration for the tile by ID.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/tilesConfig/default

Default tile configuration

get

Get information about default configuration for all tiles that the current user is authorized to see.

Different scopes may be required depending on which tiles need to be retrieved:

  • hybris.cecenteruiconfig_view Provide read-only access to Engagement Center UI configuration
  • hybris.cecenteruiconfig_customer_engage Provide access to the Engagement Context tile
  • hybris.cecenteruiconfig_ticket_backoffice Provide access to the Service Tickets tile
  • hybris.cecenteruiconfig_cctr_analytics_contact Provide access to the Interactions tile
  • hybris.cecenteruiconfig_cctr_analytics_queue Provide access to the Queues tile
  • hybris.cecenteruiconfig_cctr_analytics_agent Provide access to the Agents tile

Logo image

/{tenant}/backgroundImage

Background image

/{tenant}/backgroundImage

get

Get background image that are currently configured in this service. The background image will be returned as a link to the the Media service.

Required scope: hybris.cecenteruiconfig_view

post

Upload a picture as background image and create a key-value pair in the Configuration service. Detailed information is returned by the Media service to store picture information.

Required scope: hybris.cecenteruiconfig_manage

put

Update background image and replace the picture information stored in the Configuration service. At the meantime, delete the old image information in the Media service.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete the key-value pair that stores image information in the Configuration service and delete image information in the Media service.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/businessDocumentTypes

Business Document Types

/{tenant}/businessDocumentTypes

get

Get current business document types configuration data.

Required scope: hybris.cecenteruiconfig_view

put

Update business document types.

Required scope: hybris.cecenteruiconfig_manage

post

Post business document types.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete business document types.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/businessDocumentTypes/default

Default business document types

get

Get default business document types configuration data.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/workAreaViews

Work area views

/{tenant}/workAreaViews

get

Get work area views.

Required scope: hybris.cecenteruiconfig_view

put

Update work area views.

Required scope: hybris.cecenteruiconfig_manage

post

Post work area views.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete work area views.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/workAreaViews/default

Default work area views

get

Get default work area views.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/headerAreaViews

Header area views

/{tenant}/headerAreaViews

get

Get header area views.

Required scope: hybris.cecenteruiconfig_view

post

Create header area views.

Required scope: hybris.cecenteruiconfig_manage

put

Update header area views.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete header area views.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/headerAreaViews/default

Default header area views

get

Get default header area views.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/actionAreaViews

Action area views

/{tenant}/actionAreaViews

get

Get action area views.

Required scope: hybris.cecenteruiconfig_view

post

Create action area views.

Required scope: hybris.cecenteruiconfig_manage

put

Update action area views.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete action area views.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/actionAreaViews/default

Default action area views

get

Get default action area views.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/requiredScopes

Required scopes

/{tenant}/requiredScopes

get

Get all the required scopes that are configured in this service. Engagement Center will use these scopes to acquire tokens from the OAuth2 service.

Required scope: hybris.cecenteruiconfig_view

post

Load all the required scopes that are pre-delivered by SAP as the default configuration.

Required scope: hybris.cecenteruiconfig_manage

put

Update existing required scopes.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete the list of required scopes from the configuration. After deletion, Engagement Center will not be able to acquire a token with proper authorization to perform certain actions.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/requiredScopes/default

Default required scopes

get

Get the default required scopes. Engagement Center will use these scopes to acquire tokens from the OAuth2 service.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/moduleDefinitions

Module definitions

/{tenant}/moduleDefinitions

get

Get module definitions.

Required scope: hybris.cecenteruiconfig_view

post

Create module definitions.

Required scope: hybris.cecenteruiconfig_manage

put

Update module definitions.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete module definitions.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/moduleDefinitions/default

Default module definitions

get

Get default module definitions.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/businessContextConfig

Business context related configurations

/{tenant}/businessContextConfig

get

Retrieve all the business context-related configurations, which are required to render the Engagement Context in the Engagement Center. These configurations include:

  1. Business Document Types (/{tenant}/businessDocumentTypes)
  2. Header Area Views (/{tenant}/headerAreaViews)
  3. Work Area Views (/{tenant}/workAreaViews)
  4. Action Area Views (/{tenant}/actionAreaViews)
  5. Module Definitions (/{tenant}/moduleDefinitions)
  6. SAP GUI for HTML URLs (/{tenant}/sapguihtml)
  7. Side Panel Views (/{tenant}/sidePanelConfig)
  8. I18N Values (/{tenant}/i18n)
  9. Configuration Parameters (/{tenant}/configParameters)
  10. Account Searches (/{tenant}/accountSearches)

If the service does not find any data on one of the listed configurations, then the properties of the respective configuration are not included in the response.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/sapguihtml

SAP GUI for HTML URLs

/{tenant}/sapguihtml

get

Get list of all URLs for SAP GUI for HTML.

Required scope: hybris.cecenteruiconfig_view

put

Update the list of all URLs for SAP GUI for HTML.

Required scope: hybris.cecenteruiconfig_manage

post

Post a list of all URLs for SAP GUI for HTML.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete the list of all URLs for SAP GUI for HTML.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/texts

Text List with multilanguage support

/{tenant}/texts

get

Get list of all language dependent text objects.

Required scope: hybris.cecenteruiconfig_view

put

Update the list with all language dependent text objects.

Required scope: hybris.cecenteruiconfig_manage

post

Post a list with all language dependent text objects.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete the list with all language dependent text objects.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/texts/default

APIs for default text groups

get

Get default text groups.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/texts/{group}

APIs for a group specific list of text objects

get

Get list of all language dependent text objects that have a specific group.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/userScopes

Scopes of the user

/{tenant}/userScopes

get

Get all the scopes of a user. Engagement Center will use these scopes to acquire tokens from the OAuth2 service.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/sidePanelConfig

Side Panel Configuration

/{tenant}/sidePanelConfig

get

Get a list of all the views which are configured for the side panel.

Required scope: hybris.cecenteruiconfig_view

put

Update the list of all the views that are configured for the side panel.

Required scope: hybris.cecenteruiconfig_manage

post

Post a list of all views that are configured for the side panel.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete the list of all views configured for the side panel.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/sidePanelConfig/default

Default module definitions

get

Get a list of all the views which are configured for the side panel.

Required scope: hybris.cecenteruiconfig_view

/{tenant}/accountSearches

Account Searches displayed in the Engagement Center Account Identification view

/{tenant}/accountSearches

get

Get the list of all Account Searches displayed in the Engagement Center Account Identification view.

Required scope: hybris.cecenteruiconfig_view

put

Update the list with all Account Searches to be displayed in the Engagement Center Account Identification view.

Required scope: hybris.cecenteruiconfig_manage

post

Post a list with all Account Searches to be displayed in the Engagement Center Account Identification view.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete all Account Searches.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/configParameters

Configuration Parameters

/{tenant}/configParameters

get

Get a list of all the configuration parameters.

Required scope: hybris.cecenteruiconfig_view

put

Update the list of all the configuration parameters.

Required scope: hybris.cecenteruiconfig_manage

post

Post a list of all the configuration parameters.

Required scope: hybris.cecenteruiconfig_manage

delete

Delete the list of all the configuration parameters.

Required scope: hybris.cecenteruiconfig_manage

/{tenant}/configParameters/default

Default module definitions

get

Get a list of all the default configuration parameters.

Required scope: hybris.cecenteruiconfig_view


Scopes

The table shows the scopes that the Engagement Center UI Configuration service supports.

SCOPEDESCRIPTION
hybris.cecenteruiconfig_viewProvide read-only access to the Engagement Center UI configuration
hybris.cecenteruiconfig_manageCreate and update the Engagement Center UI configuration
hybris.cecenteruiconfig_customer_engageProvide access to the engagement context, which is a UI application used by the users to handle customer interactions with full communication integration within the Engagement Center.
hybris.cecenteruiconfig_cctr_analytics_contactProvide access to the Interactions tile
hybris.cecenteruiconfig_cctr_analytics_queueProvide access to the Queues tile
hybris.cecenteruiconfig_cctr_analytics_agentProvide access to the Agents tile
hybris.cecenteruiconfig_cctr_connectionProvide authorization to show SAP Contact Center-related toolbar on the Home page in the Engagement Center

For more information about scopes, authorization, and authentication procedures for YaaS services, see Scopes and Authorization.


Load Default Configuration

SAP delivers the default configuration. The prefix "SAP" is reserved as a naming convention for the default configuration key. For example, SAP_ENGAGEMENT_CONTEXT. To load the default configuration for your tenant, start with the Initial loading procedure and the conduct the Delta loading procedure when the new default configuration is delivered.

Initial loading

When you configure the Engagement Center application, you can load the default configuration to your tenant using initial loading, so that the Engagement Center application can work with it. Use these endpoints to perform the initial loading of the default configuration by sending a POST request:

  • /{tenant}/tilesConfig: to load all the tiles that are delivered by SAP for the first time
  • /{tenant}/businessDocumentTypes: to load all the business document types that are delivered by SAP for the first time
  • /{tenant}/workAreaViews: to load all the work area views that are delivered by SAP for the first time
  • /{tenant}/headerAreaViews: to load all the header area views that are delivered by SAP for the first time
  • /{tenant}/actionAreaViews: to load all the action area views that are delivered by SAP for the first time
  • /{tenant}/requiredScopes: to load all the required scopes that are delivered by SAP for the first time
  • /{tenant}/moduleDefinitions: to load all the module definitions that are delivered by SAP for the first time

Delta loading

After the initial loading, follow these steps to load the new configuration that SAP delivers.

  1. Make a GET request using these endpoints to retrieve the current configuration from your tenant:

    • /{tenant}/tilesConfig: for the tiles
    • /{tenant}/businessDocumentTypes: for the business document types
    • /{tenant}/workAreaViews: for the work area views
    • /{tenant}/headerAreaViews: for the header area views
    • /{tenant}/actionAreaViews: for the action area views
    • /{tenant}/requiredScopes: for the required scopes
    • /{tenant}/moduleDefinitions: for the module definitions
  2. Make a GET request using these endpoints to get the latest full set of the default configuration that SAP delivers:

    • /{tenant}/tilesConfig/default: for all the tiles that the current user is authorized to see
    • /{tenant}/businessDocumentTypes/default: for the business document types
    • /{tenant}/workAreaViews/default: for the work area views
    • /{tenant}/headerAreaViews/default: for the header area views
    • /{tenant}/actionAreaViews/default: for the action area views
    • /{tenant}/requiredScopes/default: for the required scopes
    • /{tenant}/moduleDefinitions/default: for the module definitions
  3. Check for the missing default configuration entries in your tenant by comparing the results you get from the steps listed above.

  4. Add the missing entries to the results you get from the Step 1.

  5. Send the entire data set in a PUT request to the corresponding endpoint.


Update Configuration

You can update the configuration data that you created for:

  • Tiles
  • Logo
  • Background image
  • Business document types
  • Work area views
  • Header area views
  • Action area views
  • Required scopes
  • Module definitions
  • SAP GUI for HTML configuration

You can also update the configuration data, loaded from the default configuration for:

  • Tiles
  • Business document types
  • Work area views
  • Header area views
  • Action area views
  • Required scopes
  • Module definitions

For the endpoints that manage resources as an array, the PUT method supports both creating and updating the configuration entries.

The service supports only full updates, in which the entire configuration uses the values you provide in the PUT request. When updating the Engagement Center UI configuration, first, retrieve the current configuration from your tenant. Then, modify the data and send it, in its entirety, in the PUT request to the corresponding endpoint, even if you just want to insert a new entry or modify an existing entry.

For security purposes, provide a value for the field hybris.user when you send a POST, PUT, or DELETE request to this service. There are two ways to get the hybris.user value:

  • Enter the password in field grant_type, then provide the username and password to get a token. The token contains the hybris.user value.
  • Provide the hybris.user value in the http header.


Add Custom Configuration

Use the PUT method to create custom configuration entries for:

  • Tiles
  • Business document types
  • Work area views
  • Header area views
  • Action area views
  • Required scopes
  • Module definitions
  • SAP GUI for HTML URLs


Tiles Configuration

A tile is an application that is part of the Engagement Center. Use the /{tenant}/tilesConfig endpoint to load the default configuration for tiles, as well as retrieve, change, and delete configurations for tiles. Use the endpoint /{tenant}/tilesConfig/{id} to delete the tiles developed by customers.


Logo Image

You can upload a logo image for display at the top of the Engagement Center home page. To ensure the best possible performance, use a JPG, PNG, or JPEG image that is 1 MB or smaller. Call the endpoint /{tenant}/logo to configure the logo image for the Engagement Center using the following methods:

  • The POST method uploads the picture file as a logo image.
  • The PUT method updates and replaces the logo image.
  • The DELETE method deletes the logo image information.
  • The GET method retrieves the link to the logo image.


Background Image

You can upload a background image for display as the background of the Engagement Center home page. To ensure the best possible performance, use a JPG, PNG, or JPEG image that is 1 MB or smaller. Call the endpoint /{tenant}/backgroundImage to configure the background image for the Engagement Center using these methods:

  • The POST method uploads the picture file as a background image.
  • The PUT method updates and replaces the background image.
  • The DELETE method deletes the background image information.
  • The GET method retrieves the link to the background image.


Business Context

These business context configurations are required to render the engagement context within the Engagement Center:

  • Business document types
  • Header area views
  • Work area views
  • Action area views
  • Module definitions

Send a GET request to the endpoint /{tenant}/businessContextConfig to retrieve all the business context configurations in one call.


Business Document Types

The business document types (BDTs) configuration defines the UI components used for the business document types in the engagement context. For each of the BDTs, you can specify the views used for creating, editing, displaying, and searching. Use the /{tenant}/businessDocumentTypes endpoint to load the default configuration for BDTs, as well as retrieve, change, and delete the configuration for BDTs.


Work Area Views

The work area views configuration defines which views display in the work area of the engagement context. You can include views that represent an action for a business document type, and other views. Use the /{tenant}/workAreaViews endpoint to load the default configuration for work area views, as well as retrieve, change, and delete the configuration.


Header Area Views

The header area views configuration defines which views display in the header area of the engagement context. For each of the header area views, you can specify the order from left to right and the column span. Use the /{tenant}/headerAreaViews endpoint to load the default configuration for header area views, as well as retrieve, change, and delete configuration.


Action Area Views

The action area views configuration defines which views display in the action area of the engagement context. For each of the action area views, you can specify the order from left to right and the column span. Use the /{tenant}/actionAreaViews endpoint to load the default configuration for action area views, as well as retrieve, change, and delete the configuration.


Required Scopes

The required scopes configuration defines the scopes used by the Engagement Center to acquire the tokens from the OAuth2 service. Use the /{tenant}/requiredScopes endpoint to load the default configuration for required scopes, as well as retrieve, change, and delete configuration for required scopes.


Module Definitions

The module definitions configuration defines the modules that are included in the engagement context UI. Only the activated modules display. Use the /{tenant}/moduleDefinitions endpoint to load the default configuration for module definitions, as well as retrieve, change, and delete the configuration.


SAP GUI for HTML URLs

The SAP GUI for HTML URLs configuration defines the SAP GUI for HTML and WebSocket Connection URLs for each unique combination of a key of business document type and a view type. Both URLs must point to the same server to establish the feedback channel and the SAP GUI session in the same system. To keep the data consistent, use one base URL, extended by two different paths. Use the /{tenant}/sapguihtml endpoint to post a list of all URLs for SAP GUI for HTML, as well as retrieve, change, and delete the list of all SAP GUI for HTML URLs.

For more information about setting up the URLs and further settings on the ERP side, refer to SAP Note 2353509.


Send and Retrieve Compressed Data

When working with big data sets, you can send and receive encoded data to reduce response time and bandwidth usage. The Engagement Center UI Configuration service supports the GZIP format for content encoding. To send compressed data to the Engagement UI Configuration service, set the Content-Encoding header with the gzip value. To retrieve your data in the GZIP format, use the Accept-Encoding header with the gzip value. It is recommended that you use data encoding every time you send a large amount of data in the body of your request, as well as when you expect to receive a large data set in the response from the service.


Create Default Configuration

Before using the Engagement Center application, load the default configurations that SAP delivers for your tenant. There are default configurations for these elements:

  • Tiles
  • Business document types
  • Work area views
  • Header area views
  • Action area views
  • Required scopes
  • Module definitions

Example of creating the default configuration for tiles:

Request

  • Method: POST
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/tilesConfig
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_manage.
  • URI Parameters
    • {tenant}: The name of the current tenant

Response

The successful response returns a 201 status code.


Load New Default Configuration

After the initial load of the default configuration for tiles, business document types, work area views, header area views, action area views, required scopes, and module definitions, load the new configuration that SAP delivers.

Follow the steps below to load the new default configuration for header area views:

  1. Retrieve the current configuration for header area views from your tenant.
  2. Retrieve the latest full set of default configurations for header area views.
  3. Send a PUT request with the request body. Make sure the request body contains all of the current configuration entries in the tenant and all the missing configuration entries.

Example of retrieving the current configuration for header area views from the tenant:

Request

  • Method: GET
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/headerAreaViews
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_view.
  • URI Parameters
    • {tenant}: The name of the current tenant

Response

The successful response returns a 200 status code. An example JSON content looks similar to the following:

[
  {
    "id": "SAP_Account_Identification",
    "order": 1,
    "columnSpan": 2,
    "viewPath": "com.sap.cecenter.engagementcenter.view.headerarea.accountidentification.AccountIdentification",
    "viewDescription": "Account Identification",
    "active": true
  },
  {
    "id": "Custom_Define_Item",
    "order": 2,
    "columnSpan": 1,
    "viewPath": "com.example.customdefine.item",
    "viewDescription": "custom define item",
    "active": true
  }
]

Example of retrieving the latest full set of default configurations for header area views:

Request

  • Method: GET
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/headerAreaViews/default
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_view.
  • URI Parameters
    • {tenant}: The name of the current tenant

Response

The successful response returns a 200 status code. An example JSON content looks similar to the following:

  {
    "id": "SAP_Account_Identification",
    "order": 1,
    "columnSpan": 2,
    "viewPath": "com.sap.cecenter.engagementcenter.view.headerarea.accountidentification.AccountIdentification",
    "viewDescription": "Account Identification",
    "active": true
  },
  {
    "id": "SAP_OPEN_Item",
    "order": 2,
    "columnSpan": 1,
    "viewPath": "com.sap.cecenter.engagementcenter.view.headerarea.accountrecentitems.AccountRecentItems",
    "viewDescription": "Recent Items",
    "active": true
  }

There are two default configurations for header area views in the response body. Comparing the data with the first result, you can see that SAP_OPEN_Item is a new default configuration, which is missing in the tenant.

Example of sending a PUT request with the request body:

Request

  • Method: PUT
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/headerAreaViews
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_manage.
  • URI Parameters

    • {tenant}: The name of the current tenant
  • Body:

    {
    "havConfigValues": [
     {
      "id": "SAP_Account_Identification",
      "order": 1,
      "columnSpan": 2,
      "viewPath": "com.sap.cecenter.engagementcenter.view.headerarea.accountidentification.AccountIdentification",
      "viewDescription": "Account Identification",
      "active": true
    },
    {
      "id": "SAP_OPEN_Item",
      "order": 2,
      "columnSpan": 1,
      "viewPath": "com.sap.cecenter.engagementcenter.view.headerarea.accountrecentitems.AccountRecentItems",
      "viewDescription": "Recent Items",
      "active": true
    },
    {
      "id": "Custom_Define_Item",
      "order": 2,
      "columnSpan": 1,
      "viewPath": "com.example.customdefine.item",
      "viewDescription": "custom define item",
      "active": true
    }
    ]
    }
    

Response

The successful response returns a 204 status code.


Retrieve Configurations

To retrieve any of these configurations, send a GET request to the specified endpoints:

  • /{tenant}/tilesConfig
  • /{tenant}/logo
  • /{tenant}/backgroundImage
  • /{tenant}/businessDocumentTypes
  • /{tenant}/workAreaViews
  • /{tenant}/headerAreaViews
  • /{tenant}/actionAreaViews
  • /{tenant}/requiredScopes
  • /{tenant}/moduleDefinitions
  • /{tenant}/sapguihtml

You can also make a GET request using the endpoint /{tenant}/businessContextConfig to retrieve all the business context related configurations. These configurations include:

  • Business document types: /{tenant}/businessDocumentTypes
  • Header area views: /{tenant}/headerAreaViews
  • Work area views: /{tenant}/workAreaViews
  • Action area views: /{tenant}/actionAreaViews
  • Module definitions: /{tenant}/moduleDefinitions

Example of retrieving the configuration for business document types:

Request

  • Method: GET
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/businessDocumentTypes
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_view.
  • URI Parameters
    • {tenant}: The name of the current tenant

Response

The successful response returns a 200 status code. An example JSON content looks similar to the following:

  {
    "businessDocumentType": "SAP_ACCOUNT",
    "i18nKeySingular": "BUSDOCTYPE_ACCOUNT",
    "i18nKeyPlural": "BUSDOCTYPE_ACCOUNTS",
    "active": true,
    "bcdItemHandlerClass": "com.sap.cecenter.engagementcenter.bcd.bcditem.Accounts",
    "bcdItemKey": "ACCOUNTS",
    "modulePath": "SAP_ENGAGEMENT_CONTEXT",
    "businessDocumentTypeName": "Account",
    "workareaViewCreate": "SAP_ACCOUNT__CREATE",
    "workareaViewEdit": "SAP_ACCOUNT__EDIT",
    "workareaViewDisplay": "SAP_ACCOUNT__DISPLAY",
    "interactionLogRelevant": false,
    "serviceUri": "",
    "displayOrder": 3,
    "workAreaViewSearch": ""
  },
  {
    "businessDocumentType": "SAP_ERP_SALESORDER",
    "i18nKeySingular": "BUSDOCTYPE_ERP_SALESORDER",
    "i18nKeyPlural": "BUSDOCTYPE_ERP_SALESORDERS",
    "active": true,
    "bcdItemHandlerClass": "com.sap.cecenter.erpsalesorderui.bcd.ERPSalesOrders",
    "bcdItemKey": "SAP_ERP_SALES_ORDERS",
    "modulePath": "SAP_ERPSALES_ORDER",
    "businessDocumentTypeName": "ERP Sales Order",
    "workareaViewCreate": "SAP_ERP_SALESORDER__CREATE",
    "workareaViewEdit": "",
    "workareaViewDisplay": "SAP_ERP_SALESORDER__DISPLAY",
    "interactionLogRelevant": true,
    "serviceUri": "https://api.us.yaas.io/hybris/dsdorderproxy/v1/{tenantId}/erpsalesorder/customer/{mixins.sdcustomer.sdCustomerNumber}/recentItems?pageNumber=1&pageSize=3",
    "displayOrder": 5,
    "workAreaViewSearch": "SAP_ERP_SALES_ORDER_ADVANCED_SEARCH"
  }


Update a Configuration

You can update configurations for tiles, logo, background image, business document types, work area views, header area views, action area views, required scopes, module definitions, and SAP GUI for HTML URLs.

Follow the steps below to update a configuration for the header area views.

  1. Retrieve the configuration for header area views
  2. Modify the retrieved header area views

Example of retrieving the configuration for header area views:

Request

  • Method: GET
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/headerAreaViews
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_view.
  • URI Parameters
    • {tenant}: The name of the current tenant

Response

The successful response returns a 200 status code. An example JSON content looks similar to the following:

  {
    "id": "SAP_Account_Identification",
    "order": 1,
    "columnSpan": 2,
    "viewPath": "com.sap.cecenter.engagementcenter.view.headerarea.accountidentification.AccountIdentification",
    "viewDescription": "Account Identification",
    "active": true
  },
  {
    "id": "Custom_Define_Item",
    "order": 2,
    "columnSpan": 1,
    "viewPath": "com.example.customdefine.item",
    "viewDescription": "custom define item",
    "active": true
  }

Example of how to change the results from the preceding step, and send the updated results as a request body in a PUT request:

Request

  • Method: PUT
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/headerAreaViews
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_manage.
  • URI Parameters

    • {tenant}: The name of the current tenant
  • Body:

    {
    "havConfigValues": [
     {
      "id": "SAP_Account_Identification",
      "order": 1,
      "columnSpan": 2,
      "viewPath": "com.sap.cecenter.engagementcenter.view.headerarea.accountidentification.AccountIdentification",
      "viewDescription": "Account Identification",
      "active": true
    },
    {
      "id": "Custom_Define_Item",
      "order": 2,
      "columnSpan": 1,
      "viewPath": "com.example.customdefine.item",
      "viewDescription": "custom define item",
      "active": true
    },
    {
        "id": "New_Custom_Define_Item1",
        "order": 1,
        "columnSpan": 1,
        "viewPath": "ExampleViewPath",
        "viewDescription": "HAV_EXAMPLE_1",
        "active": true
      },
      {
        "id": "New_Custom_Define_Item2",
        "order": 2,
        "columnSpan": 1,
        "viewPath": "ExampleViewPath",
        "viewDescription": "HAV_EXAMPLE_2",
        "active": true
      }
    ]
    }
    

Response

The successful response returns a 204 status code.


Remove Configurations

To remove configurations, make a DELETE request using these endpoints:

  • /{tenant}/tilesConfig
  • /{tenant}/tilesConfig/{id}
  • /{tenant}/logo
  • /{tenant}/backgroundImage
  • /{tenant}/businessDocumentTypes
  • /{tenant}/workAreaViews
  • /{tenant}/headerAreaViews
  • /{tenant}/actionAreaViews
  • /{tenant}/requiredScopes
  • /{tenant}/moduleDefinitions
  • /{tenant}/sapguihtml
When you use the DELETE method with these endpoints, corresponding configuration data is cleared. To delete only a subset of tile configuration entries, use the DELETE method at the endpoint /{tenant}/tilesConfig/{id}. To delete only a subset of other configuration entries except for tiles, use the PUT method. For more information, see the Update a Configuration section.

Example of the "delete all tiles" configuration:

Request

  • Method: DELETE
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/tilesConfig
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_manage.
  • URI Parameters
    • {tenant}: The name of the current tenant

Response

The successful response returns a 204 status code.

Example of the "delete a self-developed tile" configuration:

Request

  • Method: DELETE
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/tilesConfig/{id}
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_manage.
  • URI Parameters
    • {tenant}: The name of the current tenant
    • {id}: The unique identification of the tile
  • Query Parameters
    • version: the version of the tile to delete

Response

The successful response returns a 204 status code.


Upload the Picture as a Logo or a Background Image

To upload a picture for a logo or a background image, make a POST request using these endpoints:

  • /{tenant}/logo
  • /{tenant}/backgroundImage

Example of uploading a logo picture:

Request

This sample request uploads a file and requires the multipart/form-data content type.

  • Method: POST
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/logo
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_manage.
  • URI Parameters
    • {tenant}: The name of the current tenant
var file;
loadFile('filePlaceholder', 'readAsArrayBuffer', function(e) {
 file = e.target.result;
});
file

var request = jQuery.ajax({
 url: requestUrl,
 type: 'POST',
 contentType: 'multipart/form-data',
 data: file,
 processData: false,
 async: false
}).done(function(){console.log('uploaded');});
request.status

Response

The successful response returns a 201 status code.


Get the Picture for a Logo or a Background Image

To get a picture for a logo or a background image, make a GET request using these endpoints:

  • /{tenant}/logo
  • /{tenant}/backgroundImage

Example of getting a logo picture:

Request

  • Method: GET
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/logo
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_view.
  • URI Parameters
    • {tenant}: The name of the current tenant

Response

The successful response returns a 200 status code. An example JSON content looks similar to the following:

{
  "id": "57e25630f7c483001db3a2e1",
  "link": "https://s3.amazonaws.com/sap.yaas.us.88482993329106538260.media/57e25630f7c483001db3a2e1?x-amz-security-token=FQoDYXdzEKH%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaDBLtisMJEBiAALxpzSLMAWFTId0eG0JETD8%2Fy5UFcGWddpcDzpVHglmu7n3mR8RdPkll0uDSw9Rgka08zqOWb8fSymZ34Ut89we9ykTvQL6BwWJm4q2QJOCXa%2BPncxgAn3i7fkj8lAq6IEHJeB5VpqPs0TwLx%2Fave5tcDPzmle2fmwXfrPN48%2BqFaPlYLAARHpqaEpDb6fnWedpZ0YsblxqszRwzN4oj36s2qUWC3pfJRty0YJyO9dleZCt3tCRBemQA5VqRnFQmp3yPZQzf1O7YfscsuZHvEifO6iiL%2BbbABQ%3D%3D&AWSAccessKeyId=ASIAIADUSS3Q3KQ4VHKA&Expires=1477299314&Signature=hV6hlkq%2Fxo1vyQrHHEdXBiOYp28%3D"
}


Replace the Picture for a Logo or a Background Image

To replace a picture for a logo or a background image, make a PUT request using these endpoints:

  • /{tenant}/logo
  • /{tenant}/backgroundImage

Example of replacing a logo picture:

Request

This sample request uploads a file and requires the multipart/form-data content type.

  • Method: PUT
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/logo
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_manage.
  • URI Parameters
    • {tenant}: The name of the current tenant
var file;
loadFile('filePlaceholder', 'readAsArrayBuffer', function(e) {
 file = e.target.result;
});
file

var request = jQuery.ajax({
 url: requestUrl,
 type: 'PUT',
 contentType: 'multipart/form-data',
 data: file,
 processData: false,
 async: false
}).done(function(){console.log('uploaded');});
request.status

Response

The successful response returns a 204 status code.


Remove the Picture for a Logo or a Background Image

To remove a picture for a logo or a background image, make a DELETE request using these endpoints:

  • /{tenant}/logo
  • /{tenant}/backgroundImage

Example of removing a logo picture:

Request

  • Method: DELETE
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/logo
  • Headers
    • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and have the scope hybris.cecenteruiconfig_manage.
  • URI Parameters
    • {tenant}: The name of the current tenant

Response

The successful response returns a 204 status code.


Error Types

For information about error codes, see the API Reference.


Retrieve User Scopes

This example shows how to retrieve all user scopes.

Request

  • Method: GET
  • Request URL: https://api.beta.yaas.io/hybris/cecenterconfig/v1/{tenant}/userScopes
  • Headers
  • Authorization: This includes a valid OAuth2 access token. To access this method, the access token must be issued for the requested tenant and requested user. Also, the scope hybris.cecenteruiconfig_view is required.

    For more information about issuing an access token for the requested user, see the OAuth2 topic.

  • URI Parameters
    • {tenant}: The name of the current tenant

Response

A successful response returns a 200 status code. The JSON response content looks similar to the example shown:

[
  {
  "scopes": "hybris.email_view hybris.serviceticket_configuration_delete hybris.checkout_manage hybris.email_admin hybris.shippingcost_read hybris.price_manage"
  }
]


Glossary

TermDescription
Agent HomeThe launchpad that provides access to the Engagement Center solution. The Agent Home consists of the main header bar that permanently displays, regardless of which Engagement Center feature is in use, and various tiles.
Engagement CenterThe abbreviation of SAP Hybris Service Engagement Center. The Engagement Center is a multichannel customer engagement solution and next-generation interaction center that allows organizations to deliver convenient, contextual, and relevant service experiences to their customers. The SAP Hybris Service Engagement Center software as a service integrates customer service with digital commerce, before, during, and after the buying process.
action areaAn area in the engagement context, where agents can trigger additional actions.
business documentA document that contains information about a business object. Business documents are used in customer engagement for data exchange and data processing.
business document typeA configuration that collects the runtime data of a business document, necessary for the engagement context to process business objects. For example, an account or a service ticket.
consentPermission to access (read, write) specific profile data. For example, permission to read/write age estimation or physical address. A consumer and a tenant can grant and revoke consent for subsets of their respective data.
endpointA URI that developers point to when communicating with an API.
engagement contextThe central work environment for an Engagement Center agent that consolidates all attributes and object references that support the control and orchestration of the communication process, the interaction process, and the supported business processes for an interaction with a customer.
header areaAn area in the engagement context that is used for account identification and is configurable to show additional business-related data.
key of business document typeA unique identifier used to represent a business document type in the configuration.
productAny kind of physical item that can be defined or described with help of some properties and that can be sold for a certain price.
tileAn application that is part of the Engagement Center.
work areaAn area in the engagement context, where agents process customer data and execute business transactions.


  • Send feedback

    If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.

  • Get Help

    Use our private help channel. Receive updates over email and contact our specialists directly.

  • hybris Experts

    If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.