In Release 9.0 and earlier releases, the Sterling Business Center application used Ext JS JavaScript framework, Version 2.0 in the Web UI framework. However, in Release 9.1 (and later), the Sterling Business Center application uses Ext JS JavaScript framework, Version 3.0, in the Web UI framework.
The change in the Ext JS JavaScript framework version will not impact you if you have not customized the Sterling Business Center application, and used the application with the out-of-the box features and behavior.
If, however, you have customized the Sterling Business Center application and you are planning to upgrade the application to Release 9.2 (or later), the newer version of Ext JS JavaScript framework may impact your customized components.
Table 1 describes the impacted components and modifications that you must perform to address the issues that may occur due to the change in Ext JS JavaScript framework version.
| Affected components | Required modifications |
|---|---|
| Button | Impact: Buttons are not displayed correctly. Solution: The x-btn-left, x-btn-center, and the x-btn-right css classes have been replaced with the x-btn-ml, x-btn-mc, and x-btn-mr css classes respectively. The new entries are x-btn-tl, x-btn-tc, x-btn-tr, x-btn-bl, x-btn-bc, and x-btn-br. Note: The size of the buttons
displayed in Ext JS JavaScript framework,
Version 3.0 is larger as compared to the same in Ext JS JavaScript framework, Version 2.2.1.
|
| Toolbar | Impact: A screen does not open if a Toolbar contains
buttons. Solution: The xtype value of a toolbar button in Ext JS JavaScript framework, Version 2.2.1 is “tbbutton”. However, in Ext JS JavaScript framework, Version 3.0, the xtype value of a toolbar button is “button”. Therefore, all the occurrences of “tbbutton” must be manually replaced with “button”. |
| Screen | Impact: A screen is not displayed correctly if any component
is dynamically added to the screen. Solution: When a component is dynamically added to a screen, the doLayout method must be called. Note: This method must
be called only once after all the dynamic components have been added
and this method must not be called in a loop.
|
| Radio button | Impact: Radio buttons are displayed with incorrect font. Solution: The display of the radio button has changed because the Ext.form.Radio/Checkbox widgets UI was reverted to the native widgets. Ensure that the “sc-plat-radiolabel” radio button class overrides the “x-form-cb-label” instead of “x-form-radio-wrap”. |
| Menu button | Impact: menu buttons are displayed incorrectly. Solution: Ensure that the menu button options for the menu buttons are “menuitem” instead of regular buttons. |
| TriggerField and ComboBox | Impact: The following UI widgets are not aligned properly
on the screens:
Solution: The "sc-plat-triggerfield-text" css class and the "sc-plat-combo-selection" css class must be used instead of the "sc-plat-editable-text" css class for TriggerField and ComboBox. |
| Screen | Impact: Screens are not displayed properly if the getSelections()
method of Ext.grid.GridPanel is used. Solution: The getSelections() method on Ext.grid.GridPanel has been deprecated. All occurrences of this method must be replaced by the getSelectionModel().getSelections() method. |