Tag: MenuConfigs (Messages)

Messages 4

Results:

Thu, May, 20th 2021

BC:
Tech Best Practices week continues today with Part II of Menu Configurations Best practices!
• If you want a menu item to be visible, but only actionable when certain conditions are met, use a “valid when (…)” statement to identify the condition that must be met for the menu item to work.
• Wanting to switch the menu item from a delivered page to an external link because you’re using a 3rd party vendor for payroll, for example? Use “//”in front of the row of  Read more...delivered LPL to “turn it off” and then add a row with “link is external https://....” to send the user to the 3rd party system. That way, if you switch off of the 3rd party payroll system and implement the HR Payroll module, the menu connections to the HR Payroll pages are still there and can more easily be restored. Note: This only works in the Web-browser Configuration Console, not Rich Client.
In summary, DON’T DELETE! Spending a little time now to understand the delivered menu code, can make things much easier for you in a later phase when other modules are turned on. If you follow these practices in your menu configurations, those coming after you will thank you! More questions on menu configurations? Contact Bails! #MenuConfigs #Infor #FSM #HCM #Bails #InforPartner
 Show less...
Delivered Read
1
Wed, May, 19th 2021

Part II of Menu Configs Best Pract’s: use “valid when (…)” when you want the menu item active and “//” to turn off code when all else fails. DON’T DELETE! Those coming after you will thank you. More questions? Contact Bails! #MenuConfigs #Infor #FSM #HCM Read more... #Bails #InforPartner https://t.co/PPjLpb3J5C Show less...
Delivered Read
Mon, May, 17th 2021

BC:
It's Tech Best Practices week at Bails! Today we’re looking at Part I of Menu Configurations Best Practices! There are a few best practices when it comes to menu configurations that will prevent heartburn in later project phases:
• If a menu item has “visible when (…)” and a condition in the parentheses, know that that menu item will only show once those conditions are met. These are usually tied to an Org Config page where modules are checked to “turn them on”. Leaving  Read more...these menu items alone rather than deleting them out of the menu, will enable them to show up immediately once those conditions are met, like in a later project phase.
• If a menu item does not have a condition for being visible and there is a desire to hide it for a more streamlined end-user experience, adding in “visible when (false)” hides the menu item without deleting it, so in later phases no one has to compare the current menu configuration to the delivered to figure out if a menu item needs to be added back in to get it to appear. Someone can simply remove/comment out the “visible when (false)” phrase and the menu item re-appears.
Can’t wait for Part II later this week? Contact Bails! #MenuConfigs #Infor #FSM #HCM #Bails #InforPartner
 Show less...
Delivered Read
1
It’s Tech Best Practices week at Bails! For Menu Configurations, understanding the “visible when (…)” conditions or using “visible when (false)” to hide instead of deleting can prevent heartburn later! Stay Tuned for Part II. #MenuConfigs #Infor #FSM #HCM Read more... #Bails #InforPartner https://t.co/kJJIJG1SPg Show less...
Delivered Read

Online