Module: Revision Request
Overview
The "Revision Request" module allows any user to submit a modification request for an existing document. This module operates downstream of the document to trigger its revision cycle.
Processing Flow
Document Consultation → Revision Request → DM Manager Validation
→ Create New Version (if accepted)
Entry Point
The "Revision Request" button appears in the "Quality Module" component under the following conditions:
QVersionDoing= 0 (document not being modified)- Valid document
- Visible only for applicable documents

Form
General Information
| Property | Value |
|---|---|
| Form Name | Revision Request |
| Purpose | Formalize and track modification requests for existing documents |
| Injection | Form and workflow injected by Synctool (templates provided by the product) |
Form Structure
The form is organized into two main sections:
HEADER Section
Document reference information (auto-calculated):
- Reference (calculated)
- Title
- Version (calculated)
- Step (calculated)
REQUEST Section
Information related to the revision request:
- Subject* (required)
- Issuer
- Request Date
- Status
- Validator
Form Fields
The following table details all fields available in the form:
| Label | Technical Name | Type | Values | List | Multi | Default | Description |
|---|---|---|---|---|---|---|---|
| Reference | Reference | Text | Calculated | - | No | - | Calculated by the system according to a given convention |
| Title | Title | Text | Free | - | No | - | Allows document referencing |
| Version | Version | Number | Calculated | - | No | - | Allows document versioning |
| Step | current_activity | Text | Calculated | - | No | - | Displays document status in the workflow |
| Subject* | Objet | Text | Free | - | No | - | Multiline - 4000 characters max |
| Issuer | Emetteur | Text | Directory | - | No | Connected user | - |
| Request Date | DateDemande | Date | Calendar | - | No | Current date | - |
| Status | vStatus | Text | Calculated | DDR_STATUTS | No | - | Current status of the request |
| Validator | MRValidator | Text | Directory | - | No | Empty | Document manager |
Legend and Information
*: Field required on save- Multi: Accepts multiple values
- List: Value list used (injected by Synctool for DDR_STATUTS)
⚠️ Warning: The vStatus field depends on the DDR_STATUTS list which must be configured in the system.






Workflow
General Information
| Property | Value |
|---|---|
| Workflow Name | Revision Request |
| Purpose | Validate or reject a document revision request |
| Particularity | The workflow follows 2 paths depending on whether the issuer is a manager or not |
Resources Used
Profiles
- QDM - Advanced User
- QDM - Portal
- Administrator
Actors
- DM Manager
- Editor
- F-ResponsableValidation
- R-QDMAdmin
- QDM_Admin
- QDM_Lecteur
Roles
- QDMAdmin
- QDMAuthor
- QDMLecteur
Workflow Schema
┌──────────────┐
│ Step 1 │
│ Input │
│ (Editor) │
└──────┬───────┘
│
┌──────────────┴──────────────┐
│ │
Issuer = Issuer ≠
Manager Manager
│ │
▼ ▼
[Workflow ended] ┌──────────────┐
Status = 3 │ Step 2 │
(Auto-validation) │ Validation │
│(DM Manager) │
│ │
└──────┬───────┘
│
┌───────┴────────┐
│ │
Accept Reject
│ │
▼ ▼
[END: Validated] [END: Rejected]
Status = 3 Status = 3

Detailed Steps
Step 1 - Input
General Properties
| Property | Value |
|---|---|
| Description | Allows entering a revision request |
| Participants | Editor |
| Readers | R-QDMAdmin |
| Modifiable Fields | Defined in F3 Revision Request tab |
| Reminder | No |
Validation Rules
| Button | Required Fields | Comment | Description |
|---|---|---|---|
| Send Request | Defined in F3 Revision Request tab | No | Automatically sends the request for validation |
Exit Transitions
| Link | Condition | Notification | Action |
|---|---|---|---|
| Input → Workflow ended | Manager creates the request | No | Status = 3 |
| Input → Validation | Issuer ≠ Manager | Yes to DM Manager | Status = 1 |


Step 2 - Validation
Step 2 Configuration
| Property | Value |
|---|---|
| Description | Allows validating a revision request |
| Participants | DM Manager |
| Readers | R-QDMAdmin, R-QDMLecteur |
| Modifiable Fields | Defined in F3 Revision Request tab |
| Reminder | Yes, monthly to F-ResponsableValidation |
Buttons and Validation
| Button | Required Fields | Comment | Description |
|---|---|---|---|
| Accept Request | Defined in F3 Revision Request tab | No | Accepts the revision request |
| Reject Request | Defined in F3 Revision Request tab | Yes and mandatory | Rejects the revision request |
Exit Paths
| Link | Condition | Notification | Action |
|---|---|---|---|
| Validation → End | Accept (default) | Yes to Editor | Status = 3 |
| Validation → End | Reject request | Yes to Editor | Status = 3 |
End Event - Validated
| Property | Value |
|---|---|
| Trigger | Input → End (manager creates the request) |
| Description | Ends the document |
| Modification Rights | R-QDMAdmin |
| Read Rights | QDM_Lecteur |
End Event - Rejected
| Property | Value |
|---|---|
| Trigger | Validation → End (request rejection) |
| Description | Ends the document after rejection |
| Modification Rights | R-QDMAdmin |
| Read Rights | None |
Views
Views allow tracking the status of revision requests.
View Types
- My revision requests: Requests created by the user
- Requests to validate: Pending validation
- Validated requests: Approved
- Rejected requests: Rejected
Available Features
Each view offers the following features:
- Full-text search engine
- Filters by status, issuer, concerned document
- Excel export

Dependencies
Dependencies with Document Module
Field Inheritance
Field inheritance must be configured from "Document Form" to "Revision Request" to automatically populate revision request fields.
| Source Field (Document) | Target Field (Revision Request) | Note |
|---|---|---|
| Reference | Reference | Document reference |
| Title | Title | Document title |
| Version | Version | Current version |
| Ged_Gestionnaire | MRValidator | Manager becomes the validator |


Required Value Lists
| Value List | Usage | Impact |
|---|---|---|
| DDR_STATUTS | Request status (vStatus) | Required - Injected by Synctool |
Link to New Version Creation
Once the revision request is accepted, the document manager can create a new version via the "Create new version" button in the "Quality Module" component.
New Version Creation Mechanism
The "Create new version" button is managed by the QDM_Version actor. Creating a new version triggers:
- Automatic incrementation of the version number
- Population of the
IDPreviousVersionfield with the previous version ID - Setting the new version's
QVersionDoingto "1" (Document being modified) - Starting the new version at the "Drafting" step of the Document workflow
Project Feedback
To Be Completed
Section to be completed based on field experience feedback.