Versions Compared

Version Old Version 14 New Version Current
Changes made by

Ben Ha (Deactivated)

Ben Ha (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note
titleImportant:
  • If you are planning on upgrading from a previous version of DocRecord (prior to v5), please note the following:
    • The previous Web Client, which was based on Microsoft Silverlight, is no longer available and has been replaced with a new HTML5-based Web Client.
       
    • The Automation Server has been replaced with the Capture Server going forward in v5, but is still available (upon request) to allow for backward compatibility when upgrading from previous versions of DocRecord. Please note that v5 will be the last major version of DocRecord that supports the Automation Server. If you would like to convert your existing Automation Server configuration to use the Capture Server, please contact sales@prismsoftware.com for a professional services quote.
       
    • The Document Processing Server (DPS) has been replaced with the Workflow Server going forward in v5, but is still available (upon request) to allow for backward compatibility when upgrading from previous versions of DocRecord. Please note that v5 will be the last major version of DocRecord that supports DPS. If you would like to convert your existing DPS configuration to use the Workflow Server, please contact sales@prismsoftware.com for a professional services quote.
       
    • If you would like to request a download link for the Automation Server or DPS components, please contact support@prismsoftware.com and provide the current version and build number of DocRecord that you have installed.
       
    see the Upgrading from DocRecord 4.1 to DocRecord v5 article.

  • Otherwise, for a clean installation simply follow the instructions in the "DocRecord Installation Guide" PDF fileProcedure.

ENHANCEMENTS:

EFORMS

...

  • DocRecord now includes a fully integrated eForms solution, allowing users to electronically fill out an HTML web form or PDF form and submit it to DocRecord.  This completed form can then initiate a workflow process in DocRecord, allowing designated reviewers to approve the document for further processing.  Simple eForms may be designed over a web browser using the Quick Forms Designer, while more complex eForms may be designed using the eForm Designer application.  Once designed, these eForms can be published for use and will be available through a direct link or through the eForm Manager.
     
  • The eForms component is installed as part of the Workflow Server component.

  • To access the eForm Manager, please go to the following URL (where "SERVERNAME" represents the name or IP address of the server where the eForms component is installed).
    http://SERVERNAME/Prism/EForms/#/login 

WORKFLOW

...

  • In addition to the document-driven workflow available in the DocRecord Document Processing Server, user-driven workflow is now available through the DocRecord Workflow Server.  The Workflow Designer makes it simple to visually build a workflow process using its drag-and-drop interface, and the process can then be initiated automatically based off of specific events occurring in DocRecord.  Users will have a dedicated workflow queue, reflecting the tasks awaiting their attention.

...

  • The User Pool now features the ability to filter the user/group results from Active Directory (AD).  This makes it simple to locate a specific AD user or group by entering part of the username or group name, particularly in organizations with large AD environments.

  • The DocRecord Server Configuration screen ("Tools > Server Configuration") now features a "Search" tab, allowing the administrator to configure global search settings in DocRecord.  This includes the ability to define which type of keyword search is used for the Basic Keyword Search (e.g. "All of these words" instead of "Any of these words"), and defining a minimum relevance filter for full-text searches.

  • "USERNAMEBASE" has been added to the list of category tokens for the "Default" column,  "USERNAMEBASE" returns just the base username (e.g. "jdoe") while the existing "USER" token returns the fully qualified username (e.g. "jdoe@irvinedata.com").

OFFICE EXTENSION

  • DocRecord's integration with Microsoft Outlook has been expanded, allowing users to access documents in DocRecord directly from the Outlook interface.  Users may now browse the DocRecord folder structure, run searches, view documents, and handle workflow tasks without ever having to leave Outlook.  In addition, users may enable the "Send & Save" option to ensure that they are prompted to save all outgoing emails from Outlook into DocRecord.

  • DocRecord's integration with Microsoft Word has been expanded, allowing users to check-out documents in DocRecord directly from the Word interface.  In addition, users may now check-in a Word document directly from the Word interface, eliminating the need to switch between Microsoft Word and the DocRecord Desktop Client application.  Enhanced saving is now built into Word, ensuring that if the same document is submitted into DocRecord more than once, a new version of the document is created in DocRecord.

...

  • The server components of DocRecord are now native 64-bit applications and can only be installed on 64-bit Windows operating systems.  Please see the DocRecord Specifications (v5) page for details, including the list of supported operating systems.

  • Microsoft .NET Framework 4.6.1 is now required as a pre-requisite to installing DocRecord.  As a result, support for the Windows Vista and Windows Server 2008 operating systems have been dropped.  Please see the DocRecord Specifications (v5) page for details, including the list of supported operating systems.

  • DocRecord is now all-inclusive, meaning that most server and client components no longer need to be purchased separately and are included under the concurrent user licenses.  However, the DocRecord components requiring separate license keys still need to be licensed in the same way as with v4.

  •  The "Work In Process" system folder has been removed.  Going forward, the "Awaiting Commit" system folder shall be used as the default folder for all categories, including "[Unassigned]".

    Note: If you are upgrading from a previous version of DocRecord (prior to v5), the "Work In Process" folder will be moved automatically under "Awaiting Commit" as a subfolder.  If no documents are in the "Work In Process" folder, it may be safely deleted by the administrator.

  • Going forward with v5 builds, the properties of the Windows services for DocRecord will be maintained when upgrading to a new version.  This includes the service logon account information as well as the service startup type (previously this information would have to be re-entered after upgrading).

...