DriveWorks Pro 15: Project Settings [send feedback...]

Introduction

To edit the Project Settings a project must be open.

Hide project from new specification list

With this option checked the project will be hidden from users that don't have edit permissions for the project.

Hide Project from non-administrators

With this option checked the project will be hidden from non-administrative users.

Non-administrative users are members of a Team that do not have Edit permissions on a project.

See Project Permissions Tab under the heading To Edit a Team's Members, and Permissions for more information.

This setting allows a project to easily be taken offline for editing as it will override the settings applied in Security Settings.

This setting is checked by default for all new projects.
This setting should be unchecked before making the project available for production use.

Create documents relative to specification directory

With this option checked all documents will be stored relative to the specification. If unchecked documents will be created directly in the Specifications folder all in one location.

Create additional folders relative to specification directory

With this option checked all additional folders will be created relative to the specification path. If unchecked the additional folders will be created directly in the Specifications folder.

Metadata directory name

The metadata folder is a subfolder of the specification folder where DriveWorks files related to a specification are stored, such as a copy of the project file, specification property information, and a copy of the design master.

If the metadata folder is not specified (left blank), the aforementioned files are created in the specification folder.

To change the Metadata directory name highlight and edit the text box next to the setting.

Hide metadata directory

With this option checked the metadata directory will be hidden.

Embed Child Specifications

DriveWorks Projects (Not Excel Projects) that contain one or more Child specification controls can now have each child specification embedded within its parent.

This has numerous advantages:

  • An embedded specification is directly stored within its parent. They are not registered to the Group whatsoever. The only thing that knows about and controls the child specification is its parent specification.
  • Embedded specifications are assigned globally unique specification identifiers, so there will never be a conflict of specification identifiers.
  • Documents and reports will be registered against the “root” (topmost) specification. This is done because the root specification is the only one that will be visible to the outside world and to the group. Selecting the root specification in the specification explorer will show all child reports and documents.
  • This means all relative folder paths will be relative to the root specification too. This is, again, because documents are registered to the root specification.
  • Automatic states will not work on embedded child specifications, as Autopilot can not see the projects, but the topmost specification can still be put in an automatic state and released which will cause it and all of its children to release. Emails will work though, as they are registered against the root specification.
  • Copying a child specification will now also copy all its children. This is a direct benefit from having the child specifications stored in their parent. Move or copy the parent and you are moving or copying the children too. All children will be given new specification identifiers, as well.
  • Deleting a child specification will also delete its children too.
  • The setting for embedding child specifications is a project level setting. Meaning all child specification controls in the project will embed specifications. This is so the behaviour is the same across the specification. This is turned on by default for new projects.

Reporting Level

Minimal, Normal, Verbose

This sets the level of reporting for each Specification made.

There are three levels of reporting:

  • Minimal - Only specification errors will be reported.
  • Normal (Default)- Specification errors and any warnings will be reported.
  • Verbose - Specification errors, warnings and general information about the specification will be reported.
By default Normal level reporting will be applied.

Table of Contents