<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>We are seeing a common usability issue across our applications with validation m</title><link>https://community.appian.com/discussions/f/user-interface/5594/we-are-seeing-a-common-usability-issue-across-our-applications-with-validation-m</link><description>We are seeing a common usability issue across our applications with validation messages. If the user is presented with a form which includes field level validation messages, the validation error message upon submitting the form is not noticeable to the</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: We are seeing a common usability issue across our applications with validation m</title><link>https://community.appian.com/thread/21299?ContentTypeID=1</link><pubDate>Wed, 12 Aug 2015 09:34:14 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:8715cf04-4c4f-4806-b0c6-031d1fd064d1</guid><dc:creator>Eduardo Fuentes</dc:creator><description>Another option is, if you&amp;#39;re using a!formLayout(), you can make use of its &amp;quot;Validation&amp;quot; property. With this you basically move the validations out of the individual components and move them to the general one in formLayout(). See &lt;a href="https://forum.appian.com/suite/help/7.10/SAIL_Recipes.html#Showing_Validation_Errors_that_Arent_Specific_to_One_Component"&gt;forum.appian.com/.../SAIL_Recipes.html&lt;/a&gt; for an example.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: We are seeing a common usability issue across our applications with validation m</title><link>https://community.appian.com/thread/21173?ContentTypeID=1</link><pubDate>Mon, 10 Aug 2015 17:30:19 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ca1cdae4-5bab-4e54-829b-0f151a215bd3</guid><dc:creator>PhilB</dc:creator><description>One option is to place an empty, non-labelled section at the bottom of the form which includes the same validation as the fields, so that it displays the error message at the bottom of the form as well as on the fields themselves. You&amp;#39;d use the validations parameter on the a!section component as documented here: &lt;a href="https://forum.appian.com/suite/help/7.10/SAIL_Components.html#Section"&gt;forum.appian.com/.../SAIL_Components.html&lt;/a&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: We are seeing a common usability issue across our applications with validation m</title><link>https://community.appian.com/thread/21172?ContentTypeID=1</link><pubDate>Mon, 10 Aug 2015 14:33:41 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2479717d-f6a8-4c12-8672-ac3399d81416</guid><dc:creator>moritzw</dc:creator><description>Yes, we have the same issue. Especially on larger forms. I guess the best way to avoid this is to keep the forms as small as possible. If more field are needed a wizard like editor could help split it up in multiple smaller forms.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: We are seeing a common usability issue across our applications with validation m</title><link>https://community.appian.com/thread/21170?ContentTypeID=1</link><pubDate>Mon, 10 Aug 2015 13:44:38 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c2c52e9f-854d-4914-835f-9f43c96f1b47</guid><dc:creator>jarrods229</dc:creator><description>...hallenge?&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>