1. Introduction
A Microjourney in Pega represents a small, reusable, end‑to‑end business interaction designed to achieve a specific customer or business outcome.
Examples:
- Update Address
- Dispute Transaction
- Apply for Credit Card
Pega App Studio empowers business users and low‑code developers to design and deliver microjourneys quickly using visual, configuration‑driven tools—without deep technical coding.
This guide explains how to create microjourneys using low‑code capabilities in App Studio, covering concepts, steps, best practices, and real‑world usage.
2. What is a Microjourney?
A microjourney is:
✔ Single, focused customer interaction
✔ Outcome‑oriented and short‑lived
✔ Built on case types in Pega
✔ Reusable across channels (Web, Mobile, Chat, APIs)
Examples:
- Reset Password
- Change Contact Details
- Raise a Service Request
- Accept a Marketing Offer
zz3. Why Use App Studio for Microjourneys?
App Studio is designed for low‑code delivery, offering:
- Visual case lifecycle design
- Guided configuration wizards
- Prebuilt templates and best practices
- Minimal rule complexity
- Faster time‑to‑market
Key Benefits:
- Rapid development
- Business‑friendly UI
- Reduced dependency on technical teams
- Consistent user experience with Cosmos design system
4. Key Building Blocks of a Microjourney
- Case Type – Foundation of the microjourney
- Stages – High‑level phases (e.g., Collect Info → Review → Complete)
- Steps – Individual tasks inside a stage (Forms, Automation, Approvals)
- Personas – Defines who interacts (Customer, CSR, Manager)
- Data Objects – Internal or external data (Customer, Account, Address)
5. Step‑by‑Step: Creating a Microjourney in App Studio
Step 1: Open App Studio
- Log in to Pega
- Switch to App Studio
- Select your application
Step 2: Create a Case Type
- Navigate to Case types → Add case type
- Choose a template (Service, Request, Change, Issue)
- Provide:
- Case name (e.g., Update Address)
- Description
Step 3: Design the Case Lifecycle
- Use visual case designer:
- Define Stages (e.g., Collect Information → Validate Details → Complete)
- Add Steps (Forms, Automation, Notifications)
- Drag‑and‑drop configuration—no coding required
Step 4: Create User Forms (Views)
- Configure Collect Information step
- Add fields using drag‑and‑drop
- Set:
- Mandatory fields
- Validations
- Default values
- Uses Cosmos UI by default
Step 5: Configure Data Objects
- Navigate to Data objects
- Create or reuse existing objects
- Map fields to forms and automation
- Supports:
- Local data
- External data (via integration in Dev Studio if needed)
Step 6: Define Personas and Access
- Go to Users & Channels
- Assign personas to the case type
- Control who can:
- Create the case
- View or update it
Step 7: Add Automation (Optional)
- Low‑code automation options:
- Decision rules
- When conditions
- Service levels (SLA)
- Notifications (Email / Push)
Step 8: Configure Channels
- Expose microjourneys through:
- Web portal
- Mobile
- Chatbots
- APIs
- Enable channels in App Studio
Step 9: Test the Microjourney
- Use Preview mode
- Create a test case
- Validate:
- User flow
- Field validations
- Case resolution
6. Best Practices for Low‑Code Microjourneys
✔ Keep microjourneys short and focused
✔ Prefer one case type per microjourney
✔ Use meaningful stage and step names
✔ Reuse data objects and fields
✔ Avoid unnecessary custom code
✔ Validate early using Preview
7. When to Use Dev Studio?
Use Dev Studio when:
- Complex integrations are required
- Advanced decision logic is needed
- Custom UI or extensions are necessary
Best approach: Start in App Studio, extend in Dev Studio only if required.
8. Real‑World Example
Microjourney: Update Contact Details
- Case Type: Update Contact
- Stages: Enter Details → Verify → Complete
- Personas: Customer, CSR
- Outcome: Customer contact information updated successfully
- Delivered end‑to‑end with minimal technical effort
9. Conclusion
Low‑code microjourney creation in Pega App Studio empowers teams to rapidly deliver customer‑centric journeys with minimal complexity. By leveraging visual configuration, reusable components, and guided workflows, organizations can innovate faster while maintaining consistency and governance.
