Skip to content

Latest commit

 

History

History
96 lines (63 loc) · 3.67 KB

07-DbInteraction.md

File metadata and controls

96 lines (63 loc) · 3.67 KB

FreePDM

Concept Of Design

User / File / Database / Version management interaction

Introduction

There is a complex interaction between the User, the file(s), the database and the version management system needed.
(Most of) these interactions are noted in the workflows below. All functionalities interact with each other.

Assumptions

What is happening with the version handling and the database.

  • The database that is part of the item can be locked
  • The database that has knowledge of all available items not
  • The database that is related to the CAD files is part of the versioning system
  • If a CAD file is released, it's related (database) item is also released
  • From the database interaction the version system gives the user write access
  • From the database interaction the version system releases the user write access.

Workflow 1

A user wants to edit a file, here is the logic that occurs:

  1. The database needs to be checked if the file is writable()
  2. The database needs to be checked if the user is allowed to check-out the file
    • Not in release state.
    • Not Checked-Out by another user
  3. Give the user write access in the version system AND block all other users.

After finishing the edits:

  1. Save the file to the server
  2. (Automatically) edit the database Attributes regarding changes
  3. Check-in the file
  4. Release the write access AND release the block of other users

questions / Comments 1

  • Within which databases is set who checked-out a file? Is that on an object level or at main level?

Workflow 2

A user wants to edit an Attribute (what is part (not CAD part) of the database), the logic is involved:

  1. The database needs to be checked if the item where the attributes belongs to are writable (AKA not locked).
    • Not in release state.
    • Not Checked-Out by another user
  2. Give the user write-access in the version system AND block all other users.

After finishing the edits:

  1. Save the changed attributes to the server
  2. (Automatically) edit the database Attributes regarding changes
  3. Check-in the (database) item
  4. Release the write-access AND release the block of other users

questions / Comments 2

  • This step should also work for multiple attributes from multiple file(s) (and filetypes).

Workflow 3

A user wants to release an Item (basically the CAD model, CAD drawing, database Item, and other documentation):

  1. The database needs to checked what files are already released
  2. Fulfill the Engineerings Change Process (not described, but basically a set of checks)
  3. Database Change all Attributes that are affected to a higher revision number.
  4. Database Change all Attributes that are affected to a Release state.
  5. The affected database items are locked AND the affected files (file locations) are locked for All users.

questions / Comments 3

  • This step should also work for a whole module / assembly structure.

Workflow 4

A user wants to change an previously released Item. For example, a CAD file.

  1. The user requests a change to the needed file(s) AND the (database) item
  2. (Optionally) accepted by supervisor
  3. (Optionally) a copy is made from the released version so a changed version can always be reverted.
  4. Database Change all Attributes that are affected to an InWork state
  5. Workflow 1
  6. Optionally Workflow 2
  7. Workflow 3.

questions / Comments 4

  • This step should also work for a whole module / assembly structure.

<< Previous Chapter | Content Table | Next Chapter >>