# WorkFlow Request

<p class="doc-lead">A WorkFlow Request tracks a company process after a document exists — for example turning a Sale Order into purchase, stock-in, delivery, and invoicing. It is not Multi Stage Approval of that document. Completing the workflow does not approve or post the origin transaction.</p>

<div class="doc-toc">
<p class="doc-toc-title">On this page</p>
<div class="doc-toc-section">
<span class="doc-toc-group-title">Getting started</span>
<div class="doc-toc-links">
<a href="#/hr/workflow-request?id=what-it-is">What it is</a>
<a href="#/hr/workflow-request?id=overview">Overview &amp; List View</a>
<a href="#/hr/workflow-request?id=create-from-document">Create from a document</a>
<a href="#/hr/workflow-request?id=quick-start">Quick Start</a>
</div>
</div>
<div class="doc-toc-section">
<span class="doc-toc-group-title">Form reference</span>
<div class="doc-toc-links">
<a href="#/hr/workflow-request?id=header-fields">Header Fields</a>
<a href="#/hr/workflow-request?id=stage-panel">Stage panel</a>
<a href="#/hr/workflow-request?id=stage-actions">Stage actions</a>
</div>
</div>
<div class="doc-toc-section">
<span class="doc-toc-group-title">Examples</span>
<div class="doc-toc-links">
<a href="#/hr/workflow-request?id=use-case-sale-delivery">Sale Order — Sale Delivery</a>
<a href="#/hr/workflow-request?id=use-case-po-process">Purchase process with Create PO</a>
</div>
</div>
<div class="doc-toc-section">
<span class="doc-toc-group-title">More</span>
<div class="doc-toc-links">
<a href="#/hr/workflow-request?id=actions-status">Actions &amp; Status</a>
<a href="#/hr/workflow-request?id=view-tabs">View Tabs</a>
<a href="#/hr/workflow-request?id=best-practices">Best Practices</a>
<a href="#/hr/workflow-request?id=faq">FAQ</a>
<a href="#/hr/workflow-request?id=related">Related</a>
</div>
</div>
</div>

<hr class="doc-section-divider">

<h2 id="what-it-is">What it is</h2>

Use a WorkFlow Request when several people must complete a sequence of <b>work steps</b> around a document. Typical steps include a supplier visit, collecting quotes, bringing stock in, delivering, and raising a sale invoice.

| | <b>WorkFlow Request</b> | <b>Multi Stage Approval</b> |
|--|-------------------------|------------------------------|
| <b>Question it answers</b> | What must the team do next on this order or job? | May this invoice / voucher be posted? |
| <b>Started from</b> | Document more menu (<b>WorkFlow Request</b>), or HRMS → Workflow Request | Attaches on save when a Settings template matches |
| <b>When the last stage is done</b> | The request is Approved. The origin Sale Order (or other document) stays as it was. | The document itself becomes Approved and posts |
| <b>Setup</b> | <a href="#/hr/workflow-approval-stage">WorkFlow Approval Stage</a> and <a href="#/hr/workflow-approval-template">Template</a> | <a href="#/settings/approval-stage">Settings → Approval Stage</a> and <a href="#/settings/approval-template">Template</a> |
| <b>Docs</b> | This page | <a href="#/features/multiapproval">Multi Approval</a> |

Two kinds of stage:

<ul>
<li><b>Process-only</b> — no system button. The assigned person adds notes or attachments (site-visit photos, a supplier quote) and clicks <b>Approve</b> to mark the step done.</li>
<li><b>System action</b> — the stage has an Actions row (for example Action Type = Delivery Note, Button Label = Create Delivery Note). After the stage is sent, that button opens the New form, pre-linked to this request. Created documents appear under <b>Linked Documents</b>.</li>
</ul>

You can mix both kinds on one template.

<hr class="doc-section-divider">

<h2 id="overview">Overview &amp; List View</h2>

The WorkFlow Request list shows every process request with its current stage and status.

<img src="hr/images/workflow.webp" alt="WorkFlow Request list" loading="lazy">

<b>ERP path:</b> HRMS → Workflow &amp; Approvals → Workflow Request

<b>Quick filters</b>

| **Filter** | **Description** |
|------------|-----------------|
| Default | All requests except Cancelled. |
| Approved | All stages complete. |
| Draft | Not yet sent. |
| Multi Level Approval | A stage is in progress. |
| Cancelled | Cancelled requests only. |

<b>Advanced filters</b>

Title, Request Owner, Approval Template, Stage, Status, Created date.

<b>List columns</b>

