Use this section to define the revision parameters for the forms of this entity. To do that, check the Control form revision field and configure the following fields:
Field
|
Revision process
|
Select the desired option to define the revision template that will be used by the forms of this entity:
▪ISO9000 based: The revision of the forms of this entity will be based on the ISO9000 standard. ▪Workflow: The revision of the forms of this entity will be controlled by a process instantiated in the SE Workflow component. In that case, a process (SE Process) must be properly configured and modeled. Refer to the Revision process configuration section for more details about the revision process configuration. |
Route type
|
Define how the revision route will be. The options available for selection will vary according to the previously selected revision process:
▪Workflow: This field will be filled out with the "Fixed" option and cannot be edited. In this case, it will be possible to edit the process selected in the respective field when creating the revision. ▪ISO9000 based: Select one of the following options: ▪Variable: Allows the revision route to be selected/edited when creating the revision, in addition to allowing editing its members. ▪Fixed: Allows the revision route to be selected/edited when creating the revision; however, it will not be possible to edit its members. ▪Fixed & unique: A default revision route will be set for all the forms of this entity, that is, the route selected in the respective field may not be edited (nor its members) when creating the revision. |
Route
|
This field will be available if the previously selected revision process is "ISO9000 based". In this case, select the revision route of the forms of this entity. If the previously selected route type is "Fixed & unique", the completion of this field will be mandatory.
|
Process
|
This field will be available if the previously selected revision process is "Workflow". In this case, select the process that will be used in the revision of the forms of this entity. The revision process of the forms must be previously configured through the SE Process component.
|
ID #
|
Select how the reference revision ID # of the forms of this entity will be generated:
▪Numeric: A sequential number will be generated by the system automatically. E.g.: 0, 1, 2, 3, ..., n; ▪Text: An alphabetical sequence will be generated by the system automatically. E.g.: A, B, C, ..., AA, AB, ..., ZZ; ▪Customized: The system does not fill out this field and allows the user to assign any value to the revision ID #. |
Cycle
|
Select how the forms revision cycle number will be generated:
▪Numeric: A sequential number will be generated by the system automatically. E.g.: 0, 1, 2, 3, ..., n; ▪Text: An alphabetical sequence will be generated by the system automatically. E.g.: A, B, C, ..., AA, AB, ..., ZZ; |
Retain obsolete revisions up to
|
Enter the number of revisions/months/years that will remain in the history of the forms of this entity.
|
Change
|
Select how the number of changes in the revision of the forms will be generated:
▪Numeric: A sequential number will be generated by the system automatically. E.g.: 0, 1, 2, 3, ..., n; ▪Text: An alphabetical sequence will be generated by the system automatically. E.g.: A, B, C, ..., AA, AB, ..., ZZ; |
ISO9000 settings (available only for "ISO9000 based" revision processes)
|
Approval
|
Select one of the following options to define how the revision approval will be:
▪Incremental: The draft of a revision may be rejected both by the reviewer and the approver of the revision. If it is rejected by the reviewer, it automatically returns to the drafter. ▪Circular: The draft of a revision may only be rejected by the revision approver. Rejection by the reviewer does not return the revision to the draft step. |
Closure
|
Select one of the following options to define how the revision will be finished:
▪Automatic: When the releaser executes their task, the revision will be automatically closed, meaning that the system will not generate the revision "Closure" step. ▪Manual: When the releaser executes their task, the "Revision closure" step will be generated for the responsible users. |
Draft
|
Configure how the system should proceed if there is more than one participant with the same sequence in each of the revision steps. Select one of the following options for each of the fields:
▪AND: All the participants of the step must accept the revision before it may continue to the next step; ▪OR: At least one of the participants must accept the revision before it may continue to the next step; |
Review
|
Approval
|
Release
|
Option
|
Checked
|
Unchecked
|
Require explanation to be filled out when revision is started
|
Once the forms revision starts, filling out the Explanation field will be mandatory.
|
Filling out the Explanation field will not be mandatory.
|
Require changes from draft step to be filled out
|
In the revision draft step, it will be mandatory for the drafter to enter the location of the forms and the change, in the "Change" tab of the revision data. This parameter is not valid for the first cycle of a document being issued.
|
The revision draft step may be sent to the next step without entering the changes.
|
Block obsolete revision deletion
|
Obsolete revisions of forms cannot be deleted. Open revisions can be deleted.
|
Any obsolete or open revision can be deleted, whereas current revisions cannot be deleted in any case.
|
Save the record after performing the necessary configurations.
|