Understanding UI Override Controls

Process flow type panels are made up of a data area or UI map fragment. The delivered start, stop, and transfer process flow type panels are built using data areas. Instead of a single data area, these panels are built using nested or included data areas. This is done to facilitate custom extension of the data area at the lowest. This is useful when your business rules include adding something at the end of one of the delivered sections. However, there are times when your business rules are more complex than just adding on to a delivered section. Some of the UI sections that are delivered can to be overridden with a custom replacement UI section. This logic is enabled through UI Override Controls on the request types.

The start, stop, and transfer processes each contain a summary header that is show at the top of each step in the process that can be overridden. By overwriting this, you can create a custom header that is displayed throughout the process flow.

When starting service, especially for a new customer, business rules can differ between different organizations or within different operating units of the same organization. For example, a utility with customers in different states may have different requirements around verifying identity or checking credit. The sections responsible for new customer and existing customer identification can be replaced with a custom experience using the UI override controls.

When the request type indicates that the UI section is overridden, the extension data area replaces the UI component of the delivered data area that it extends. It does not override or replace the data area’s schema