| **Column** | **Description** |
|------------|-----------------|
| ID | Record ID. |
| Number # | Reference number. |
| Title | Process name (for example Sale Delivery — SO-1042). |
| Date | Request date and time. |
| Due date | Expected completion deadline. |
| Request Owner | Employee who owns the request. |
| Approval Template | Process template applied. |
| Created date | System creation date. |
| Stage | Current stage. |
| Status | Current status. |

<b>List row actions</b>

| **Action** | **Available when status is** |
|------------|------------------------------|
| Edit | Draft, For Revisal |
| Delete | Draft, For Revisal |
| View | All statuses |

<hr class="doc-section-divider">

<h2 id="create-from-document">Create from a document</h2>

The usual start is the origin transaction, not the HRMS menu.

<ol>
<li>Open the document (for example an approved <a href="#/sales/sale-order">Sale Order</a>).</li>
<li>Click the more menu (⋮) → <b>WorkFlow Request</b>.</li>
<li>The New WorkFlow Request form opens with that document as <b>Origin Transaction</b>.</li>
<li>Enter <b>Title</b>, choose the <b>Approval Template</b> for this process (for example Sale Delivery), add a description, and save.</li>
</ol>

<b>WorkFlow Request</b> appears on the more menu of these documents when status is typically Approved or Closed (Sale Order also allows Closed): Opportunity, Sale Order, Sale Invoice, Sale Quotation, Pro Forma Invoice, Commercial Invoice, Credit Note, Sale Return Order, Purchase Order, Purchase Invoice, Purchase Quotation, Purchase Expense, Debit Note, Purchase Return Order, Work Order, Delivery Note, Receipt Note, Expense, Payment Voucher, Receipt Voucher, Expense Claim.

On an <a href="#/crm/opportunity">Opportunity</a>, the action is available when the opportunity is <b>Approved</b> or <b>Closed</b>, if you can create a workflow request. The opportunity stays as it is. Its view shows <b>WorkFlow Request</b>, which opens the request.

You can also create a request with no origin document from <b>HRMS → Workflow &amp; Approvals → Workflow Request → New</b>.

<hr class="doc-section-divider">

<h2 id="quick-start">Quick Start</h2>

<h3>1. Set up stages and a template</h3>
Create process steps in <a href="#/hr/workflow-approval-stage">WorkFlow Approval Stage</a>. Add system Actions only on steps that should create a document. Combine the stages in a <a href="#/hr/workflow-approval-template">WorkFlow Approval Template</a>.

<h3>2. Start from the document</h3>
Open the Sale Order (or other document) → more menu → <b>WorkFlow Request</b>.

<h3>3. Fill in details</h3>
<ul>
<li>Enter <b>Title</b>, <b>Date</b>, and optionally <b>Due date</b>.</li>
<li><b>Request Owner</b> is auto-filled with the logged-in user.</li>
<li>Select the <b>Approval Template</b>.</li>
<li>Add a <b>Description</b> (what must happen, customer, items).</li>
</ul>

<img src="hr/images/new-workflow.webp" alt="New WorkFlow Request" loading="lazy">

<h3>4. Send the first stage</h3>
Save (status = Draft), open the request, and click <b>Send Request</b> on Stage 1. Choose the person who will do that step.

<hr class="doc-section-divider">

<h2 id="header-fields">Header Fields Reference</h2>

| **Field** | **Description** |
|-----------|-----------------|
| Title * | Short name for the process (for example Sale Delivery — Acme SO-1042). |
| Request Number | Auto-generated when numbering is configured. |
| Request Owner * | Employee who owns the request. Auto-filled on create. |
| Date * | Creation date and time. |
| Due date | Deadline for finishing the process. |
| Approval Template * | Process template to follow. |
| Description | What must be done (rich text). |

<b>View-only fields</b>

| **Field** | **Description** |
|-----------|-----------------|
| Origin Transaction | Linked document type (for example Sale Order) when created from a document. |
| Origin Transaction [Id] | Quick-view link to that document. |

<hr class="doc-section-divider">

<h2 id="stage-panel">Stage panel</h2>

The request view shows each stage from the template: name, status, history, attachments, linked documents, and buttons.

<img src="hr/images/workflow-new.webp" alt="WorkFlow Request view with stages" loading="lazy">

<b>Stage status values</b>

| **Status** | **Description** |
|------------|-----------------|
| Not Requested | This step has not been sent yet. |
| Approval Requested | Waiting for the assigned person to complete the step. |
| Approved | Step is complete. |
| Rejected | The assigned person rejected the step. |
| Cancelled Request | The requestor cancelled while it was waiting. |
| Requested for Revision | Sent back to the request owner. |

<b>Per-stage information</b>

