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.

Issue: a!isNullOrEmpty() not working with blank a!map()

While trying to check an empty map, a!isNullOrEmpty and a!isNotNullOrEmpty are not working, rather giving opposite result. 

The result of 

a!isNullOrEmpty(a!map())

should be true but the function is returning false. Not sure if this is a bug but something that might need the engineering team's attention. 

  Discussion posts and replies are publicly visible

Parents
  • Hmm, it does seem odd - that being said, I'm pretty sure behind the scenes this function is just doing a length() check on the value. If I do length(a!map()) it returns 1, so that's probably why this is returning false.

    If you'd like, you could probably submit a support case and have the team investigate it. My hunch though is that it is behaving as expected given the result using the length function.

Reply
  • Hmm, it does seem odd - that being said, I'm pretty sure behind the scenes this function is just doing a length() check on the value. If I do length(a!map()) it returns 1, so that's probably why this is returning false.

    If you'd like, you could probably submit a support case and have the team investigate it. My hunch though is that it is behaving as expected given the result using the length function.

Children
No Data