Let's say you are going to build a brand new component in PeopleSoft Application Designer. Would you build it using
- Classic,
- Classic Plus, or
- Fluid?
Here is how our LinkedIn audience answered that question:
Why Fluid?
Over 50% of our audience chose Fluid, and here are some reasons:
Strategic Direction
Fluid is Oracle's strategic direction. This means everything new that Oracle builds will be built in Fluid. If Fluid is Oracle's strategic direction, perhaps it should be ours as well?
Accessibility
Fluid generates better markup for screen readers and other accessibility features. If you must comply with the New Rule on the Accessibility of Web Content, then Fluid is your best option.
Mobile and Touch Friendly
Fluid is touch-friendly out of the box. Data entry fields have more space around them, and buttons are larger to facilitate touch. Through adaptive style classes and adaptive PeopleCode, Fluid can render better on mobile, whereas Classic renders the same across all devices.
Styling and Layout
Fluid offers more flexibility than Classic through grid types, HTML elements, and the PeopleCode function AddStylesheet.
Is Classic Still Relevant?
With so many good reasons to choose Fluid, is there still a case for Classic? We believe the answer is, "YES!" Many PeopleSoft-delivered business processes are 100% Classic. If you are extending an Oracle-delivered business process with a new component, it might make sense to build that component in Classic. Otherwise, your new component would be the only Fluid component in the business process. Another reason to choose Classic is that you prefer Classic features, such as highly flexible Related Content at the bottom of the page or traditional Scroll Areas.
Where Does Classic Plus Fit?
Classic Plus is Classic with a different skin. All Classic features apply to Classic Plus. Development for Classic Plus is nearly identical to Classic. Since Classic Plus requires more area, the only development consideration is spacing: Is there enough room?
Classic Plus makes Classic content look like Fluid, but not behave like Fluid. It just changes the PeopleSoft theme to look like Fluid. Classic Plus is a great way to make your existing Classic pages merge with a new PeopleSoft-delivered Fuid experience. Alternatively, Classic Plus is a great way to make PeopleSoft's Classic content merge with your new Fluid content.
So what do you think? As you consider new components, will you create them in Classic, Classic Plus, or Fluid?
At JSMpros, we teach PeopleTools tips like this daily! Check out our live virtual events calendar to schedule your next class. Interested in learning more about Fluid specifically? Then be sure to check out our Fluid-specific collection!
All of our classes are available live, live virtual, and on-demand. Want to learn more? Contact us, and let's get you scheduled!

No comments:
Post a Comment