'=' sign before interface components

RE: '=' sign before interface components

Jerry Sylveus — Fri, 09 Nov 2018 17:07:25 GMT

As everyone, mentioned there is not much of a difference between having the "=" or not having.

RE: '=' sign before interface components

Mike Schmitt — Fri, 09 Nov 2018 15:06:56 GMT

More primitive appian expressions (like if you put an expression in a node input for example) require the "=" prior to expression code so that Appian knows to interpret it as an expression and not plain text. The "=" sign used to be required at the start of all expressions, expression rules, etc, but in recent releases has been largely mitigated. The only place I can still think of that it makes any difference is, as I mentioned, node inputs (to see what I mean, type in a literal value without the "=" and then open the expression editor for the field, and you should notice that the expression editor has interpreted it as a string, complete with quotes.)
www.screencast.com/.../fjQlBzG0th2G

RE: '=' sign before interface components

rohinip91 — Fri, 09 Nov 2018 03:20:37 GMT

Thanks Alok

RE: '=' sign before interface components

rohinip91 — Fri, 09 Nov 2018 03:20:05 GMT

Thanks Ashvin..

RE: '=' sign before interface components

aloks0189 — Thu, 08 Nov 2018 22:42:08 GMT

Agreed with @Ashwin there isn't any advantage/disadvantage of having "=" before the expression as a prefix AFAIK.

In fact when we do not add "=" before an expression, appian adds this by default while saving/publishing the rules or the Process models.

Not sure whether this adds any advantage to Appian internally or not.

RE: '=' sign before interface components

Ashvin Kapur — Thu, 08 Nov 2018 21:33:02 GMT

Hi Rohini,

As far as I understand, there really isn't any reason for an "=" before the interface component. On an interface, you can optionally put an "=" sign before your code, but there is no advantage or disadvantage of doing so. I tend to omit the sign as the code is cleaner without it.

I hope this helps!
Ashvin