Skip to main content
johnk896091
johnk896091
New Participant
October 14, 2026
Question

How do I build a content request and approval workflow in Appian?

Hi all,

I’m building an internal application in Appian, which we’re calling “Wikipedia Page Maker.” It manages requests for drafting articles and getting them reviewed and approved before delivery. I’m fairly new to designing multi-stage approval flows and would appreciate guidance on the right architecture.

What the process needs to do:

  1. A requester submits a content request through a form (subject, source links, deadline, priority).
  2. The request is stored and assigned to a writer.
  3. The writer submits a draft, which goes to a reviewer.
  4. The reviewer can approve it or send it back with comments for revision, and this can repeat.
  5. After approval, the request moves to final sign-off and is marked complete.
  6. If a review sits for more than 14 days, it should escalate or notify a manager.

What I’m trying to figure out:

  1. Should the request be modelled as a record type with a process model driving the stages, or should the status live only in process variables?
  2. What is the cleanest way to handle the revision loop (reviewer rejects, writer revises, reviewer reviews again) without the process model becoming unmanageable?
  3. How should I assign tasks to different reviewers based on a field value, for example the content category? Is it better to use groups, a rule, or a lookup table?
  4. What’s the recommended way to attach and version draft documents at each stage?
  5. Is a record action or a Start Form better for submitting new requests?
  6. For escalations, are timers on the user input task the standard approach, or is there a better pattern?

What I’ve tried so far: A single process model with XOR gateways for the approve or reject outcome

Any best-practice advice or links to relevant docs or design patterns would be great. Thanks!

3 replies

mathieud0001
mathieud0001
Genius
October 14, 2026
  1. If you’re building in Appian, I would typically go with Process + Record Type. Otherwise it’s just a regular CRUD app.
  2. Hard to help without designing it per say. There are plenty of examples of this type of process in the docs and academy.
  3. It depends on how granular you need be. As a general rule, choose the simplest option that satisfies the requirement. You can always change it later.
  4. I would roll my own doc versioning implementation. Appian does have versioning built in their doc manager but it’s not incredible. I would also question why this would be required for an MVP.
  5. Record Actions usually require a Start Form.
  6. That is the usual approach.

 

stefanhelzle0001
stefanhelzle0001
Brainy
October 14, 2026

Link to https://www.wikiwriters.co.uk/??? Is this SPAM?

    nareshs945
    Inspiring
    October 14, 2026

    You can implement this requirement using a combination of Record Types, Process Models, and Appian Interfaces. I would recommend starting by identifying the different user roles, workflow stages, and approval requirements.

    • Record Types: Manage content requests, statuses, assignments, and approval history.
    • Process Models: Handle request submission, task assignments, reviews, approvals, and revision cycles.
    • Interfaces: Provide users with forms to submit requests, review content, provide feedback, and track progress.
    • Dynamic Assignment: Use business rules to assign tasks to the appropriate users or groups.
    • Notifications and Escalations: Configure reminders and escalations for pending approvals.

    I would also suggest building a simple end-to-end workflow first and gradually incorporating additional functionality, such as document versioning, audit history, and reporting. This approach should provide a scalable and maintainable solution using Appian's standard capabilities.

    Terms & ConditionsAccessibility statement