Behavior of portlets and backward compatibility

The behavior of portlets and the aspects of backward compatibility of the application.

Backward compatibility in the new release is made possible through the "Layout For New Home Page" rule in Sterling™ Business Center, which allows you to keep all the extensions as-is and take adequate time to test and adopt the new changes.

When you configure the application to use the fixed layout, it forces the application to revert back to the earlier layout, before adoption of new features.

If the "Layout For New Home Page" rule in Sterling Business Center is set to "Fixed User Interface", the fixed UI layout is enabled. If set to Persona-based Interface, the new UI layout is enabled.
  • Old specification portlets do not contain the personaConfig JSON attribute and new specification portlets contain the personaConfig JSON attribute. The following table describes the behaviour and visibility of the portlets based on the value selected for the "Layout For New Home Page" rule.
    Table 1. Behaviour and visibility of the portlets
    Layout For New Home Page Behaviour and visibility of Old specification portlets Behaviour and visibility of new specification portlets
    Fixed User Interface
    • Only old specification portlets are displayed.
    • Since there is no associated persona, the sequenceNumber attribute determines the ordering of portlets.
    • The showPortlet and resourceId attributes determine the visibility.
    		None of the new specification portlets and More Tasks portlets are displayed.
    Persona-based Interface
    • All visible old specification portlets are ordered according to the sequenceNumber and added after the More Tasks portlet.
    • Since no personaName is defined, all old specification portlets are added for every persona.
    • A console warning about the misconfiguration is logged. It indicates that new persona-based AngularJS page is being used with old specification portlets and you need to upgrade your portlets.
    • The new specification portlets are displayed and ordered based on personaSequenceNumber
    • All new specification portlets and More Tasks portlets are displayed.
    • Old specification custom portlets are displayed after the More Tasks portlet.
  • Table 2. Behaviour of the footer based on the value of the Layout For New Home Page rule
    Layout For New Home Page Footer
    Fixed User Interface The old footer options - Manager Dashboard and Dojo Order Fulfillment are displayed.
    Persona-based interface All personas defined are fetched. Display is based on the following factors:
    • Presence of at least one portlet that uses the persona (personaName).
    • User has permission to access the portlet (resourceId).
Manager Dashboard and Dojo Order Fulfillment persona:
  • These are two special personas that do not have any direct portlets. You should not register any custom or overridden portlets against these personas. To check if a persona is special, use the iscPersona.isSpecialPersona(personaName) method.
  • They are also displayed based on permissions for these screens. In case new resource permissions for Manager Dashboard and Dojo-based fulfillment screens need to be added or changed by customization teams, you can use: iscPersona.setSpecialPersonaPermissions(personaName, resourceIdString, overrideFlag)
    • personaName: Name can be a special persona. There are two special personas namely: "Manager_Dashboard" or "Dojo_Order_Fulfill".
    • resourceIdString: String containing single or multiple resource ids to associate with persona. In case of multiple, separate the ids by a pipe |.
    • resourceIdString - Set true to replace all existing permissions with resourceIdString passed. Otherwise, new permissions passed will be appended to list.