Discussion posts and replies are publicly visible
The workaround I did was to create a rule with if-else logic. Are we going to extend functionality to support the decision table in future releases?
Decision objects are only partially supported in Portals by connecting to a web API object using an integration object. Direct support for decision objects in Portals may be added in the future, but we do not have a specific timeline at this time.
Instead of multiple If-Else you can use Match function. It will increase the readability of the code and alse it is performance efficient as well.
a!match() Function - Appian 22.1
Let's take a moment and understand what actually is supported in the portals and what is not.
If I explain to you in simple language, when you publish a portal, it takes all of your interface code and pushes it to another server. Now when you want to use objects inside the interface that would require Appian's engines to evaluate, then it will not work unless you bring Appian connectivity in picture using a service account. It seems like you will have to connect Appian to Appian, but in reality, you will be connecting that public site (portal) to Appian.
Decisions are very easily replaceable in Appian using if(), index(), choose() or match() or a combination of these. You can write your logic in the interface itself.
My use case is different it requires a number range. thanks
Then you can use if else conditions.
a!match() can handle number ranges as well - that's what the "whenTrue" parameter is for.
© 2022 Appian. All rights reserved.