Idea ID: 1659987

Condition Editor in SMAX business rules

Status : Declined
over 2 years ago

We need to provide an easy, friendly way to add condition(s) in SMAX.  Would be nice to have it similar to what SM has with its Condition Editor.


  • Thank you for your idea. At this time, your idea hasn’t received enough community support and doesn’t align with our priorities so we are closing this idea. But we may review this again in the future. Thank you for your support and continue posting & voting on ideas to help make our products better.
  • After configuring an Execute REST business rule, there definitely need to be practical adjustments made to make this truly useful.

    1) The space provided in the expression editor is not at all adequate for composing the bodies of REST calls. These bodies of JSON could easily be 100 lines long, depending on the system you are integrating with.

    2) Composing JSON with a mixture of Expression Language and Static strings is very confusing and not easily done. Being able to use expression language directly within strings would make it infinitely more useful and natural to the end user. For example, the text should be something like this:

         "attribute1" : ${entity.StaffMember_c.Name}

  • Hi Tonya - this applies to all conditions (simple or complex) that you need to build out using SMAX (the "if...then" condition).  It can be a simple "if/then" expression such as only make the justification field in a change record mandatory if the risk is high.  It can also be a complicated condition such as make the justification field in a change record mandatory if the risk is high and if the location is AMS, only need if the city is Las Vegas or New Year City or the impact is high or critical, but only if the location is not AMS. 

  • Thanks Kasey for providing destails of the SM solution, that's helpful. Also, while this is a general purpose editor, are they specific use cases/requirements you can provide as well? (i.e., what rules you were trying to write with SMAX, that made you think about the SM solution) The usefulness of a general editor is intuitive I think, but perhaps some of the cases are common enough to be OOTB??

    The idea is open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team.