Flow Definition: Purchase Request Flow
This document elaborates on the "Flow Definition" section of specification.md.
Basic Information
| Item | Value |
|---|---|
| Flow Name | Purchase Request Flow |
| Flow ID | purchase_request |
| Version Control | Used (standard setting) |
| Application Reference Date | System date (default) |
| Matter Name Rule | PurchaseRequest_[ApplicantName]_[VendorName] |
Flow Group
| Item | Value |
|---|---|
| Assigned Flow Group | Placed in the tenant's default group |
Association of Content Definition and Route Definition
| Related Definition | Definition Name | Definition ID | Configuration Method | Detailed Document |
|---|---|---|---|---|
| Content Definition | Purchase Request Content | purchase_request_content | Initial setting | content_definition.md |
| Route Definition | Purchase Request Route | purchase_request_route | Initial setting | route_definition.md |
Function Settings
| Function Setting | Configured Value | Notes |
|---|---|---|
| Calendar | Standard calendar | The calendar used for the desired-delivery-date validity check (BR-004) |
| Attachments | Used | PDF files such as quotes and catalogs can be attached |
| Batch Processing Feature | Used | Approvers can process multiple purchase requests together |
| Review of Completed Matters | Used | Past purchase request history can be reviewed |
| Automatic Processing | Not used | Manual approval only |
| Processing Deadline | Not configured | The urgency field conveys operational priority instead |
| Automatic Reminders | Not used | Not needed since no processing deadline is configured |
| Asynchronous Processing | Not used | Not needed at this scale, which completes with synchronous processing |
| Matter Operation Authority | Not configured | Only workflow operations administrators can operate matters |
| Standard Organization | Not configured | Uses the tenant's default organization |
| Date to Resolve Assignees | Matter start date | Timing at which assignees are resolved |
| Applicant Self-Approval Prevention | Enabled | Prevents (skips) self-approval if the applicant is resolved as an assignee of an approval node |
Function Policies
| Function | Policy | Notes |
|---|---|---|
| Temporary Save Feature | Used | Allows temporary saving on the application screen in case there are many line items |
| Confirmation Feature | Not used | No need for confirmation-target users to review matters |
| Proxy Feature | Allowed | A proxy approver can process when the department manager is absent. Uses the standard IM-Workflow proxy setting screen |
Master Definition Structure
Related Documents
- specification.md - Main specification
- content_definition.md - Content definition
- route_definition.md - Route definition