We've been trying to send a customer id from one interface to another but haven't figured out a way to do it without using process model. Is there any way to do it without using process model?
Discussion posts and replies are publicly visible
The idea of Appian is to implement business processes using process models. This is not just a platform to somehow connect user interfaces.
What exactly do you want to achieve? A wizard style UI? What is the goal of "sending" data to the other UI?
As stefan already mentioned, this request doesn't really make sense in context of what Appian is / can do.
shreyasb0001 said:send a customer id from one interface to another
Can you provide a bit more description as to what you want to see, perhaps from a user experience perspective?
What you can actually do is, to save that customer id in a table from the first interface and load it from the other interface.
Sending something from one interface to another it doesn't make sense in Appian as Stefan and Mike already mentioned.
For a little bit more detail:
Interface1 saves customerID to table,
Interface 2 refreshes from DB every 30 seconds, or when person using interface furiously mashes "refresh button"
After refresh on Interface 2, it grabs customerID that was saved some time less than 30 seconds ago.
This is actually a classic anti-pattern of using a relational database as a messaging system when there's far better approaches available to you. It's just that there aren't far better approaches with Appian. You can't get data out of a form and into the PM without submitting it, and you can't get data from a PM into a form except for when the form loads.
If Appian did change this, however, we could have real-time collaboration between two people on two machines doing the same task and seeing each other's updates live in the same form. Think excel sheet on shared drive with multiple people completing it at the same time.