While Initial Pre UAT and Validation of New UCI Transition, We received a lot of issues raised by System users that Layout of form is irregular and they are having a hard time coping with it,
We knew that it's because of the responsiveness of the form and that is a good thing it's just they need to understand it better and we have to test it better
Then another was Composite Field which is split into UCI which we for sure understand to make UI more responsive, it was required but convincing system user its been tricky
So receiving from layout issue by system user will be common while transitioning to New UCI especially if we have lots of information on our old legacy form to make it more interactive for the system users
- Above image, we can see if we open New UCI of our dev in Ipad both have different section view on the screen (note these are not divided into tabs, we are taking example of the section itself, if we see new UCI of above record it will show us 2 columns instead)
- So the Unified Client interface uses responsive web design to provide an optimal viewing and interaction experience for any screen size, device, or orientation.
- But it better to test it from development and validation perspective before handing it over for UAT and we can do the Responsive testing in our web browser itself, chrome, firefox, etc
- GO to the page which needs to be validated -> Press F12 to enter the dev tool and once inside devtool , you can see device button on very left top corner (chrome)
- There we can choose between different Devices or resolution to see how the page is rendered
Then we have 1 more thing which we already informed system user about "composite field", i.e address field splits up
We fully understand why removing composite is done and frankly don’t like composite field much,
so we informed system user that this is going to be permanent for now and the reason,that to make our new UCI more responsive this might be essential step like if we want to access the environment from a smaller screen, pop from the composite field would not fit in a responsive manner and it was this easy to explain to them until we ended up creating a field to populate split value into a read-only field
