Reworking Components for Classic Plus Display

If you have custom classic components that your end users access along with fluid components and you want to provide a more uniform experience, you can set your components to display in classic plus as described in the previous section. Before end users access classic plus components in a live system, verify that the classic plus rendering continues to meet your requirements and rework and reposition any of the page elements as needed. Using the page preview feature in Application Designer, you can preview any classic page definitions as classic plus, regardless of whether the component property is enabled for classic plus. See “Previewing a Page as Classic Plus” in Previewing Classic Pages for more information.

Note:

The page controls on these classic plus pages will resemble the page controls on fluid pages. However, because these components and pages remain as classic definitions, certain aspects of the PeopleSoft fluid user interface experience will be absent—for example, dynamic, responsive rendering across all supported device types.

The following list provides a set of guidelines to assist in the transition from classic to classic plus for your custom components:

• Perform side-by-side comparisons with the page in classic and classic plus to help identify rendering, alignment, and behavior issues.

• Classic plus incorporates larger font sizes and larger control sizes, which means the page layout requirements can increase up to 20% in some situations. In addition, PeopleTools adds some vertical padding to reduce clutter between page controls, which increases overall page height. Look for overlapping issues, text truncation issues, alignment issues and so on. Typically, you can adjust the page controls slightly in the page definition to resolve these issues.

• If the page appears to have grown too big when rendered in classic plus, try to reduce the white space in the page layout and look for ways to use the space more efficiently.

• The PeopleTools Save button (the delivered Save button), renders as the primary button in classic plus by default. If you do not have the Save button on a page, or you have a set of custom buttons on your page, you may want to set one button as the primary button.

  To make any button other than the PeopleTools Save button a primary button, open the Push Button/Hyperlink Properties dialog box for that button. On the Use tab, select the Activate by Enter Key check box. With this selection, the system renders your button as the primary button on the page, which end users recognize by its solid color.

• If you have custom buttons, remove any images in the buttons for classic plus rendering.

• If you are using images in your page, they must be scalable vector graphics (SVG).

• Make sure to test all page control types, such as grids, scroll areas, group boxes, drop-down lists, date selectors, hyperlinks, and so on.

• Test classic plus pages in all of the browsers used by your organization.

• If a page contains HTML areas, custom style classes, or custom style sheets, you need to update the custom HTML and CSS manually to match the classic plus experience.