Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!

The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
  • State Not Answered
  • Replies 11 replies
  • Subscribers 8 subscribers
  • Views 19019 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Best Practices

expression rule vs decision

krisk

Hi,

     I know decision designer is new feature.

     Would like to check what are best use cases for writing expression rules  and  best use cases write decision rules? 

     Where are these decision rules are going to stored. Do we have access these tables         

      Can we group decision rules under one rule set and make use of them in another rule?  Can we use this decision designer as a typical rule engine(IBM ODM,DROOLS,PEGA rule engine) functionality?

Thanks.

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer
    Hi krisk,



    One of the use cases where we implemented a Decision table was to set the "required", "disabled" and few other properties of UI form components.

    The UI form consisted of several fields that required user indexing. Based on user selection of a couple of fields some fields had to be mandatory and some other fields had to be disabled and so on...

    A decision table was created that takes two fields as input and then returns multiple boolean values, each of which indicate a certain property (required/disabled/etc.,) for a SAIL component.

    The Business Analysts in the team were given access to this decision table to configure the scenarios as per the business requirement.

    Since using a decision table is straight forward and real-time, it is very convenient to maintain business logic and adapt to frequent requirement changes.



    Regards,

    Sunil Zacharia
Reply
  • 0
    Certified Lead Developer
    Hi krisk,



    One of the use cases where we implemented a Decision table was to set the "required", "disabled" and few other properties of UI form components.

    The UI form consisted of several fields that required user indexing. Based on user selection of a couple of fields some fields had to be mandatory and some other fields had to be disabled and so on...

    A decision table was created that takes two fields as input and then returns multiple boolean values, each of which indicate a certain property (required/disabled/etc.,) for a SAIL component.

    The Business Analysts in the team were given access to this decision table to configure the scenarios as per the business requirement.

    Since using a decision table is straight forward and real-time, it is very convenient to maintain business logic and adapt to frequent requirement changes.



    Regards,

    Sunil Zacharia
Children
No Data
© 2026 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.