- 8 Posts
- 1012 Views
New fluid pages use conditional navigation, when user clicks on classic pages they might be routed to fluid pages, this is because of conditional navigation enabled on classic content reference
Enable fluid approvals refer to my blog: http://peoplesoftfluidui.blogspot.com/2018/07/mobilefluid-approvals-in-peoplesoft.html
For migration of tiles created from online, use Data Migration Workbench, PTPPB_GROUPLET is the data set that stores your delivered/custom tiles
We are planning on activating Fluid in FSCM during our update. We've heard of many issues with migrations and are wanting to discuss approach you've taken to migrate Fluid successfully. Is anyone willing to meet with us for about one hour or less to review?
Hi Evonne -
I saw these posts while skimming Technology forum for Fluid-related content, so thought I'd chime in. I agree that many of the Fluid pages being delivered fall into the HCM & Expense area. However, we're about to upgrade to PeopleTools 8.56 and we're rolling out Fluid Homepages & Navigation Collections so our administrative users can reach their classic PS screens in far fewer clicks. That conversion will let our users access PS HCM, FIN, Campus Solutions, and Integration Hub faster & easier. So that's another possible option to consider, on the Fluid continuum.
Adding to @Scott Hirni commentary - keep in mind the technology change is only one aspect of this move. Fluid UI presents a vastly different navigation than homepages, breadcrumbs, menus, etc, users are accustomed to. It's not an intuitive move from a top/left navigation to a double-sliding right-side navigation. Some of the header links behave differently. Simply dumping a new user interface on the user community is asking for issues, and throwing a bunch of training documents at them creates more work. In my work the best way I've seen to facilitate a transition is to meet with to-be-affected users and understand what they do. Then, as you prep to roll out Fluid, roll it out in a way that minimized the gap between classic and Fluid. that may mean pulling some tiles off the landing pages, limiting the number of landing pages, removing a few of the options on the nav bar, maybe even leveraging the classic homepage as a way to help users adapt. Various tactics work but they aren't universal - they are user group specific and your users might respond favorably to some vs others. Engage a small group of users, ask what they do, try to see the world of PeopleSoft from their perspective and in the words of their user stories.
@Alexandria Heitzer Hi Alex, Fluid can be very straight forward or not depending on the path you take. If you go with the delivered Fluid and Classic Plus pages from Oracle as is then Fluid works great and will offer your users a much better user interface and user experience than pre 9.2.
If you need to configure (not customize...more on that in a minute) and use the features delivered in applications and PeopleTools then, again, things will be straight forward. Yes there will be some things you will need to learn but that is no different than any other release of PSFT or Tools.
Where I have seen customers have challenges is dealing with customizations. If you have taken delivered PeopleSoft screens which are now Fluid you have a choice: redo them in the new Fluid screens, move them to an extension using the configuration tools in PeopleTools (preferred) or move them to bolt ons and use Classic Plus to make them look like Fluid.
There are multiple nuances of what I wrote above but quickly that sums it up. As background, until this year, I spent 17 years at PeopleSoft and Oracle focused on PeopleTools including Fluid and user experience. I am more than happy to spend some time with you on the phone discussing in detail what I have mentioned above as it is the same conversation I would have had if I was still at Oracle.
@Alexandria Heitzer Hello,
We did enable FSCM Fluid 8.55/9.2 at our organization we did not notice any issues while enabling fluid, most of the steps for configuring fluid is from online, so we followed these steps for enabling fluid in Test/QA environments and on the go-live day we flowed exact same steps for successful fluid implementation.
Few things to keep in mind:
Let me know if you have any specific questions