UX feedback -- Policies

What We Did

UX evaluated the Policies feature demonstrated at https://drive.google.com/open?id=1M9Vrwp8b_v8oHpB8ykd_Fot4XrwQ6Ddi and created a set of feedback, organized into the following categories:

  1. Development effort required
  2. UX team to investigate further
  3. Patternfly issues identified

What is/isn’t in the scope of our feature feedback

Our feedback includes comments on:

  1. Viewing policies
  2. Creating policies
  3. Modifying policies

This feedback does not include recommendations about the Expression editor/creator tool.

Findings & Recommendations

Issue 1: Cannot identify which fields are required and which are optional on the Create New Policy form.



Recommendation: Follow PatternFly recommendation for required field labeling on forms. Disable the “Add” button to prevent user from submitting the form without all required fields filled.


Issue 2: “Description” is the label for the object (policy) identifier instead of the typical label, “Name.” A Description is typically tend to be optional and lengthy explanations of what a policy is for and is not a brief way to identify the object.


Recommendation: Rename “Description” to “Name” and show syntax hints.


Issue 3: The system allows a user to create an empty policy that has no conditions, events, or actions. This does not satisfy a use case, especially since there is a control that allows a user to deactivate a policy from creation.


Recommendation: If there is no use case for an empty (and potentially inactive) policy object, do not allow user to create an empty policy (disable “Add” button on the Adding a new Control Policy).


Issue 4: We should not be abbreviating “Auth” because someone might interpret it differently (Authorization vs. Authentication).


Recommendation: spell out Authentication


Issue 5: There are no indicators to notify which fields are required vs. optional on the Add a New Condition form.



Recommendation: Follow PatternFly required field label guidelines (add link) to the “Description” field and the Expression section title. Reword ().


Issue 6: A pencil icon is not necessarily known as an “Edit” button.


Recommendation: Instead of using an pencil icon as the “Edit” button, create a button labeled “Edit."


Issue 7: The expression editor’s choices are filtered to show only items specific to the policy this new condition will be assigned to or the condition type the user is creating it under. However, there is no reference on the form to indicate the policy or condition type the condition is being created in conjunction with.


Recommendation: Either on the form’s title or as a field, indicate what Policy or Condition Type this new condition is being created for.


Issue 8: The user is able to choose “Edit a Policy’s Condition” even though there are no conditions in the policy at all.


Recommendation: Don’t allow the user to launch/navigate to edit a policy’s condition when we know there are no conditions to edit.


Issue 9: Inline notifications (for warnings, errors) appear instead of disabling action buttons until the user makes a choice.


Recommendation: If there are no selections made, do not enable the buttons to allow user to click on. If nothing is selected on the “Available Actions” panel, all of the buttons should be disabled. If nothing is selected on the “Selected Actions” panel, all of the buttons should be disabled.


Issue 10 : Navigating to policies is confusing because there is no terminology on the main navigation bar that matches the term “Policy.”


Recommendation: UX to investigate possible terminology change.


Issue 11 : If not familiar with how policies are created, it’s easy to think that events, conditions, and actions are peer objects by looking at the explorer menu, when in fact, they are not.


Recommendation: UX to investigate further possible alternative navigational flows to help reinforce the relational hierarchy between all these objects.


Issue 12: There are no instructions for a novice user defining a scope using the expression editor.


Recommendation: UX to investigate alternative ways to select “scope” and/or redesign of expression editor.


Issue 13: After creating a policy, there is no guidance on how to populate it, including adding conditions, events, or actions to this particular policy.


Recommendation: UX to investigate using the PatternFly wizard pattern to build a create a policy wizard flow that allows a user to setup a policy.


Issue 14: Inline notifications appear whenever there are no objects in a Policy section.


Recommendation: UX to investigate on how to use the PatternFly Empty State pattern to resolve this issue.


Issue 15: There is no easy way to find and select an event for a policy.


Recommendation: UX to investigate further.


Issue 16: If the user is following the workflow Policy, Event, Condition, Action (PECA) they create a Policy, assign an Event, add a Condition and finally add an Action. But if the user was following that order, she adds an action on Event details to do so (not intuitive?).

Recommendation: UX to investigate on a flow mechanism that will guide the user in creating a policy, if prioritized.