This topic introduces Cypress.Web and provides guidelines for planning the implementation of it in your environment.


These are development tools that enable you to customize Cypress for your site:

  • Cypress.Web allows users to search, retrieve, and view documents stored in the Cypress DocuVault, access their Inbox Viewer, and launch the Cypress client user interface from within their Web browser.
  • Cypress Server Pages (CSP) provides developers with the ability to implement server-side document query and retrieval. See the ASG-Cypress Server Pages Programmer’s topic for more information.
  • Content Processing Facility (CPF) enables you to create scripts to perform customized document processing, such as sorting and moving pages, adding bar codes, adding forms, and indexing documents. See the ASG-Cypress Content Processing Facility Reference topic for more information.

Cypress.Web provides an enterprise document portal that can be implemented in minutes and as a stand-alone solution. Cypress.Web makes documents and reports immediately, yet securely, accessible from any Web browser. It preserves document integrity by not converting documents to traditional Web formats. Cypress.Web does not require the installation of special viewing devices, eliminating the need for your organization to maintain a separate dedicated Web server. It also allows users to view or print a document that is exactly like the original.

Cypress.Web includes these components:

  • Cypress.Web Inbox
  • Cypress.Web Query
  • Cypress.Web CSP

Implementing Cypress.Web

ASG recommends that you perform these basic tasks for your implementation:

  • Define the scope of the implementation.
  • Identify the implementation team.
  • Determine the new Cypress.Web HTML pages to be created and identify the existing HTML pages into which to incorporate Cypress.Web.
  • Fully test Cypress.Web.
  • Launch Cypress.Web.

Defining the Scope of Your Cypress.Web Implementation

Identify your goals. A thorough understanding of your goals, and the goals of your user base, is required to identify the scope of the implementation project. Ask yourself these questions:

To what extent do you wish to empower your employees, partners, and customers? Do you want to provide Web access to Cypress Inboxes to all employees, generic document search and retrieval capabilities for customers and partners, and query capabilities tailored for specific departments and functions? Identify the business processes that can benefit from implementing Cypress.Web; then, survey users to determine specific needs and goals.

Do your users already have the required hardware and software to support Cypress.Web? Do all users use Windows? Are all systems equipped with Web browsers? Will you need to support virtually any client over the Internet? Survey the platforms and browser types users are currently using to determine what additional hardware and software, if any, is required to roll out Cypress.Web to your users.

What training, if any, is required? Are you providing employees with generic or high-level functionality that can be explained in a mass-distributed e-mail message or sophisticated DocuVault Query capability for specific departments? Although Cypress.Web is intuitive, the business processes being implemented might require end-user training. While you will not be able to identify training requirements at this stage, it is helpful to keep training requirements in mind throughout the implementation process, as the desire to minimize training might result in simplifying your design.

Identifying the Implementation Team

Because the functions Cypress.Web performs require that it be able to access several enterprise departments, it is critical that representatives from all affected organizations be involved in the implementation process. The simplest way to organize your team is to examine the path that information must travel from the source to an end user using Cypress.Web. Every organization that is responsible for a component of that path should have a representative on the implementation team. Additionally, you will want to include the managers and information officers responsible for overseeing and/or approving IT acquisitions.

At a minimum, your team should include personnel responsible for these job functions:

Data Center or Print Operations: The department responsible for generating output should be extensively involved in Cypress.Web implementation, as it is quite often the organization that realizes the most benefit from Cypress.Web.

Content Development: Content developers (e.g., application programmers, ERP application administrators, and CRM application administrators) should be aware of the upcoming Cypress.Web implementation, but need not be extensively involved. Whether to include or exclude content development organizations should be decided on a case-by-case basis.

Cypress Administration: The Cypress administrator is typically responsible for communicating the capabilities and requirements for a Cypress.Web implementation to all members of the team. Additionally, the administrator might need to configure and/or update Cypress objects and functions (e.g., Inboxes, subreports, and settings in the Address Book and the Administration Tools module) to enable Web document delivery.

Information Systems and Upper Management: These organizations should be represented to ensure that the vision of Web document delivery corresponds to management’s vision. Additionally, management support is often required to resolve issues that arise during the planning and implementation processes.

Network Operations: This organization plays an integral role in implementing Cypress.Web. It can assist in estimating Cypress’s impact on network bandwidth and granting access to specific HTML pages and server directories.

Web Administration: The Web group should be highly involved in the implementation process, as this organization typically creates the HTML pages that launch Cypress.Web and is responsible for opening access to Cypress.Web via the Web server. Because this organization’s personnel essentially implement Cypress.Web, they must be very familiar with Cypress.Web functions and design.

User Base: While a representative for the appropriate sectors of your user base should be interviewed extensively to identify required functions and operability, determine the need to add a user base representative to the team on a case-by-case basis. For example, if you are providing generic access to Inboxes, you may not need a representative on the team. If, however, you are implementing a detailed query structure tailored for specific business processes, you would benefit from the involvement of a user-base representative.

Determining Changes to Cypress.Web HTML Pages

After you have identified the collection of pages to be created, you can begin the development process. These are some suggestions before you begin to develop the pages:

Familiarize yourself with Cypress.Web operation, components, and design. Because Cypress.Web is more of a toolbox than an application, it can be implemented in many different ways. Thus, it will be helpful if you first understand all its functions and the opportunities it can create for your business. As you become more familiar with Cypress.Web, you will begin to discover new ways that it can be implemented. Additionally, you will need a thorough understanding of Cypress.Web to discuss and plan Cypress.Web applications with end users, department managers, application owners, and so on.
Ensure compliance with site design standards. In most cases, Cypress.Web is implemented within an existing portal strategy or Intranet/Internet framework. As such, you will most likely want those design standards reflected in your Cypress.Web pages.
Follow the planning process described in Implementing Cypress.Web topic. ASG strongly encourages you to consult the planning suggestions provided earlier in this topic. In addition to ensuring that end-user needs and expectations are met, these suggestions will ensure that all affected organizations are consulted prior to HTML page development.

See Managing Cypress.Web Pages for information on creating Cypress.Web pages.

Testing the Cypress.Web Implementation

If you are implementing Cypress.Web for the first time, you are no doubt aware of this critical step. If you are upgrading Cypress.Web, however, ASG recommends that you also fully test the updated implementation before using it in your production environment. To ensure a successful implementation, validate that all required functions are present and working properly by following your site’s process for introducing an new or upgraded application into your production environment.

Launching Cypress.Web

Launching Cypress.Web can be as simple as sending an e-mail message that directs a user to a specific URL. You can employ a variety of roll-out and announcement campaigns, but most customers create an announcement page that describes the new Cypress.Web features and general support information.