Installing Aligned Elements Web Server
  • Elements SPA Installation
  • Preparing the Windows Server
    • Before you get started
    • Install and Configure SQL Server for Aligned Elements
    • Install .NET 4.8
    • Install/Activate the IIS
    • Enable ASP.NET 4.5/4.6/4.7
    • Optional: IIS Always running part 1
    • Installing Web Platform Installer and Web deploy
    • Install URL Rewrite Module
    • Install IIS Crypto to disable Weak Ciphers and Protocols
  • Deploying the Aligned Elements Web Solution
    • Install the Aligned Elements Web Server Package
    • Setting HTTP Strict Transport Security (HSTS)
    • Optional: Open Ports in the Network on Azure hosted Virtual Machines
    • Optional: Get a SSL certificate from Let’s Encrypt
    • Binding your SSL certificate to the Aligned Elements web site
    • Creating the „Temp“ and „Files“ directories
    • Remove stdole.dll from bin directory
    • Move ElementsSPA.xml from the "App_Data" folder to the "bin" folder
    • Add the Aligned Elements License Files
    • Set the necessary security permissions for directories
    • Optional: IIS Always running part 2
    • Install necessary Unicode Font
    • Install and Configure File Server Resource Manager
  • Configure Application Options in web.config
    • Configure Application Options in web.config
    • Set the Server and connection string
    • Always Require SSL
    • Referring to the Project Templates
    • Email Configuration
    • Word Add-in Configuration and deployment
      • Distribute an Add-in using the Office 365 admin center
      • Distribute the Add-in using sideloading for Windows
      • Distribute the Add-in using sideloading for Mac
    • Optional: Integration of the Aligned Elements Automation Tool
      • Importing Dashboards with Rename using the Automation Script
    • Optional: Enabling Active Directory Integration
  • Optional: Configuration of AI Features
  • Optional: Enable editing of Configuration Sections from the UI
  • Create an Initial User
    • Option 1: Aligned Elements Projects already exist
    • Option 2: New Web server, no Aligned Elements Projects exist
  • Upgrading the Aligned Elements Web Server
    • Upgrading a Server
  • Troubleshooting
    • Generic Server Error
    • Missing version of stdole.dll
    • Missing Dependencies for Txic.dll
    • Error shown: Could not load file or assembly “System.Net.Http”
    • 500 Internal Server Error
    • Error when trying to start application
    • The server is not starting after upgrading to v2.5 SP 4 Part 1
    • The server is not starting after upgrading to v2.5 SP 4 Part II
    • Load a project works but when clicking on a design Item, you are re-directed to the login
    • The application cannot connect to the license server
    • The urls in email notifications are incorrect/missing port information
    • Missing Font
    • Mismatch of server name between Windows-client and Web.
  • Cannot upload Templates
  • Running 'ElementsSPAPackage.deploy.cmd' closes the Command-Prompt window
  • Web.config Settings
    • Settings of the Web.config
  • Configuring Aligned Elements
    • Introduction to rvt templates
    • Type Info Element
    • Compulsory Trace Holders Element
  • Attributes Element
    • String Attribute
    • Enum Attribute
    • Rich Text Attribute
    • Dynamic List Attribute
    • Multiselect Attribute
    • Enum User Attribute
    • Date Time Attribute
    • Boolean Attribute (Checkbox)
    • Int Attribute
    • Double Attribute
    • Int Range Attribute
    • File Attribute
    • Table Attribute
    • Traced Objects Attribute
    • Approval Attribute
  • Trace Holders Element
  • Positive Cues Element
  • Validation Rules Element
    • Traced To Rule
    • Traced From Rule
    • Illegal Trace To Rule
    • Illegal Trace From Rule
    • Obsolete Linked Trace Rule
    • Suspect Trace Rule
    • Missing Execution In TestRun Rule
    • Incoming Suspect Trace Rule
    • Object In File Rule
    • Objects In File Up To Date Rule
    • Not Reviewed Rule
    • Object In Completed Signature Rule
    • Has Open Issue Rule
    • Related Attribute Value Rule
    • Date Overdue Rule
    • Executed From Last Revision Rule
    • Signature Missing Rule
    • Linked Attribute Value Rule
    • Objects In File Not Reviewed Rule
  • Attribute Workflows
    • Sign Action
    • Email Action
    • Set Attribute Action
    • Copy File Action
    • Lock Action
    • Unlock Action
    • Generate Object Action
    • Add PDF Footer
Powered by GitBook
On this page
  • ReviewTypeName (Required)
  • ConsistentIfReviewOpen (Optional, Default: true)

Was this helpful?

  1. Validation Rules Element

Not Reviewed Rule

This validation rule checks whether the current revision of a Document Object is part of a completed (Review Status set to 'Closed') Reviews.

If the current a Document Object is not part of a completed Review, an inconsistency is displayed.

<NotReviewedRule ReviewTypeName="Review"/>

ReviewTypeName (Required)

The type name of the Review Document Object. Must be 'Review'.

ConsistentIfReviewOpen (Optional, Default: true)

If this xml attribute is set to true and the Document Object is added to a Review that has been started (not disabled) but not finalized (Review Status set to 'Closed'), the current Document Object is considered to be reviewed, and no inconsistency is displayed.

If this xml attribute is set to false and the Document Object is member of a Review, that has been started (not disabled) but not finalized (Review Status set to 'Closed'), the current Document Object is NOT considered to be reviewed, and an inconsistency is displayed.

PreviousObjects In File Up To Date RuleNextObject In Completed Signature Rule

Last updated 4 days ago

Was this helpful?