24.12 Update 07-Feb-25
Importing and Updating Design Review Issues (DRIs)
Overview
This update enhances the ability to import and update Design Review Issues (DRIs), ensuring greater control over how DRIs are linked to document revisions. Additionally, new validation rules prevent unintended behavior when dealing with Mark Up (MU) Revisions.
Functionality
The system now supports the following scenarios when importing DRIs:
1. Creating a New DRI (Empty Reference)
Condition: The "Reference" field in the import file is empty.
Outcome: The system will create a new DRI and assign the next available reference number in sequential order.
Example:
Import File
Reference | Document No. | Revision | DRI Title |
---|---|---|---|
(Empty) | DOC001 | A | "Review missing details" |
Result: The system assigns the next available reference (e.g.,
DRI#0050
) and links it toDOC001
on Revision A.
2. Updating an Existing DRI (Reference Already Exists)
Condition: The reference in the import file matches an existing DRI.
Outcome: The system updates the existing DRI with the provided details.
Example:
Existing DRI in System:
DRI#0032
linked toDOC001
(Rev A)Import File
Reference | Document No. | Revision | DRI Title |
---|---|---|---|
DRI#0032 | DOC001 | A | "Additional comments added" |
Result:
DRI#0032
is updated with the new Title for Revision A ofDOC001
.
3. Creating a New DRI with a Specific Reference (Reference Does Not Exist)
Condition: The reference in the import file does not exist in the system.
Outcome: The system creates a new DRI using the provided reference.
Example:
Reference | Document No. | Revision | DRI Title |
---|---|---|---|
DRI#0100 | DOC002 | A | "New issue detected" |
Result: The system creates a new DRI with the reference
DRI#0100
linked toDOC002
on Revision A.
New Validation Rules for Mark Up (MU) Revisions
This update introduces additional validation when dealing with MU revisions:
4. Importing to Create a New DRI Against an MU Revision (Not Allowed)
Condition: An import attempt is made to create a DRI against an MU revision.
Outcome: The import will be skipped for those rows, and an error message will be displayed.
Error Message:
"You cannot create a new Design Review Issue (DRI) against a Mark Up revision. These rows will be skipped."
Example:
Import File
Reference | Document No. | Revision | DRI Title |
---|---|---|---|
(Empty) | DOC003 | A-MU1 | "Check alignment issue" |
Result: The import for this row is skipped, and the user is notified.
This scenario will be supported in a future release so that you will be able to import a DRI against a MU rev.
5. Importing to Update an Existing DRI Against an MU Revision (Allowed)
Condition: The reference in the import file matches an existing DRI linked to an MU revision.
Outcome: The system updates the existing DRI.
Example:
Existing DRI in System:
DRI#0045
linked toDOC004
(Rev A-MU1)
Reference | Document No. | Revision | Description |
---|---|---|---|
DRI#0045 | DOC004 | A-MU1 | "Additional alignment check required" |
Result:
DRI#0045
is successfully updated for Revision A-MU1.