Each log shows <b>By</b>, <b>Time</b>, <b>Note</b>, <b>Next Action By</b>, <b>Pending Approval By</b>, <b>Min no. of approvals required</b>, attachments (paperclip), and <b>Linked Documents</b> (bill number and type).

<b>Per-stage buttons</b>

| **Button** | **Who sees it** | **When** |
|------------|-----------------|----------|
| Send Request | Request owner | Stage not started, or after revision; prior stage approved. |
| Approve | Assigned person (or Super User) | Stage status = Approval Requested. Marks the step done. |
| Reject | Assigned person (or Super User) | Stage status = Approval Requested. |
| Cancel | Original requestor | Stage status = Approval Requested. |
| Send For Revise | Assigned person | Stage status = Approval Requested. |
| Edit | Request owner | Stage sent for revision and document editing is allowed. |
| Custom button (for example Create Delivery Note) | Users on that stage after it has been sent | Stage has Actions configured. |

<b>How stages flow</b>

<ol>
<li>Request owner clicks <b>Send Request</b> on Stage 1 and selects who will do the step. Request status becomes <b>Multi Level Approval</b>.</li>
<li>That person adds notes or attachments if needed. If the stage has a system action, they click the button (Create Delivery Note, Create Sale Invoice) to open the New form.</li>
<li>They click <b>Approve</b> to mark the step done. Optionally tick <b>Request Next Stage</b> and choose who does the next step.</li>
<li>Stages run in order. A process-only stage has no extra button — Approve plus notes and attachments is enough.</li>
<li>After the last stage is approved, the WorkFlow Request status is <b>Approved</b>. The origin Sale Order is unchanged.</li>
</ol>

<hr class="doc-section-divider">

<h2 id="stage-actions">Stage actions (create documents)</h2>

On <a href="#/hr/workflow-approval-stage">WorkFlow Approval Stage</a>, the Actions table adds buttons to that step.

| **Column** | **Description** |
|------------|-----------------|
| Action Type (Transaction) | Document to create. |
| Button Label | Text on the request view (for example Create Delivery Note). |

<b>Action Type options:</b> Sale Invoice, Sale Order, Sale Quotation, Pro Forma Invoice, Commercial Invoice, Credit Note, Purchase Invoice, Purchase Order, Purchase Quotation, Debit Note, Purchase Expense, Delivery Note, Receipt Note, Expense, Payment Voucher, Receipt Voucher, Expense Claim.

Leave the Actions table empty for a process-only step (site visit, quote collection, verbal confirmation).

The New form opens with the request linked. After save, the document shows under <b>Linked Documents</b> on that stage.

Dialogs for Send Request / Approve / Reject / Send For Revisal / Cancel are the same as on document Multi Stage Approval (Notes, Approver, Request Next Stage). Attachments can be added on each log.

<hr class="doc-section-divider">

<h2 id="use-case-sale-delivery">Use case — Sale Order to delivery and invoice</h2>

A Sale Order is received. The company still needs to purchase, take stock in, deliver, and invoice. Those steps are a WorkFlow Request, not approval of the Sale Order.

<h3>1. Create stages</h3>

| **Stage Name** | **Approval Rule** | **Approvers** | **Actions** |
|----------------|-------------------|---------------|-------------|
| Purchase / supplier | ANY | Purchase executives | — (process-only: site visit, quotes, attachments) |
| Stock in | ANY | Store keepers | Action Type = Receipt Note, Button Label = Create Receipt Note |
| Delivery | ANY | Dispatch team | Action Type = Delivery Note, Button Label = Create Delivery Note |
| Sale invoice | ANY | Accounts | Action Type = Sale Invoice, Button Label = Create Sale Invoice |

<h3>2. Create the template</h3>

Template name: <b>Sale Delivery</b>

| **Sl Num** | **Approval Stage** |
|------------|-------------------|
| 1 | Purchase / supplier |
| 2 | Stock in |
| 3 | Delivery |
| 4 | Sale invoice |

<h3>3. Start from the Sale Order</h3>

<ol>
<li>Open the approved Sale Order.</li>
<li>More menu → <b>WorkFlow Request</b>.</li>
<li>Title: <b>Sale Delivery — Acme SO-1042</b></li>
<li>Approval Template: <b>Sale Delivery</b></li>
<li>Description: items, customer, promised date.</li>
<li>Save.</li>
</ol>

<h3>4. Run the process</h3>

