Skip to main content
Version: Next

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

Home Page - In Progress - Revision Request

Form

General Information

PropertyValue
Form NameRevision Request
PurposeFormalize and track modification requests for existing documents
InjectionForm 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:

LabelTechnical NameTypeValuesListMultiDefaultDescription
ReferenceReferenceTextCalculated-No-Calculated by the system according to a given convention
TitleTitleTextFree-No-Allows document referencing
VersionVersionNumberCalculated-No-Allows document versioning
Stepcurrent_activityTextCalculated-No-Displays document status in the workflow
Subject*ObjetTextFree-No-Multiline - 4000 characters max
IssuerEmetteurTextDirectory-NoConnected user-
Request DateDateDemandeDateCalendar-NoCurrent date-
StatusvStatusTextCalculatedDDR_STATUTSNo-Current status of the request
ValidatorMRValidatorTextDirectory-NoEmptyDocument 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.

Revision Request Form - Components

DDR Doc Parent Component - Revision Request

DDR Hidden Component - Revision Request

DDR Subject Component - Revision Request

DDR Origin Component - Revision Request

DDR Status Component - Revision Request

Workflow

General Information

PropertyValue
Workflow NameRevision Request
PurposeValidate or reject a document revision request
ParticularityThe 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

Revision Request Workflow

Detailed Steps

Step 1 - Input

General Properties
PropertyValue
DescriptionAllows entering a revision request
ParticipantsEditor
ReadersR-QDMAdmin
Modifiable FieldsDefined in F3 Revision Request tab
ReminderNo
Validation Rules
ButtonRequired FieldsCommentDescription
Send RequestDefined in F3 Revision Request tabNoAutomatically sends the request for validation
Exit Transitions
LinkConditionNotificationAction
Input → Workflow endedManager creates the requestNoStatus = 3
Input → ValidationIssuer ≠ ManagerYes to DM ManagerStatus = 1

Publication Page - Input - Revision Request

Page Rules - Revision Request

Step 2 - Validation

Step 2 Configuration
PropertyValue
DescriptionAllows validating a revision request
ParticipantsDM Manager
ReadersR-QDMAdmin, R-QDMLecteur
Modifiable FieldsDefined in F3 Revision Request tab
ReminderYes, monthly to F-ResponsableValidation
Buttons and Validation
ButtonRequired FieldsCommentDescription
Accept RequestDefined in F3 Revision Request tabNoAccepts the revision request
Reject RequestDefined in F3 Revision Request tabYes and mandatoryRejects the revision request
Exit Paths
LinkConditionNotificationAction
Validation → EndAccept (default)Yes to EditorStatus = 3
Validation → EndReject requestYes to EditorStatus = 3

End Event - Validated

PropertyValue
TriggerInput → End (manager creates the request)
DescriptionEnds the document
Modification RightsR-QDMAdmin
Read RightsQDM_Lecteur

End Event - Rejected

PropertyValue
TriggerValidation → End (request rejection)
DescriptionEnds the document after rejection
Modification RightsR-QDMAdmin
Read RightsNone

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

Home Page - End - Revision Request

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
ReferenceReferenceDocument reference
TitleTitleDocument title
VersionVersionCurrent version
Ged_GestionnaireMRValidatorManager becomes the validator

Field Inheritance - Revision Request

Value Lists - Revision Request - Status

Required Value Lists

Value ListUsageImpact
DDR_STATUTSRequest status (vStatus)Required - Injected by Synctool

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 IDPreviousVersion field with the previous version ID
  • Setting the new version's QVersionDoing to "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.