What a great topic! I’ll gladly provide some content soon!

Some great presentations from Accelerate. Looking forward to the Tiles/Column Set management improvements. Also, as mentioned, user management.

From a Legacy perspective, managing layouts via configurations has been the same for… a decade +? While it’s second nature for long term Planview developers, I’d wager newer admins are surprised to see what it takes to make a layout. In this day and age, “modern” would be a layout builder similar to power apps. Based on the component you chose, you select the properties to add from a list. You don’t have to look up UUIDs. Security would be universally controlled for both Column Sets and Layouts in the same place. Layouts is an area where SO much can improve, however, so much would have to be re-worked if you did so. However, I’ve often built secondary data management sites (such as a SharePoint forms) for data collection as it allowed me extra room for customization of the form, including more help text for improved context. I’d like 100% confidence that a user could manager their data in EA, and never have to build a secondary mechanism again.

As far as tiles, I want a generic tile for HTML links. This would help me embed Power BI reports hosted in my Power Bi Workspace. Also, when selecting “More” my users will tell me “I don’t see anything under More!” Then, I have to tell them to select Manage. It’s a tiny bit confusing. Most users are not aware that there are tiles available, they just aren’t on THEIR respective tileset.

As far as users, smart is remembering what they did most often in the UI. What instances have they visited the most? What were their most used tiles? What are their “Favorited” instances (the standard star you can select/unselect). Etc.

As far as metamodel, two common properties I add to Generic Components are “Integration Source” and “Alternative ID” (or some name similar). I find both of these extremely useful when working with integrations and believe they should be added to a higher archetype and therefore trickle down. Integration Source is filled in with the source of data (if automated, example “ServiceNow,” “Apptio”). Alternative ID should be used for primary keys/locators you don’t want searchable in the main search bar. Only locators - example an alias such as the Application ID or Acronym - that you want searchable via the main search bar should go in External ID.

Those are some thoughts off the top of my head...

Previous Planview EA announcements mentioned ‘Next Gen forms’ to improve the edit/view screens. I have not seen this development in recent announcements and I am curious if and when this will receive attention.