I'd like to document the various form fields for a page in an application onto a Confluence page — things like the field name, its ID attribute, validation rules, etc. This is easy enough to do in a simple table, but I'd also like to document more complicated things, like the conditions under when certain fields are hidden/shown.
For example, perhaps a Zip Code field only appears or is only required if the Country field further up the page has the value "USA" selected.
What is the best way for modeling UI/UX requirements like this in Confluence?
Anyone have any insight? I'm sure I'm far from the first person looking to document form validation rules and user flow in Confluence.
I realize this thread is old, but I have some questions about this too. I do have a few ideas but I'm sure you've found something Jacob.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.