<div class="doc-workflow">
  <div class="doc-workflow-step">
    <strong>Sale Order</strong>
    <span class="doc-workflow-detail">More menu → WorkFlow Request</span>
  </div>
  <div class="doc-workflow-arrow" aria-hidden="true">→</div>
  <div class="doc-workflow-step">
    <strong>Purchase / supplier</strong>
    <span class="doc-workflow-detail">Visit, quotes, attachments — then Approve</span>
  </div>
  <div class="doc-workflow-arrow" aria-hidden="true">→</div>
  <div class="doc-workflow-step">
    <strong>Stock in</strong>
    <span class="doc-workflow-detail">Create Receipt Note → Approve</span>
  </div>
  <div class="doc-workflow-arrow" aria-hidden="true">→</div>
  <div class="doc-workflow-step">
    <strong>Delivery</strong>
    <span class="doc-workflow-detail">Create Delivery Note → Approve</span>
  </div>
  <div class="doc-workflow-arrow" aria-hidden="true">→</div>
  <div class="doc-workflow-step">
    <strong>Sale invoice</strong>
    <span class="doc-workflow-detail">Create Sale Invoice → Approve</span>
  </div>
</div>

<ol>
<li>Request owner sends Stage 1 to a purchase executive.</li>
<li>Purchase visits the supplier, attaches quotes, clicks <b>Approve</b>, and sends Stage 2 to stores.</li>
<li>Stores clicks <b>Create Receipt Note</b>, saves the receipt, then <b>Approve</b>.</li>
<li>Dispatch clicks <b>Create Delivery Note</b>, delivers, then <b>Approve</b>.</li>
<li>Accounts clicks <b>Create Sale Invoice</b>, then <b>Approve</b>.</li>
<li>The WorkFlow Request is Approved. The original Sale Order is still the same document — this process did not sign it off.</li>
</ol>

If the Sale Order itself must be signed off before it is Approved, that is a separate <a href="#/features/multiapproval">Multi Stage Approval</a> template on the order.

<hr class="doc-section-divider">

<h2 id="use-case-po-process">Use case — Process that creates a Purchase Order</h2>

When the first documents do not exist yet, start from HRMS → Workflow Request (or from another origin document) and put a Create PO action on a later stage.

| **Stage Name** | **Approval Rule** | **Actions** |
|----------------|-------------------|-------------|
| Manager review | ANY | — |
| Finance review | ALL | — |
| Raise PO | ANY | Action Type = Purchase Order, Button Label = Create PO |

After Raise PO is sent, <b>Create PO</b> opens New Purchase Order linked to this request. The PO appears under Linked Documents.

<hr class="doc-section-divider">

<h2 id="actions-status">Actions &amp; Status</h2>

<h3>View toolbar actions</h3>

| **Action** | **Description** | **Available when status is** |
|------------|-----------------|------------------------------|
| Edit | Opens for editing. | Draft, For Revisal |
| Delete | Permanently removes the request. | Draft, For Revisal |
| Print | Prints the request. | All |

<h3>More menu (⋮) actions</h3>

| **Action** | **Description** | **Available when status is** |
|------------|-----------------|------------------------------|
| Cancel | Cancels the request. | Approved, Closed |

<h3>Statuses</h3>

| **Status** | **Description** |
|------------|-----------------|
| Draft | Saved but Stage 1 has not been sent. |
| Multi Level Approval | A stage is in progress. |
| Approved | All stages complete. The origin document is unchanged. |
| For Revisal | Sent back for changes. Treated like Draft for edit. |
| Cancelled | Request has been cancelled. |
| Closed | Request is closed. |

<hr class="doc-section-divider">

<h2 id="view-tabs">View Tabs &amp; Side Panels</h2>

| **Tab** | **What it shows** |
|---------|-------------------|
| History | Activity log — who created, sent, approved, rejected, or cancelled and when. |
| Attachments | Files uploaded to the request. |

Stage logs also have a paperclip for per-step files (quotes, photos, signed papers).

<hr class="doc-section-divider">

<h2 id="best-practices">Best Practices</h2>

<ul>
<li>Name templates after the process (Sale Delivery, Installation, Warranty return), not after document approval.</li>
<li>Start the request from the origin document so Origin Transaction stays linked.</li>
<li>Use process-only stages for work that happens outside Freespace (site visit, supplier meeting). Ask for notes and attachments before Approve.</li>
<li>Put Create Delivery Note / Create Sale Invoice (and similar) only on the stage that should produce that document.</li>
<li>Do not use a WorkFlow Request to replace Settings Multi Stage Approval when the invoice itself must not post until managers sign it.</li>
<li>Use the <a href="#/hr/reports/workflow-request-report">WorkFlow Requests Report</a> to see open processes.</li>
</ul>

<hr class="doc-section-divider">

<h2 id="faq">FAQ</h2>

