Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. 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.
Has anyone else noticed this in checkbox component. The expression mode does not show error when i have both saveinto and saveInto (notice the difference "i" vs "I"). I am able to save, and the selected value is not getting saved as expected. The expression mode does not show the parameter as invalid for "saveinto" and also does not save the value.
I always thought the correct syntax is saveInto with capitalized "I"
Janaki Ram
Discussion posts and replies are publicly visible
Yes, ideally the expression editor should warn about duplicate use of the same parameter, but in this case Appian is not flagging it because saveInto is the documented parameter and saveinto is being tolerated due to case-insensitive parameter handling in the component parser.So your point is correct: from a developer experience perspective, Appian should highlight this as a duplicate parameter or invalid usage, but currently it appears to be a parser/editor limitation rather than expected validation behavior.