Question on if() function's documented functionality

It appears that the if() function has some undocumented functionality: it can handle if-elseif-else structures with only one call to if() instead of several nested calls. I found this use case while looking through the objects in a Quick App -- have a look in the interface rule GetIconForPriority.

Can any Appian employee confirm that this functionality was intended? Given that it's used in Quick Apps, I'm not exactly afraid that it will disappear, but I still hesitate to make use of undocumented functionality.

OriginalPostID-212631

OriginalPostID-212631

  Discussion posts and replies are publicly visible

Parents
  • Phil,
    I'd be interested to hear about the best practices violations you've mentioned finding. The Send Task model shares the same layout as the other process models, so I'm not sure what you're referring to in that case.

    Some of the objects do not have descriptions because they would have been redundant with the object name. There are a few legitimately missing descriptions, which we're in the process of adding, but not in the process models.
Reply
  • Phil,
    I'd be interested to hear about the best practices violations you've mentioned finding. The Send Task model shares the same layout as the other process models, so I'm not sure what you're referring to in that case.

    Some of the objects do not have descriptions because they would have been redundant with the object name. There are a few legitimately missing descriptions, which we're in the process of adding, but not in the process models.
Children
No Data