I would like to create a Portal with initial page that will have a field for code input, and after submitting the code, second Portal/Interface or page will reveal with more info. I also want few variations of the code, so a different code will show us different interfaces.
How can this be achieved from a technical point of view? What solutions do I need to use ?
Any advice is welcome. Thank You in advance.
Discussion posts and replies are publicly visible
I managed to create Interface that will "showWhen" (visibility is set to a condition) and it works fine. On start, the Portal only shows the field for code input, after I submit correct code, it reveals the hidden components.
What comes to my mind, is this "hidden" component truly hidden? I mean, is the data secured?
When I enter DevTools (by clicking F12), in the web elements, the hidden elements are missing, until they are revealed. Does this mean they are secured and cannot be entered/seen/copied etc until I submit my code?
Also another question is about Portal Interfaces.
Appian docs mentions about Initial Interface and Secondary Interface, where in the Initial we cannot use Rule Inputs, and in the Secondary we can use them. Am I understanding that correctly, that my Initial Interface is the one with field input, and Secondary is when the rest components are revealed? As an object, it is still a single Interface but with visibility options. Can someone enlighten me what really are Initial and Secondary Interfaces and how to properly create them (in case I am doing it wrong)?
Hi Marcin! I'm a product manager at Appian working on Portals features. The answer to your first two questions is "yes" -- based on the showWhen configuration you described, the data in the component would be hidden and would not be seen until you submit.
To answer your last question, the primary interface is what gets added to the portal object in Appian Designer and the secondary interface(s) are all the interfaces nested within that primary interface. It behaves similarly to nesting interfaces when you're designing interfaces outside of Appian Portals as well, if you're familiar with that design pattern (i.e., calling an interface using rule! in the expression of another interface). Depending on your configuration, the end-user shouldn't be able to tell what the primary vs. secondary interface(s) are.
We are actually working on a couple upcoming features this year to make this design experience simpler. One is allowing portals pages so that you can add more than one interface directly to your portal object. Another is allowing rule inputs in your portal interfaces so that you don't have to use secondary interfaces to work around that.
Please let me know if you have any follow up questions or other feedback on Appian Portals!
I wanted to further clarify my answer. If you're concerned about inadvertently exposing something to the wrong users through using a showWhen expression, we'd recommend using record-level security (configured on the record type) instead or omitting that data from your portal altogether if it's not absolutely necessary to your use case.
© 2023 Appian. All rights reserved.