Customer Detail View

The Customer Detail View screen shows details of the selected customer(s).

The top part of the Customer Detail panel displays all the columns and their values for the selected customer (table view preferences are applied).

The empty canvas below is fully customizable – you can add as many portlets as you wish, you can resize them and change their position. If there are many portlets on the canvas, making the content difficult to read, you can open a portlet in a pop-up window by selecting the option Open in Dialog in the 3 Dots menu. Table layout changes in portlets can be saved as a preference.

The default portlets are:

• Customer Text – Displays text and images.

• Customer Assignments – Shows all Manual Price Lists, Price Lists and Live Price Grids which are assigned to the selected customer (or to a group to which the customer belongs).

• Customer Quotes – Displays all Quotes related to the selected customer.

• Customer Agreements & Promotions – Displays all Agreements/Promotions related to the selected customer.

• Customer Rebate Agreements – Shows all Rebate Agreements assigned to the selected customer (or to a group to which the customer belongs).

• Change Requests – Shows all Data Change Requests related to the selected customer.

• Price Records – Shows all Price records associated with the selected customer (or with a group to which the customer belongs).

You can also add your own portlet representing:

• All Customer Extensions – Any CX table you create can be used as a portlet.

• Additional charts/tables based on Datamart – Defined in Customer Query Chart Definition.

• Additional calculations – Defined in Customer Detail Logics.
  For example, if you have a large amount of data for one customer, you may want allow your end users to view just some of this data and grouped according to their needs. Using a portlet, this can be done dynamically and without the need to duplicate the data in a CX column in a certain structure (which leads to an integration overhead for a "just in case" scenario). The solution is to configure a Customer Detail Logic that gathers the data and formats it in a result matrix. It is basically a logic-driven mini dashboard inside the Customer Details View. The logic gets the customer context and is re-executed when the user changes customer in the left-hand navigation list.