MyDriveWorks - Tech Tips
A way of completing a Child Specification, pulling data inputted in the Parent Specification, without needing to open the Child.
Projects are applied in the Child Specification List editor.
The Child Specification Lists reads information from the Projects that can be specified from it, you will see a helper link (see below) requesting a refresh of the information from the Projects. Click the helper link to refresh the information.
The project information cannot be accessed if it is open in another seat of DriveWorks Administrator.
To launch the Child Specification List Editor:
The Project Details tab allows the Projects that are to be specified from the child specification list control to be selected.
The filter box immediately above the Project Name and Constants list allow each to be filtered.
This is very useful if you have many Projects with many Constants.
Please see How To: Use Filters for more information.
The Project Details tab also allows information to be passed into Constants, in the Child Projects, from the Project the Child Specification List Control has been added to.
Once all Constants have been retrieved from the Child Project, rules can be built for the Constants created for information being passed from the Parent Project.
The filter box immediately above the Project Name and Constants list allow each to be filtered.
This is very useful if you have many Projects with many Constants.
Please see How To: Use Filters for more information.
The Result Columns tab allows you to add placeholders that will store information coming from the Child Project. These placeholders are added as columns to the Child Specification List Control. The Control includes three columns by default, which are:
The visibility of the Name, State and Type columns can be turned off in the (Name, State and Type) Column Visible property.
The Result Column Values tab is where the values in each Child Project, are matched to the Result Columns created.
Variables or Specification Properties in the Child Project are passed to the Child Specification List Control by this mechanism.
Embedded Child Specifications, which are only supported in DriveWorks Projects, can now be constantly synchronized with their Parent.
This means that any Constants being set by its Parent (via rules in the Parent) are updated instantly, regardless of how many levels deep the Child Specification is.
Earlier versions of DriveWorks required each Child Specification to be opened in turn to apply any updates, this happens because synchronized Child Specifications are opened when the Parent is opened.
With Embedded Child Specifications, the instant you open the Root Specification, all Child Specifications that are synchronized will be efficiently opened in the background as well.
The setting for this is at a Child Specification Control level, so on a list by list basis, you can say if the Child Specifications should synchronize all the time.
An example for the use of this is when a top level Project has a particular option that changes what Child Specifications do or return. Such as something that will change the total cost of the entire Specification. Normally, you would have to open each affected Child Specification so that the Constant values are sent into them.
With synchronized Embedded Child Specifications, this is now automatic.
When you enable synchronized Specifications, the Project Setting to enable embedded Specifications must also be enabled.
To enable embedded Child Specification:
See Project Settings for more information.
A way of completing a Child Specification, pulling data inputted in the Parent Specification, without needing to open the Child.
View all available MyDriveWorks Tech Tips.