Configuration control of database entries

Darryl Bennett

• June 19, 2019 22:51

We have expanded the number of users of E3 and need to implement some controls on creating and editing components and symbols in our database. Currently all E3 users can create and edit anything, but our interns may not have the experience to know when they could mess something up. Is there a way to implement review and approval of entries before becoming live in the production database? Are there methods for review/approval other than restricting all component and symbol editing to a subset of the users?

Was this Helpful?

0

• 

  Permanently deleted user

  • June 19, 2019 23:02

  The best way I have found to accomplish this task is to create separate production and development databases. The development database is a copy of the production. Any new parts that are added or created in the development phase are then sent for approval by editing the component/symbols in database mode and saving that file on the hard drive. This file, when opened by approving authority, will show the parts ready for review and edits (if necessary). These can then be saved in the production database. 

  There is no dedicated tool for review that i can remember.

  Was this Helpful?

  0

Please sign in to leave a comment.