# Process Designer with Approvals: an Approval Request per Stage

> A process stage can ask Approval Workflow for a yes: the case raises the request as it arrives, waits for it, and moves on by itself once approved - installed by itself alongside Process Designer and Approval Workflow.

- **What it is:** A process stage can ask Approval Workflow for a yes: the case raises the request as it arrives, waits for it, and moves on by itself once approved - installed by itself alongside Process Designer and Approval Workflow.
- **For:** Productivity
- **Odoo versions:** 16.0, 17.0, 18.0, 19.0, 20.0 - Community and Enterprise
- **Runs on:** Odoo.sh or Odoo you host yourself - not Odoo Online, which accepts no third-party apps
- **Price:** 287 EUR, one-time, on the Odoo Apps Store
- **Technical name:** bambooforge_process_approvals
- **Not for:** Keep the amount up to date. It is read as the case enters the stage: a number filled in at this same stage is still empty then, and the request goes up for 0.; Pass the stage without the yes. A process owner's Complete Stage waits for it too.
- **Manual:** https://docs.bambooforge.dev/bambooforge_process_approvals/
- **Live demo:** https://demo20.bambooforge.dev/odoo/action-bambooforge_process.bf_process_action
- **Store page:** https://apps.odoo.com/apps/modules/20.0/bambooforge_process_approvals
- **Manual last updated:** 2026-11-11

---
# Process Designer with Approvals: an Approval Request per Stage

With Process Workflow Pro and Approval Workflow installed on Odoo 20, a stage of a process can ask
an approval type for a yes. The case raises the request as it enters the stage, cannot leave before
it is approved, and moves on by itself once it is. This small module installs by itself when both
apps are there.

This page is the complete manual of that bridge.

## Overview

**For whom.** A company that runs its processes in Process Workflow Pro and its approvals in
Approval Workflow, and wants a stage of a process (a purchase over an amount, a contract, a hire) to
be decided by an approval ladder: the type's steps, delegations, SLA and trail.

### What it does

- **A stage names an approval type.** On the stage: *Approval*, the type; *Amount From*, a number
  field of the case the request takes as its amount; *Move On When Approved*, on by default.
- **The request is raised as the case enters the stage**, in the name of the person who started the
  case, with the case's contact and the amount, and submitted to the type's ladder.
- **The case waits for it.** **Complete Stage** names the request and its state until it is
  approved.
- **It moves on by itself** once approved, when nothing else is missing (checklist, fields,
  sign-offs) and *Move On When Approved* is on.
- **An approval always stands.** When the case cannot move on by itself (the next stage goes to
  whoever completes this one, and nobody filled in *Hand To*), the approval is kept and the holder
  is told to complete the stage.
- **A refusal is posted on the case** for its holder and the process owners. **Raise the Approval
  Again** raises a new request after a refusal.
- **A case that leaves the stage withdraws its request.** Sent back, failed or cancelled, the
  request still waiting is withdrawn.
- **Installs by itself** when both apps are installed.

### What it does not do

- **Keep the amount up to date.** It is read as the case enters the stage: a number filled in at
  this same stage is still empty then, and the request goes up for 0.
- **Pass the stage without the yes.** A process owner's **Complete Stage** waits for it too.

### What it needs

- **Process Workflow Pro** (`bambooforge_process`) and **Approval Workflow**
  (`bambooforge_approvals`) on Odoo 20, Community or Enterprise.

## Concepts

**Approval stage.** A work stage that names an approval type: it raises a request and waits for it.

**Amount From.** The number field of the case the request reads its amount from.

**Move On When Approved.** Whether the approval completes the stage by itself.

## Install and first run

1. Install Process Workflow Pro and Approval Workflow: this module installs by itself.
   
   Expected: a stage's form has *Approval*, *Amount From* and *Move On When Approved* below
   *Sign-offs*.
2. Open a process, then the stage that should wait, and choose an approval type under *Approval*.
   Choose a number field of an earlier stage under *Amount From* when the type reads an amount.
   
   Expected: saved.
3. Start a case and complete the stages before it.
   
   Expected: on entering the stage the chatter says "Approval requested: ..." and the case shows "1
   approval request(s)".

### Uninstalling

Uninstalling leaves the requests raised so far in Approval Workflow and takes the three fields off
the stage: such stages then wait for nothing.

