Manually Modifying the Plan Review Client Web.config File - Electronic Plan Review - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Electronic Plan Review

Platform
OnBase
Product
Electronic Plan Review
Release
Foundation 23.1
License
Standard
Essential
Premier

If necessary, the Plan Review Client web.config file can also be manually edited in a text editor, such as Notepad. The following options change the behavior of your Plan Review solution as described:

Option

Description

StyleSheetPath

The StyleSheetPath setting (<add key="StyleSheetPath" value="BasicBlue"/>) controls the appearance of the Plan Review web site. This value can be set to BasicBlue or BasicGreen.

By default, this setting is set to BasicBlue.

AllowSignon

The AllowSignon setting (<add key="AllowSignon" value="true"/>) is used in conjunction with Single Sign-On.

For more information on using Single Sign-On with Plan Review, contact your solution provider.

AllowSignoff

The AllowSignoff setting (<add key="AllowSignoff" value="true"/>) is used in conjunction with Single Sign-On.

For more information on using Single Sign-On with Plan Review, contact your solution provider.

DefaultTimeZone

The DefaultTimeZone setting (<add key="DefaultTimeZone" value="4"/>) controls the time zone that is used by default when a new user registers a Plan Review account.

The value used for this setting should correspond with a time zone from the default time zone table - for more details, see Default Time Zone Table.

By default, this setting is set to 4(Eastern Standard Time).

Note:

The name of the time zone displayed to the user may not exactly match the name of the time zone in the default time zone table, due to differences in hardware.

SearchStartYear

The SearchStartYear setting (<add key="SearchStartYear" value="2009"/>) controls the earliest year that can be searched for when purchasing documents.

DisplayDocumentsPerPage

The DisplayDocumentsPerPage setting (<add key="DisplayDocumentsPerPage" value="20"/>) controls the number of projects that are displayed on a user's Project list from the Plan Review site.

By default, this setting is set to 20.

ResetPasswordLinkExpiration

The ResetPasswordLinkExpiration setting (<add key="ResetPasswordLinkExpiration" value="60"/>) controls the amount of time it takes for a reset password hyperlink to expire. Once a hyperlink has expired, a user will be unable to use that hyperlink to reset his or her password.

This value is set in minutes. For example, if this value is set to 60, a user will be able to access his or her reset password hyperlink up to 60 minutes after clicking the Reset Password button. After 60 minutes have passed, the user will no longer be able to use that hyperlink to reset his or her password.

FileUploadDirectory

The FileUploadDirectory setting (<add key="FileUploadDirectory" value="C:\Inetpub\wwwroot\PlanReview\Temp\"/>) allows you to specify the directory used to temporarily store documents before they are imported into OnBase.

Note:

The application pool's identity account must have the following Windows permissions for the specified directory: Create, Delete, Read, and Write.

FileUploadValidator

The FileUploadValidator setting (<add key="FileUploadValidator" value="" />) allows you to specify a custom-built file validator that will be used to scan files uploaded through your Plan Review site. For example, you could use a file validator to scan uploaded files for viruses before they are imported into your OnBase system.

For more information on creating and configuring a file validator for use with your Plan Review site, please contact your solution provider.

TokenAuthentication

The TokenAuthentication setting (<add key="TokenAuthentication" value="false" />) allows you to enable or disable token authentication for your Plan Review solution. When this setting is set to true, users will be able to type a user's token into a Plan Review URL in order to access the data that would be displayed to that user.

For example, an administrator could enter a submitter user's token in order to ensure that a document has been correctly transferred from one Workflow queue to another, or to ensure that a project invitation was sent to the correct user account. Tokens are added at the end of the URL, as in the following example:

http://[APPSERVER]/PlanReview/Plan?token=[TOKEN]

CAPTCHAPublicKey

You can add the CAPTCHAPublicKey setting (<add key="CAPTCHAPublicKey" value=""/>) in order to require new users to answer a CAPTCHA before registering a Plan Review user account. Set the value of this setting equal to a public CAPTCHA key.

If this value is left blank, users will not have to answer a CAPTCHA to register an account.

Note:

CAPTCHAs are not supported for use with Microsoft Internet Explorer 7.

CAPTCHAPrivateKey

You can add the CAPTCHAPrivateKey setting (<add key="CAPTCHAPrivateKey" value=""/>) in order to require new users to answer a CAPTCHA before registering a Plan Review user account. Set the value of this setting equal to a private CAPTCHA key.

If this value is left blank, users will not have to answer a CAPTCHA to register an account.

Note:

CAPTCHAs are not supported for use with Microsoft Internet Explorer 7.

PasswordStrengthPattern

The PasswordStrengthPattern setting (<add key="PasswordStrengthPattern" value="^(?=.{4,}).*$"/>) allows you to specify regular expressions to limit the type of passwords that users can configure when registering a new account.

For example, the default value of ^(?=.{4,}).*$ forces users to configure a password that is at least 4 characters long.

For more information on regular expressions, see http://msdn.microsoft.com/en-us/library/hs600312.aspx.

PasswordStrengthMessage

The PasswordStrengthMessage setting (<add key="PasswordStrengthMessage" value="Password must contain at least 4 characters"/>) allows you to specify a message to be displayed to users who attempt to configure a password that does not meet your PasswordStrengthPattern criteria.

DisciplineItemsPerMenu

The DisciplineItemsPerMenu setting (<add key="DisciplineItemsPerMenu" value="15"/>) allows you to specify the maximum number of disciplines that will be displayed in the Disciplines menu.

For example, if DisciplineItemsPerMenu is set to 15, only the first 15 disciplines will be displayed in the disciplines menu. Additional disciplines will be displayed by selecting More from the Disciplines menu.

SessionUser

The SessionUser setting (<add key="SessionUser" value="MANAGER" />) allows you to specify the OnBase user account that is used to determine the Disciplines and Sheet Types that can be used by Electronic Plan Review web users. Specify the user name of your Electronic Plan Review Administrator account to give web users access to all available Disciplines and Sheet Types.

For example:

<add key="SessionUser" value="JOHNADAMS" />

In this example, all users who log on to the Electronic Plan Review website are able to submit documents using any Disciplines or Sheet Types that can be accessed by the OnBase user JohnAdams.

SessionPassword

The SessionPassword setting (<add key="SessionPassword" value="PASSWORD" />) allows you to set the value of the password for the user account you specified as your SessionUser.

DataSource

The DataSource setting (<add key="DataSource" value="[dmsdatasource]" />) allows you to set the value of your OnBase data source.

maxRequestLength

The maxRequestLength setting (<httpRuntime maxRequestLength="4096"/>) is located in the system.web node, and (in conjunction with the maxAllowedContentLength setting) controls the size of documents that can be uploaded through the Plan Review site. The maxRequestLength setting must be set to the same value as the maxAllowedContentLength setting.

maxAllowedContentLength

The maxAllowedContentLength setting (<add key="maxAllowedContentLength" value="30000000"/>) is located in the system.webServer node, and (in conjunction with the maxRequestLength setting), controls the size of documents that can be uploaded through the Plan Review site.

The maxAllowedContentLength setting must be set to the same value as the maxRequestLength setting.

Note:

You must set the Application Server's maxAllowedContentLength setting to the same value used by the maxAllowedContentLength setting in your Plan Review web.config file.