Hi,
We have 3 interfaces and 1 RecordType. 2 Interfaces call a RecordType and the latter calls a third interface.
Example:
InterfaceA => RecordType => InterfaceC
InterfaceB => RecordType => InterfaceC
My Question: How the InterfaceC may know which source Interface (A or B) have called the RecordType please?
The 2 interfaces A and B calls the RecordType with a RecordLink like :
link: a!recordLink( recordType: cons!TST_RECORD_TYPE, identifier: fv!row.id )
The RecordType calls the InterfaceC using the Summary action (Tab View).
Discussion posts and replies are publicly visible
Is your goal to display something different on interface C based on where you started? Can you describe more what you want to display on interface C?
Assuming that is what you're hoping to do, there really isn't an easy way that I know of to identify what link you came from. The only thing that might work is to just conditionally show interface C within interface A or B using a dynamic link instead of a record link. If you did this, you wouldn't navigate to the summary view itself, you would just temporarily hide all of the content in interface A using an if() or showWhen and then display interface C within your original interface.
Yes Peter, it is exactly that.
We need for a customer, to just hide a button in one case (but keep the button displayed in the other case).
I would have liked to avoid changing anything else for such a little need.
But thank you, I will try what you've suggested me.
Since 4 years, does new Appian versions came with a workaround for my need ?My need is still the same :
InterfaceA => Related Action (RecordType) => InterfaceC
InterfaceB => Related Action (RecordType) => InterfaceC
If InterfaceA is the initiator, I need to display Section in InterfaceC,otherwise, if InterfaceB is the initiator, I need to hide this Section.My Customer needs to keep the Modal Dialog functionnality.
There haven't been any changes with record actions, but the one change that may be beneficial is the introduction of URL Parameters for navigation in Portals and Sites. This should allow you to pass data through a URL parameter that on where you started.
The only caveat is I can't think of a way to do this through a dialog - record actions still require only the identifier, so there wouldn't be a great way to pass info to the record action.
Thank you Peter for this idea and your reply. Isn't it a little lack, the fact that we can't pass a context to the Related Action ?We could just imagine to be able to add a context like this?
a!recordActionItem( action: 'recordType!Usager.actions.displaySomeData', identifier: ri!v_usager.usager_id, context: 1 /* or 2 for the other Interface source */ ) /* with a rv!context available from the RecordType... */
Yeah it's definitely on our radar as a potential future enhancement, but unfortunately it doesn't exist yet for record actions.
That's a good news :-)