Car Insurance App - Part 3

Exploring user interfaces

      In Part 2 we saw that each persona was able to do their job using the platform back-end.
      In order to allow your users to access the App functionalities, in the back-end we use the Application menu and modules.
      The application menu usually is your Application name. In our example the users can use the filter navigator typing Car Insurance to access the application modules.
      Each persona has access to different modules and this is what differentiates the personas.

Persona: Agent

      When the Agent is logged in, he can see in the back-end:

Menu Agent

      The module "Proposals - Agent", only visible to Agents, is a list of records and contains records with Status "Under construction" and "Send to analysis" false.

Persona: Employee

      When an Employee is logged in, the available modules are different as we can see:

Menu Employee

      The module "Proposals - Employee", only visible to Employees, is a list of records and contains records with Status "Under construction" and "Send to analysis" true.
      This filter capability is easily configured when creating the modules and does not require the use of ACLs [1].
      We talked about it in this article but now we have a better scenario to explain it.

Persona: Administrator

      Our third persona - the Administrator - do not manage proposals so the only feature he has is the Vehicle table maintenance:

Menu Admin

The Service Portal

      Another common User Interface is the Service Portal. Let's explore some interface examples.
      A Service Portal is comprised of different parts organized in a defined hierarchy.
      1) The first degree are the pages.
      2) Then each page has containers.
      3) And each container has rows and columns.
      4) Inside a column we have the widgets.

      Inside the Page below, we can see a widget that shows records from our Proposal table.

Service Portal

      Impersonating the Car Insurange Agent

      We can simulate an Agent using the Service Portal to create a new proposal.
      An Agent would see an interface like this:

UX Agent

      Impersonating the Car Insurance Employee

      Similar to what happens in the back-end, the Agent can work on a proposal while the "Send to analysis" is not checked. Once this field is checked and the record Updated, it will be available to the Employee.
      Using the Service Portal, a logged in Employee can Approve or Reject a proposal and the interface can be similiar to this:

UX Employee

      Note that the security rules are valid here so the Employee can't edit information provided by the Agent.

      Thanks for reading.

[1] Access Control List Rules - ServiceNow
Service Portal - ServiceNow