Design Patterns Introduction

Design Patterns are a powerful tool to understand what types of use cases you can build in Moveworks.

👉 Get Design Pattern Certified in Moveworks Academy

What is a use case?

In Language User Interfaces (LUIs), a "use case" replaces ONE digital inquiry between an employee and an expert by interfacing with any digital systems the expert would have used.

For examples of use cases, see our use case library

What are Design Patterns?

Design Patterns are categories of use cases that follow roughly the same structure. For example, one design pattern might be an Lookup Single Record by ID (DP-6).

Some use cases that fit that design pattern might be:

• Purchase Order Lookup: "Show me PO123"
• Incident Lookup: "Any updates on INC456"
• Expense Report Lookup: "What is the status of my expense report #789"

These use cases all follow the same structure, they just have different information (intents, data, systems, etc.)

Supported Design Patterns

You can explore all our supported design patterns here.

• (Paths) DP-1: Knowledge Selection Path
• (Paths) DP-2: User-Based Action Path
• (Queries) DP-5: Lookup Single Personal Record
• (Queries) DP-6: Lookup Single Record by ID / Keyword
• (Queries) DP-7: Lookup Single Record by Name
• (Queries) DP-8: Filter Records by Name
• (Events) DP-9: Informational Updates
• (Events) DP-10: Actionable Updates
• (Queries) DP-15: Lookup Multiple Personal Records
• (Paths) DP-20: ID-Based Action Path
• (Multi-Workspace) DP-26: Event-Triggered Paths
• (Queries) DP-28: Filter Records by ID / Keyword
• (Paths) DP-44: Resource Selection Path

Future Design Patterns 🚧

These design patterns are under future considerations. Find out how you can build them today.

• (Paths) DP-23: Handoff Path with Actions
• (Paths) DP-24: Actions with Dates