Project Settings

The Project Settings contain information and settings for the project. Only users with Project Management rights may edit Project Settings.

Information

Name

The Name of the Project.

Created

The date the project was created.

Database Version

The version of Aligned Elements currently used.

Security

Password Expires After # Days

Defines when the password will expire due to password aging. The user must select a new password prior to expiration. Max length: 365 days. Default: 90 days.

Warn if Password Expires in # Days

Informs the user that the password is about to expire. Default: 10 days.

Allow Windows Logon

If selected, checks the login credentials against the current Active Directory. Not applicable for the Web Client.

Allow Automatic Change Comment

If selected, the value in the Automatic Change Comment will be automatically applied as Change Comment when saving an updated Document Object without displaying the Gap Form.

This option is active for all modification actions except when performing Update Multiple Items and is active for all users in the project.

Automatic Change Comment

The Automatic Change Comment applied as Change Comment if this feature is active.

Paths

Template Path

The path to the root folder of the project templates which defines the project configuration.

Storage Connection String (optional)

For distributed scenarios, it might make sense to place the templates somewhere outside the company network on a location that every project member can reach. To accommodate for such situations, Aligned Elements supports storing templates on an Azure File Storage in the Cloud.

To designate a location in an Azure File Storage, you need to supply two pieces of information:

1) The path to the templates on the form “\”

2) The Storage Connection String

Web Base URL

The prefix part of the URL to the project.

Smtp Mail Settings

Host

The smtp server address (e.g. smtp.gmail.com)

User

An email address that has an account on the server

Password

The password valid for the User above.

Sender

The name you want to appear as sender in the email.

Port

The port used (e.g. 465 for SSL).

Use SSL

Select if SSL shall be used.

Signature Preferences

Mode

ECertificate - For Digital Signatures. Users can only sign if a valid Electronic Certificate has been associated with the User (see User Management).

NoCertificate - No Electronic Certificate is required and thus an Electronic Signature (but no Digital Signature) is applied.

Start on Page

On which page to place the signature stamps relative to the “From”-setting.

From

• From Beginning

• From End

• Create Page From Beginning - an additional page is created for signature stamps

• Create Page From End - an additional page is created for signature stamps

Sign Direction

The direction in which subsequent signature stamps are placed on the page.

Start Position X - Start Position Y

The Lower Left X and Y position (in pixels) of the first signature stamp relative to the lower left corner of a document.

Width

The width of a signature stamp on the page (in pixels)

Height

The height of a signature stamp on the page (in pixels).

Gap

The horizontal and vertical gap between signature stamps (in pixels).

Add Document Info

Adds Aligned Elements information of the Document being signed to the signature page, includes:

• File Name

• File Object ID

• Signature Object ID

• Reason for signature (from Signature Object)

The Document Info is always placed 100px from the top of the page and 30px from the page left and right border, stretching across the page. The Document Info box height is 100px.

Document Info - Use Version

Optionally include the Aligned Elements File Version in the Document Info.

No Certificate - Use Location

For NoCertificate-Mode, optionally request and include Location information in the signature stamp.

No Certificate - Use Reason

For NoCertificate-Mode, optionally include Reason in each signature stamp.

No Certificate - Use Comment

For NoCertificate-Mode, optionally request and include Comment information in the signature stamp.

No Certificate - Use Time in Signature Stamp

For NoCertificate-Mode, optionally include Timestamp and Time zone in the signature stamp. Note that the Assigned Users Table Attribute in the Signature.rvt must contain a DateTimeColumn for this option to function properly.

Test Signature

Use the button to create a PDF page displaying the signature layout using the current settings.

Options

RPN Threshold

Displays the configured RPN threshold for the risk type.

Suspect Traces are only Cleared Manually

Overrides the default behaviour of automatic clearing of the suspect trace state when the child object in the suspect trace relationship is updated.

Automatically update linked traces to Latest Revision

Applies to traces between projects. Automatically updates traces between parent objects in other projects and modified child object when the child object is committed.

Note! A necessary prerequisite is that traces between parent and child objects are to latest revisions ("most current") before the modification takes place.

Visible DHF Columns

Defines the DHF columns displayed in the Word Output.

Project Phases

In order to compare the status of a concrete deliverable and the status that the QMS specifies for a certain Project Phase (i.e. DHF Index), Aligned Elements needs information about project phases (or milestones).

Add the names of the Project Phases according to your QMS and arrange the phases in sequence order. Select the name of the current Project Phase.

Note! Remember to update the selection of the current Project Phase as the project progresses.

Dynamic List Attributes

If Dynamic List Attributes are configured in the template set, they are listed in the left list, organized by Document Object Type Name. Additional selectable values in the Dynamic List Attribute can be added with carriage return-separated list in the text box displayed next to the Attribute Name. Add or remove items to adapt the list.

Note! A list of Dynamic List Attribute items may contain an empty string but may not include duplicates.

Note! Standard items for Dynamic List Attributes can be defined in the rvt-templates. These standard items are not displayed here.

Note! The Dynamic List Attribute can be configured in the rvt file to allow users to add new values on the fly in the Document Object form.

Project Type Name Mapping

Sometimes you want to re-use templates but with slight modifications. One way to accomplish this is to copy the template set and make the desired changes to the copied set. However, having several copies of a template set requires an additional management effort.

The settings below are stored in a dedicated xml file in the Template set, called ProjectMapping.xml.

Visible Type Names

Add Document Object Type names to this section for templates which has the property IsVisibleBook="false". They will for the current project be treated as IsVisibleBook="true".

Invisible Type Names

Add Document Object Type names to this section for templates which has the property IsVisibleBook="true". They will for the current project be treated as IsVisibleBook="false". Invisible Document Object Types exists in the project but are not visible to the user.

Excluded Type Names

Excluded templates, templates that are present in the Template directory but will not be considered for the current project.

Included Type Names

With this section feature, your template set can include several rvt-template files for the same type name, and by mapping a Type Names to a concrete rvt-file in the template set, the other rvt template with the same Type Name will not be loaded.

Applying a project specific Risk Calculation

The Type Name mapping can be used to e.g. override the Risk Calculation in a template set with a Risk Calculation that is specific for the project in question.

To achieve this effect for a Hazard Analysis.rvt, do as follows:

• Copy the Hazard Analysis.rvt file and add a prefix word to differentiate it from the original file, e.g. "HighRisk.Hazard Analysis.rvt"

• In the copied rvt file, add the following xml attribute to the TypeInfo tag: ExcludedByDefault="true"

• In the copied rvt file, modify the risk calculation as desired.

• Load the project with "Force Template Reload" checked.

• Navigate to Settings => Project Settings

• In the Type Name Mapping section, select Included Type Names and map the Document Object Type Name "Hazard Analysis" with the rvt-file "HighRisk.Hazard Analysis.rvt".

• Reload the project with "Force Template Reload" checked and verify that the calculation in "HighRisk.Hazard Analysis.rvt" is acutally used.

Export Project Settings

The Project Settings can be exported into an xml file and later imported into a different project. This is especially handy when distributing company-wide SMTP Settings and Signature Preferences.

In Project Settings, click Export to export the current project settings to an xml file.

Import Project Settings

When importing the exported Project Settings xml file in a different project, the following parameters are ignored:

• Project Name

• Project Creation Date

• Project Version

• Current Project Phase

• Any information about linked projects

Note! You can modify and trim the exported ml file to only contain the parameters you want to be imported. Since this feature can have significant consequences on your project, treat it with considerable consideration!