HOW TO INDICATE THAT ONCE SAVED, AN ENTRY CAN NOT BE CHANGED
There are some fields with in App Orchestration that can not be changed once saved. For example; Domains. Once a Domain is created and in use, changing it is not an option because it will throw off everything that uses that domain.
DISPLAYING ADDITIONAL DETAILS
There were often times where it was imperative to show extensive amounts of detail for a property. To reduce visual overload, I implemented a interaction pattern called progressive disclosure.
Progressive disclosure is an interaction design technique that sequences information and actions across several screens in order to reduce feelings of overwhelm for the user (Spillers 2004).
Nielsen (2006) defines progressive disclosure as a technique that defers advanced or rarely used features to a secondary screen, making applications easier to learn and less error-prone
This screen shows how the page looks in it’s default state without the additional content.
This screen shows how the page looks once the user has clicked view more detail.
Wizards are the most commonly used pattern throughout App Orchestration. Every new property requires the user run through the wizard to set it up. During this project I was working with a visual designer. I needed her to provide me the specs for the design so I could give them to the development team. I annotated the wireframes so she would know exactly what was needed.