Commerce Layout Editor

Overview

The Commerce Layout Editor provides the same functionality as the previous editors combined with improved usability. The new Commerce Layout Editor provides administrators with a simple and intuitive way to create and edit JET and legacy Transaction UI pages within Oracle CPQ. This editor provides the groundwork for a common user experience across all Oracle CPQ administration pages.

Refer to the following videos for the Commerce Layout Editor.

  • Oracle CPQ JET Commerce Layout Editor Watch Video  Video icon
  • Oracle CPQ JET Commerce Layout Editor - Demonstration Watch Video  Video icon

The editor contains a layout panel and a collapsible side panel. Administrators can easily select items from the side panel and drag-and-drop the item into layout.

ClosedJET Transaction UI User Side

ClosedLegacy User Side Transaction UI

ClosedCommerce Layout Editor

Administration

Layout Elements

ClosedLayout Title

ClosedPanels

ClosedTabs

ClosedColumns

ClosedSpacers

ClosedToolbars

ClosedLine Item Grid

ClosedeSignature Table

Attributes, Array Sets, and Actions

ClosedAttributes

ClosedArray Set Tables (Transaction Arrays)

ClosedActions

Notes

  • The FullAccess user must be careful when using alternate stylesheets as it can affect the enhanced commerce UI adversely. Some things to look out for are resizing menu or text type attributes, placement of HTML attributes, and so on. Also, the FullAccess user should test any alternate CSS on all supported browsers since CSS behavior can vary greatly by browser.
  • Deleting a layout container like a panel, tab or column layout will delete all elements within the container as well.
  • You cannot mix pixels and percentages within a column layout.
  • HTML attributes that contained malformed HTML might break the UI. The admin is advised to check if an HTML attribute contains tags that are not enclosed in tags.
  • Including prototype.js in the header or footer of the transaction page may interfere with the functionality available to the end user, such as switching tabs, uploading files using the File Attachment attribute, expand/collapse of line items, and so on. Admins are discouraged from using prototype in any advanced customization on the transaction page.
  • The Main Document layout editor looks the same as the Sub-Document Layout Editor. The only exceptions are that in the sub-document layout editor, you cannot add attributes , you can only show line item attributes, and Add Action Strip only shows line item commerce actions.
  • Height of spacers, attributes and action strips within a column are consistent in the Layout Editor. All layout elements within a column are drawn with the same height on the Layout Editor for better usability.
  • Numeric fields can only have the value field right-aligned in the line item grid.
  • Horizontal scrolls are not provided by default. If the column width is bigger than the page width, then some fields may appear to be cut off on the transaction page. The admin can enable the horizontal scroll by using the alternate stylesheet.
  • Single-select menus and multi-select menus can be changed from one to another, but they first have to be removed from the layout and then changed in the attribute editor itself.
  • If labels intrude into the column space, either increase the label width or provide a space in the label text so that it can wrap.
  • Refer to Stylesheet Manager > JET UI Style Customization for information on the following JET UI CSS customizations:
    • Force Content to Stay in a Fixed Position (Non-responsive behavior)
    • Create Sub-Headers Styles
    • Create Tab Label Styles
    • Create Button Styles

Related Topics

Related Topics Link IconSee Also