[Response Ops][UX] Rule creation flow updates

[mdefazio]

Rule creation flow updates

Current priorities for improving the current Alert framework rule creation flow

Rule Selection

A growing list of rule types is causing us to rethink how we present these to the user, and how to simplify the choice relevant to the context.

Goal: Improve our rule selection process to provide quicker access to editing the actual rule condition values.

• Minimize rule type options
• Improve rule type selection
• Provide more and 'smarter' defaults from contextual information

Actions

Our action framework has added many new features with more coming. How can we provide a more scalable solution to performing actions on alerts.

Goal: Provide a more scalable and customizable action UX framework to better accommodate the broader features and use cases.

• Improve action selection
• Improve experience for customizing and action payload definition
• Action and/or message templates

Rule flow optimizations

There is a growing list of requests and issues surrounding our create rule flow. Let's take a look at feedback and user research to determine the best course forward.

Goal: Improve our overall rule flow to include recent feedback and user research

• Review form order to better optimize to the mindset of the user
• Review current patterns to align ourselves with other complex forms
• End-of-flow improvements and jumping off points

---

Design assets:

Project Goals (Figma)
Milestone 1 Mockups (Figma)
Prototype: Management flow (Figma)

Design doc (Google doc)

---

Milestone 1

Preview Give feedback

1. Transition flyout to page layout
2. Update rule selection view
3. Reorder form with rule metadata at the end
4. Update action blocks with different views for settings and message

Milestone 2 (TBD)

Preview Give feedback

1. Action message templates
2. JSON preview of rule configuration

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[mdefazio]

@XavierM @Zacqary Are we still using this ticket? Or did you have a different one for the current v2 Rule creation work?

[Zacqary]

#175634 is where I'm tracking implementation work.

[joana-cps]

Closing this issue. MS1 is being developed and should be tracked here: #175634
We need to gather and list necessities for MS2. Future form creation improvements will be listed here: https://github.com/elastic/platform-ux-team/issues/325