General context: I have worked as a contractor for Adobe Workfront where, alongside my colleagues, I developed multiple client-oriented solutions. This is one of them.
What we were solving: An admin user should be able to view all custom forms they (or their peers) create, in a list that can be searched or filtered and should be able to assign/re-assign these forms. A user should also be able to set a custom form as default for an object type and apply conditions. These can be either written as code, or be generated with AI.
What we were solving: An admin user should be able to view all custom forms they (or their peers) create, in a list that can be searched or filtered and should be able to assign/re-assign these forms. A user should also be able to set a custom form as default for an object type and apply conditions. These can be either written as code, or be generated with AI.
In the image above we see a list (table) with custom forms. We were able to create this type of table after a team effort, involving people from 3 contintents, including staff level designers, who decide the design policy for the company. Why so much effort for just a table? Because this is not a one-of item, but itwas created because of this and implemented across multiple of Adobe's products.
I have designed components for this and have written the entire documentation for it. After this first screen, the rest of the designs are entirely made by me, using Adobe's Spectrum design system.
I have designed components for this and have written the entire documentation for it. After this first screen, the rest of the designs are entirely made by me, using Adobe's Spectrum design system.
Below you will be able to see a simple dialog, from the platform to the user, as well a more complex selection interaction.
