Is there any way to expose Decision Table as an interface or in JSON format?

Is it about the table definition itself or about the result?

The Table definition, as if I am viewing the decision matrix in the interface.

Sorry, there is no way to do that AFAIK. May I ask why you would like to do that?

Some one from outside Appian needs the Decision Matrix data. So I thought of sending over the data by exposing it as an API.

Why would they need the whole matrix? If they intend to replicate it doesn't that raise the potential for the two to become out of sync?

If Appian should be the source of that decision rule then any consumers of that rule should be calling the rule in Appian to obtain a result. If multiple consumers need to access that matrix and Appian should not be the source then it should probably be hosted in some sort of decision rules engine and Appian should be calling that when necessary.

If it's just a one-off sharing of the current values of the decision matrix then can't you share it as screenshots?

Alternatively...bring that person into Appian so they can access the Decision Matrix natively themselves. You can lock the security down so they can view but not change if that's a concern.

Stewart Burchell I'm tying to give the decision table access to the basic user. I gave editor rights. But when use clicks on the link then it giving him the 403 forbidden error message. Could you please help me how basic user can access the decision table?

I believe you'll need to provide the Basic User with 'Designer' rights (add them to the 'Designers' group). But you would need to dial down their access to 'Viewer' access so as to prevent them from editing the object.

I believe you'll need to provide the Basic User with 'Designer' rights (add them to the 'Designers' group). But you would need to dial down their access to 'Viewer' access so as to prevent them from editing the object.