## Flows

One thing the bridge does.

### A stage that waits for a yes

1. The case enters the stage: the request is raised and submitted; the approvers get it under
   *Approvals > Waiting on Me*.
2. **Complete Stage** says "Still waiting for: Approval ..." until it is approved.
3. Approved: the case moves on by itself, or the holder completes the stage.
4. Refused: the holder and the owners read it in the chatter, then send the case back, fail it, or
   press **Raise the Approval Again**.

## How it works

### What happens when

- **Entering the stage.** The request is created with the type, the starter as requester, the case's
  contact and company, and the amount of *Amount From* as it stands; then submitted. When the type's
  ladder cannot be built (nobody to ask), the request stays a draft and the case's holder is told in
  the chatter.
- **Approved.** Only while the case is still in that stage; then the case moves on by itself if
  nothing else is missing.
- **Refused.** A message for the holder and the owners; the case stays.
- **Raise the Approval Again** works when the stage's latest request is refused or withdrawn.

### Who reads and writes what

- The holder of the case, a process owner or a Process Designer presses **Raise the Approval
  Again**.
- Who decides is the approval type's ladder; the person who started the case is never on it.

### How we make sure it works

Before every release, **5 automated checks** run against this app on Odoo 16, 17, 18, 19 and 20.
Among them:

- No auto move when the stage says no.
- A refusal stays on the case.
- The stage waits for the approval and moves on.
- Approval move on manual.
- Stale request send back.

The complete list is in the source you receive.

## For managers

This bridge has no analysis of its own: the requests show under *Approvals > Reporting*, and the
time a case waited in the stage under *Processes > Where Cases Wait*.

## Reference

The complete reference of this app is generated from the code on every release and published with
this manual at https://docs.bambooforge.dev/bambooforge_process_approvals/ under *Reference*.

## Troubleshooting and FAQ

****"Still waiting for: Approval <request> (Waiting)"****

The request is not approved yet. Open it from the case's *approval request(s)* link.

****"The approval request <request> is waiting to be completed and submitted: ..."****

The ladder could not be built: the type names nobody but the starter, or a step applies to no
amount. Correct the type, then submit the request from Approvals.

****"'<stage>' asks for no approval."****

**Raise the Approval Again** on a stage with no approval type.

****"<case> already has its request."****

The stage's latest request is a draft, waiting or approved: open it instead.

### Questions people ask

****Does the approver need to see the case?****

No. The request carries the case's name and subject; the approver decides on the request.

****Can the starter approve their own stage?****

No: the ladder is built without the requester, who is the starter.

### Support

Write to [support@bambooforge.dev](mailto:support@bambooforge.dev) with your Odoo series, the stage and what the screen said.

## Changelog

### 20.0.1.0.1

- Help texts on the two fields this bridge adds.
- This manual.


## Reference

Generated from the module's own code (version 20.0.1.0.1, series 20.0) on 2026-11-12; every menu, field, setting, scheduled action, group, rule, report and endpoint below is read from the files, not written by hand.

### Models

#### bf.process.stage (extends bambooforge\_process's bf.process.stage)

| Field | Technical name | Type | Help | Flags |
|---|---|---|---|---|
| Approval | `approval_type_id` | Many2one to bf.approval.type | Entering this stage raises an approval request of this type for the case; the case waits for it. |   |
| Amount From | `approval_amount_field_id` | Many2one to bf.process.field | A number field of the case the request takes as its amount. |   |
| Move On When Approved | `approval_auto_complete` | Boolean | Once approved, the case leaves the stage by itself if nothing else is missing. |   |

#### bf.approval.request (extends bambooforge\_approvals's bf.approval.request)

| Field | Technical name | Type | Help | Flags |
|---|---|---|---|---|
| Process Stage | `bf_process_stage_id` | Many2one to bf.process.stage | The process stage whose case raised this request. Approved while the case is still in that stage, it lets the case move on. | readonly |

#### bf.process.case (extends bambooforge\_process's bf.process.case)

| Field | Technical name | Type | Help | Flags |
|---|---|---|---|---|
| Approval Requests | `approval_request_ids` | One2many to bf.approval.request | Every approval request raised for this case, on any visit to any of its stages. | computed |
| Approval Request Count | `approval_request_count` | Integer |   | computed |
