Screen Configuration Maintenance – In Mind Cloud

Adding / Removing Fields

Following a zero-code approach for configuring the Commerce application's look and feel, Screen Configuration enables the application administrators to enable/disable fields as well as rearrange the sequence of the same.

As an example, the following screens can be configured (not a finite list):

Product Card (Tile)
Product Card (List)
Product Detail
Equipment (Tile)
Equipment (List)
Shopping Cart (Order)
Shopping Cart (Inquiry)
Checkout Order
Review Order
Reorder
Review Reorder
Order History (Overview)
Order History (Detail)
Order Amendment
Inquiry History (Overview)
Inquiry History (Detail)
etc.

Depending on the screen itself, different sections are available. For example: the fields available on the 'Order Checkout' screen is depicted in the following figure:

For each section, the administrator can take the following actions:

Display / Hide Label by selecting the respective toggle switch state
Change/define the localization
Hide fields from the UI by selecting the respective toggle switch state (only available for sections that can host more than one (1) field)
Re-arrange / change sequence by dragging/dropping the respective rows (only available for sections that can host more than one (1) field)

Certain sections (e.g. 'Line Item Header' and 'Line Item Sub-Header') can only host one field. In this case, the administrator is only allowed to change the field. For the other sections (e.g. 'Line Item Attributes' and 'Order Attributes'), the user can decide which fields to be printed:

Selecting / Swapping Fields	Adding Additional Fields

As we're following an API-first approach, the administrators can also traverse through the data structure by accessing related/nested data points, e.g. the product is part of the line item, hence the product information can be accessed by leveraging the following relation:

Indicating Fields for Validation During Checkout

For the checkout relevant screens, input fields can be marked to indicate a server-side validation. If e.g. the PO Number is required to be validated upon entry (because there may be a changed pricing behavior), then the toggle switch for the fields 'Validate' can be set to 'True':

In the above example, when the user performs a checkout and enters a PO number, the system will trigger a pricing call. On the opposite, if Billing and / or Shipping Address info is entered, the system will not trigger a round-trip to validate the entries made.

Product Detail Specific Configuration Capabilities

For Sealed Variants (i.e. configurable products with pre-selected attribute values), Commerce Administrators can decide whether to print a Technical Specification of the specific variant on the Product Detail screen: