Skip to main content

UI Config Best Practices

  • January 16, 2025
  • 3 replies
  • 196 views

Forum|alt.badge.img+8

We are planning to roll-out IFS to a large number of lower-tech users and want to make the user interface as simple and as standardized as is possible. We have researched a number of ways of doing this within IFS 23R1. Through these discussions, we have identified a number of methods (below). However, I would like input, ideas, and suggestions based on other’s experience in this and later releases. Please comment and share.

  • Navigation Screen - Had to go through and hide all the menus under one profile to then allow us to selectively reveal what we want users to see.
  • Screen, Column Layouts, Command Buttons, Saved Searches, Field Position, Field Renaming - Use Page Designer. Be sure to deploy changes through BuildPlace to make these permanent through deliveries.
  • Start Page, Bookmarks, Table View v. List View - We created the idea of a Job Role Template (JRT) which is a dummy user that has the bookmark configuration desired and then use this as the basis for adding users. However, this doesn’t update existing users if we want to make a change.
  • Field Level Security - If we want one group of users to have different access to a field than others, we have needed to create a customization to check a user attribute or their security before accepting the value.

 

3 replies

Forum|alt.badge.img+4
  • Do Gooder (Customer)
  • 19 replies
  • January 16, 2025

We are just now starting our upgrade from apps 10 to cloud and will be tackling this same exact problem. I feel like option number 2 seems the most robust and permanent out of the listed options though. 


eqbstal
Superhero (Partner)
Forum|alt.badge.img+21
  • Superhero (Partner)
  • 677 replies
  • January 16, 2025

@CRUNDELL Valid points. From my perspective as an employee of an IFS partner I would say:

  1. Whenever someone gets access to functionality, the navigator option to get there is automatically opening up. A start page, use a lobby page, like the Central ones, would help to select the correct option.
  2. Column Layouts and Saved Searches are part of the user profiles. So these fall under third point. It is good to use BuildPlace, but be careful with it. The more you build (and make it easier for the end user), the further you away from standard IFS. This will be noticed most by IT team at the moment of a new version (remember: 2 per year) and all the changes have to be rebuild in next version, tested, approved, documented etc.
  3. I think that all are hoping that something to this will be done by IFS in a newer version. The usage of profiles is not at all up to the level that it was in IFS10 and before.
  4. There are option in the page designer for that now (see point 2). Another option might be to use the context that is available per page. Please investigate if the context rules are enough for your company to make this work.

Forum|alt.badge.img+4
  • Do Gooder (Customer)
  • 19 replies
  • January 16, 2025

@eqbstal 

“It is good to use BuildPlace, but be careful with it. The more you build (and make it easier for the end user), the further you away from standard IFS. This will be noticed most by IT team at the moment of a new version (remember: 2 per year) and all the changes have to be rebuild in next version, tested, approved, documented etc.”

This is a good point, but I would guess that if this approach is taken then it would be by the IT team directly and they would have to manage these configurations the same as they would any other in cloud. As long as they stick to sensible configurations instead of customizations then the deviations from standard IFS should be minimal.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings