Team, Can we have a decision tree/ decision table like rule which is

Team,

Can we have a decision tree/ decision table like rule which is exposed to the user to modify the table values when they need, say for example:

Discount Category for Season           Summer          Winter          Spring
Category A           10% 12%           15%
Category B           12%          15%          17%
Category C           15%          20%          25%

How we can achieve the same? Do we have any APIs to support this or smart service?

Please provide inputs on the same...

OriginalPostID-103985

OriginalPostID-103985

  Discussion posts and replies are publicly visible

Parents
  • Hello Manikandang,

    Well, as announced there is the Decision Designer released in the version 17.2, Take a look to the link.
    * docs.appian.com/.../Appian_Decisions.html

    I haven't found the way to get modified by the End User out side the designer, even Appian states the following:
    "Decisions can be exposed to certain users in a limited editing mode that allows these users to update the business rules of the Decision but not change the structure of the Decision (to limit the affects of all the other application objects using the Decision). This allows designers to set up the structure of a Decision and then share with business experts to fill out the actual business logic."

    At the end you can call the decisions/rule just like this "rule!AT_Decision(name:1)" wherever you need to, so, this is mostly what you want to

    Best Regards
    Jose Perez
Reply
  • Hello Manikandang,

    Well, as announced there is the Decision Designer released in the version 17.2, Take a look to the link.
    * docs.appian.com/.../Appian_Decisions.html

    I haven't found the way to get modified by the End User out side the designer, even Appian states the following:
    "Decisions can be exposed to certain users in a limited editing mode that allows these users to update the business rules of the Decision but not change the structure of the Decision (to limit the affects of all the other application objects using the Decision). This allows designers to set up the structure of a Decision and then share with business experts to fill out the actual business logic."

    At the end you can call the decisions/rule just like this "rule!AT_Decision(name:1)" wherever you need to, so, this is mostly what you want to

    Best Regards
    Jose Perez
Children
No Data