<b>Does finishing a WorkFlow Request approve the Sale Order or Sale Invoice?</b><br>
No. Only the request is marked Approved. Document sign-off is <a href="#/features/multiapproval">Multi Stage Approval</a> under Settings.

<b>How do I start a workflow from a Sale Order?</b><br>
Open the order, more menu, WorkFlow Request. Choose the Sale Delivery (or other) template and save.

<b>Must every stage create a document?</b><br>
No. Leave Actions empty. The assigned person completes the step with Approve, notes, and attachments.

<b>Can I skip a stage?</b><br>
No. Stages run in Sl Num order. The previous stage must be Approved before the next can be sent.

<b>Can multiple people be assigned to one stage?</b><br>
Yes. The stage Approval Rule (ANY, ALL, MINIMUM) decides how many must click Approve.

<b>Who can see pending steps?</b><br>
Assigned people see Approve and Reject on their stage. Super Users can act on any stage. Use the <a href="#/hr/reports/workflow-request-report">WorkFlow Requests Report</a> for a list view.

<b>What happens when a stage is rejected?</b><br>
That stage is Rejected. Later stages do not run until the request is sent again or cancelled.

<b>Can I attach files?</b><br>
Yes. Use the Attachments tab on the request, and the paperclip on each stage log.

<b>Does completing a stage send notifications?</b><br>
Assignees and the request owner may receive in-app notifications per company notification settings.

<hr class="doc-section-divider">

<h2 id="related">Related Topics</h2>

<ul>
<li><a href="#/hr/workflow-approval-stage">WorkFlow Approval Stage</a> — process steps and optional Create-document buttons</li>
<li><a href="#/hr/workflow-approval-template">WorkFlow Approval Template</a> — stage order</li>
<li><a href="#/sales/sale-order">Sale Order</a> — WorkFlow Request on the more menu</li>
<li><a href="#/features/multiapproval">Multi Approval</a> — signing off the document itself</li>
<li><a href="#/hr/reports/workflow-request-report">WorkFlow Requests Report</a></li>
<li><a href="#/hr/reports/approval-request-report">Approval Requests Report</a></li>
</ul>

<section class="ai-index-only">

## Errors and warnings

Exact messages for Workflow Request from the ERP screen and `fs_api`. Visitors do not see this section; Vertex AI Search uses it to answer questions about on-screen errors.


### Future or back-dated date

- **Type:** Error (blocks save)
- **Action:** Save, Save And Approve
- **When:** Date is in the future and future-date transactions are off, or the user cannot enter previous dates, or the date is before the allowed cutoff.
- **Example message:** *Future date transactions are not allowed.* or *Previous date transaction entries are not allowed.* or *Transaction date cannot be before YYYY-MM-DD.*
- **Outcome:** The document is not saved.
- **Solution:** Set Date to an allowed date, then save.

### Accounts closed for the date

- **Type:** Error
- **Action:** Approve, Save And Approve, Master Update
- **When:** The document date is in a closed accounting period.
- **Example message:** *Accounts closed for the date*
- **Outcome:** Not posted, or the date is not changed.
- **Solution:** Use a date after the accounts closing date.

### Multi-level approval required

- **Type:** Error / workflow
- **Action:** Approve, Save And Approve
- **When:** An active multi-level approval template matches this document.
- **Example message:** *Multi level approval is required*
- **Outcome:** Direct approve is blocked.
- **Solution:** Use Send Request on the first stage. For other stage-action messages (*You are not authorized…*, *Already requested for approval.*, *Cannot … at the current status.*), see <a href="#/features/multiapproval?id=action-errors">Multi Approval — Action error messages</a>.

### Edit or delete not allowed

- **Type:** Error
- **Action:** Edit, Delete
- **When:** Status is not Draft or For Revisal, or auto bill-number is on for delete.
- **Example message:** *Edit not allowed in the current status* or *Invalid status* or *Delete prevented..*
- **Outcome:** Posted documents stay in the ledger.
- **Solution:** Cancel a posted document after unlinking related records. Delete only drafts.

### Cancel date restriction

- **Type:** Error
- **Action:** Cancel
- **When:** User cannot cancel previous-date transactions, or the date is before the cancel cutoff.
- **Example message:** *Cancelling previous date transactions are not allowed* or *Cancelling transactions before YYYY-MM-DD is not allowed.*
- **Outcome:** Not cancelled.
- **Solution:** Cancel only dates the user is allowed to cancel.

Workflow Request uses the shared Transaction and multi-level approval messages (*Multi level approval is required*, *You are not authorized for approval*, *Already requested for approval.*). There are no extra document-specific API strings.

</section>
