The preview release of Platform update 33 for Finance and Operations is now available (general availability is scheduled for March). This is part of a series highlighting features in the new platform update.
A quick refresher: saved views enable users to save sets of personalizations on a given form. Forms have a standard “classic” view. When personalizations are made, an asterisk identifies that the classic view has changed, providing the user with the option to save the new view.
In manage my views, users have the option of reordering, renaming, and setting the desired default from their personally available views. Additionally, the publish button in manage my views allows users to share their views with the larger organization by role and legal entity.
(The ability to publish views is limited to system administrators and those with the “Saved views administrator” role)
Publish as Default View
Platform Update 33 extends the publish view functionality, the publish as default view toggle enables a published view to be the first view a user sees when accessing a form – instead of the form opening in “Classic view” and the user having to select the desired view or configure the default individually.
In the example below, I have a “Simple view” for the project form where infrequently used buttons and fields are hidden. I would rather users be direct here first, with the option to view the full “Classic view” information if necessary, so I have published the “Simple view” as the default.
Managing Published Views
All views are visible in the personalization form. Clicking the publish button on a published, unpublished, or personal view allows management of access and presentation of the view.
I would be grateful if you take a screenshot of this post and share it on social media. You’ll be publishing a view – saved from my published, saved view on saved view publishing.
One can only hope that will lead to more views.