Skip to main content

We have multiple companies running in the same IFS tenant, and some associates have access to the multiple companies. We’ve created appearances for each company to help lessen any confusion. The issue is on screens like Customer Agreements and Customer Financials - when you change the company option on the local page the Appearance Configuration doesn’t automatically update to the newly-chosen site’s appearance. Is there a way to have sections like Customer Agreements and Customer Financials update their appearance automatically?

 

Note - we have thought about trying a workflow but haven’t yet.

To change the Appearance Configurations on company-specific subpages like customer agreements and customer financials, you can follow these steps:

  1. Access the Appearance Configuration page.
  2. Create a new Appearance and set the context to match the company-specific subpages you want to customize.
  3. Set Appearance Properties for each theme, such as Light and Dark, based on your preferences.
  4. Save the changes, and the new Appearance will be created in an ‘Unpublished’ state.
  5. Ensure to map the Appearance to the specific subpages like customer agreements and customer financials for the changes to take effect ​

How to configure and map appearance - Technical Documentation For ... - IFS

 


Hi Tony,

Thank you for the follow up! 

How do I map the appearance to specific subpages? Via a specific Context Expression or something else?

Right now I’m using the COMPANY context expression already, one for each active Company. While that works for standard log ins and general pages, it still requires a full screen refresh when getting into the subpages where users can change their company. 

 

 

Thanks,

Crystal


Hi,

Appearance configuration company context mapping works for the default company that the user is assigned to. When the application starts, it evaluates if the default company that the user is assigned to has any matching appearance configurations and applies the changes. Switching the company context in the page level won't affect the appearance configuration that was applied at the application startup.

Default company


However, when applying the page level company context, if the user selects "Apply changes to all pages", then that company gets applied globally for the current user session. Therefore, if the user reloads the page after this, if there is an appearance configuration published for that specific company, it gets applied.
 

Appling global context values


But this is only works for the current session. When the user logs out and logs in again, the global company fallbacks to the default company.


Reply