Skip to main content
December 30, 2025
Question

Dynamically changing an interface depending on the website

  • December 30, 2025
  • 7 replies
  • 0 views

Hello, 

I am currently working with a record which is being used in 2 different websites on the same environment. These 2 websites have a different look and feel, and some record informations should only be displayed on one of the website, but not on the other one.

Is there a way to keep using the same record on these 2 websites, but have the summary interface dynamically change depending on the website it is accessed from ? For instance, if we access the record from website A, some cards are hidden, whereas if we access the same record from website B, the same cards are showing.

So far I haven't been able to find a way to "detect" the active website from my interface, and I am not sure this is possible.

Thanks

7 replies

stefanhelzle0001
December 30, 2025

What "website" are you talking about? Is this about embedding Appian SAIL UI into externally hosted HTML content?

December 30, 2025

Hello Stefan,

No, the websites I am talking about are Appian sites. I have 2 differents sites in 2 differents applications, on the same cloud environment.

One of my record type is used in both these sites. I would like to know if there is a way to customize the record views depending on the site it is accessed from. For instance, if you access the record view from the first website, you would have access to some information, but if you access the same record from the second website, these informations would be hidden.

stefanhelzle0001
December 30, 2025
mikes0011
Brainy
December 31, 2025

Will the 2 different sites both be accessed by the same base of users?  If they're targeted at separate (or even mostly-separate) user subsets, you would simply need to use group-checking functionality in the SAIL code to determine which elements to show.

If both sites are expected to be used by the same users or a largely-overlapping base, then I'm less sure what you can do.  I can't think of anything off the top of my head that allows you to detect (from interface code) what your current "parent site" is, apart from doing something hacky (and, notably, un-supported) like generating a URL and then seeing which site string it contains, if it's even still possible.  Not that I'd ever do that.  *looks around innocently*

January 5, 2026

Hello Mike, 

I think I found a way to do it in the end by doing so : 

  • Defining 2 distinct summary views in the Record Views (one for each site)
  • In the recordLinks, specify which view to access depending on the parent interface

The only problem with this solution is that you have to disable the record header, or else you can't hide the "unused" summary view in the tabs. So you have to recreate your record header directly in the interface, which can be a bit annoying.