Related Information Examples & Tutorials
Do you need a special functionality, process automation or report? Check out the Collect! customization services. Available to all but rates are discounted for Members. Membership has it's perks!
“ You and your staff have made the conversion much easier than expected. ” Paul S.

Modifying Web Host Message HTML Pages

When using Web Host, there are several instances when a default message page is displayed to the end user. For example, a default page is returned after successful data submission. A "Too many users" message is returned when the number of users exceeds the Collect! licensed users. Also, several HTPP Errors are handled by Web Host and might return a message to the end user. These are HTTP Errors 403, 404, 501 and 505.

You can modify any of the default pages with your own custom messages and Collect! will use your page to override the defaults shipped with Web Host. One very useful application of this would be to redirect your users to another site or page.

tip.gif To use your own messages, it is necessary only to use the correct name for each page and to place your HTML files in the correct database "html" folder.

tip.gif Web Host override HTML files should be placed in the {database}\html\global folder.

Example: C:\CV11\demodb\html\global\notfound.html

Submission Received HTML Page

Whenever an end user successfully submits data to Collect! through the Web Host, a "Submission Received" summary page is displayed. To override the default format of this page, you need to create two HTML pages, one for the header, submitheader.html and one for the footer, submitfooter.html. Place these pages in the the {database}\html\global folder.

Example: C:\CV11\demodb\html\global\submitheader.html
Example: C:\CV11\demodb\html\global\submitfooter.html

The Web Host content with be displayed as HTML tables in between these two files. Both files need to exist and successfully load in order for an override to take effect.

Top of page.

Too Many Users Message

Web Host returns the "Too many users" message when a user's attempt to sign on to Web Host results in too many users connected. This means that the number of connected users exceeds the number of Collect! licensed users. To override the default message that the end user sees, create an HTML page named toomanyusers.html and place it in the database\html\global folder.

Example: C:\CV11\demodb\html\global\toomanyusers.html

Top of page.

Web Host Http Errors

Web Host returns error messages for HTTP Errors 403, 404, 501 and 505. We will now discuss what these messages mean to the Web Host user and the names of the pages you can create to override each default message page.

authfailed.html - HTTP Error 403
notfound.html - HTTP Error 404
notimplemented.html - HTTP Error 501
badversion.html - HTTP Error 505

tip.gif All Web Host 400 and 500 series errors are logged to the Collect! Application Log. Select the Web Host option to view any 400 or 500 series errors encountered by the users of the Web Host.

Top of page.

Http Error 403

The HTTP Error 403 message is returned to the end user when they are not authorized to view the requested page. When a user first goes to the Web Host sign on page and attempts to sign in, Web Host intercepts a 403 error and pops up the Sign On dialog. You can put your own page into the Web Host to override the default 403, but end users would probably not see this page ordinarily. To override the default 403 page, create an HTML page named authfailed.html and place it in the database\html\global folder.

Example: C:\CV11\demodb\html\global\authfailed.html

Top of page.

Http Error 404

The HTTP Error 404 message is returned to the end user when the requested page was not found. To override the default message that the end user sees, create an HTML page named notfound.html and place it in the database\html\global folder.

Example: C:\CV11\demodb\html\global\notfound.html

tip.gif Perhaps you might want to redirect your users to another site or another page when they get this error.

Top of page.

Http Error 501

The HTTP Error 501 message is returned to the end user when the requested feature has not been implemented. This error may occur if someone tries to send commands to the Web Host that are not implemented in the Web Host functionality. To override the default message that the end user sees, create an HTML page named notimplemented.html and place it in the database\html\global folder.

Example: C:\CV11\demodb\html\global\notimplemented.html

tip.gif Perhaps you might want to redirect your users to another site or another page when they get this error.

Top of page.

Http Error 505

The HTTP Error 505 message is returned to the end user when the requested page cannot be displayed because the user is attempting to open the Web Host using an unsupported browser. To override the default message that the end user sees, create an HTML page named badversion.html and place it in the database\html\global folder.

Example: C:\CV11\demodb\html\global\badversion.html

tip.gif Perhaps you might want to redirect your users to another site or another page when they get this error.

Top of page.

Summary

When using Web Host, there are several instances when a default message page is displayed to the end user. A default page is returned after successful data submission and also when too many users attempt to sign into the Web Host. Several 400 and 500 series errors are recognized by the Web Host and messages may be returned to the end user.

You can modify any of these message pages with your own custom messages and Collect! will use your page to override the defaults shipped with Web Host. One use for this may be to redirect your users to another site or another page.

To use your own messages, it is necessary only to use the correct name for each page and to place your HTML files in the correct database html folder.

tip.gif Web Host override HTML files should be placed in the {database}\html\global folder.

Top of page.

See Also

- Web Host Topics

Top of page.

Setting Up Client Access

Currently, Web Host supports two user setups for Client access. These are Single Client Access and Client Group Access. Collect! will use the settings from these configurations when evaluating Web Host signons.

Only these valid types will be considered "unlimited" for web access:

Single Client Access

1. Operator Type is set to "Client."

2. Operator Client # is set to a valid current Client in the Collect! database.

tip.gif If you leave the Client # blank, Collect! will not allow the Client operator to sign into Web Host.

3. Operator User Level is set to "98."

When these three conditions are met for a single client signing into the Web Host, this user will not be subject to the licensing limits.

Client Group Access

1. Operator Type is set to " Collector."

2. Operator Title must have a "Client Group ID."

tip.gif This Group ID is a value stored in the User 1 field of one or several Clients. Please refer to Help topic, How To Add a User to Web Host for details.

3. Operator User Level is set to "97."

When these three conditions are met for a client group signing into the Web Host, this user will not be subject to the licensing limits.

Top of page.

Summary

When the conditions for unlimited client access are met, as described above, any client who signs in to Web Host is not counted. If any of the conditions are not met, the user is counted in the normal licensing limits.

Top of page.

See Also

- Web Host Topics

Top of page.

Was this page helpful? Do you have any comments on this document? Can we make it better? If so how may we improve this page.

Please click this link to send us your comments: helpinfo@collect.org

Collection Advisor Veracode Verified RMA ACA Member