8/5/2023 0 Comments Redacted stamp png![]() The document information is passed on the request, so that the service has access to all of those details. Whenever a Daeja Viewer is launched, a request is made to one of these services, depending on the repository where the document is stored. In ICN 2.0.3.3, a new set of services are introduced “per-platform”: This article describes this new ViewONE Bootstrap service, and provides a basic sample plugin that can be used as a starter for developing a variety of customizations to viewer configuration and behavior. So, as of ICN 2.0.3.3, a new set of services are provided, that allow context-specific customization of both Pro and Virtual launch via ICN plugin.įor sites that had been maintaining custom viewer launch scripts, this is the recommended way forward. The good news is that with ICN 2.0.3, internal requirements obviated the need to provide a generalized, extensible Daeja ViewONE Pro/Virtual startup customization capability. Also, there is no script available that allows for customization of the startup of ViewONE Virtual. With ICN 2.0.3, many sites are discovering that their scripted customizations to viewer launch in ICN 2.0.2 and earlier no longer work. Which leads us to the purpose of this article. ![]() Moreover, the scripts that launch Daeja ViewONE Pro, and Daeja ViewONE Virtual are heavily modified from prior releases, in order to load ICN admin-stored configuration on viewer startup. The first time these settings are modified and/or saved in the ICN admin database, the filenetViewer_properties.jsp file is never used again. Some basic upgrade support is provided in ICN 2.0.3 that reads the filenetViewer_properties.jsp, and initializes default settings in ICN admin, based on the values found there. In ICN 2.0.3, all of the configuration of Daeja ViewONE Pro (called FileNet Viewer in earlier releases), the new Daeja ViewONE Virtual, and the related streaming and redaction services have been moved into the ICN admin interface. One of the more common cases for this is to disable annotation support for certain classes of documents, or for certain groups of users. Sites have gone this route in order to provide more granular, and context-specific customization to startup parameters. Upgrade installations to ICN do not overwrite this file.Īs it turns out, there are sites that have gone to customizing the viewer startup scripts around filenetViewer_properties.jsp anyway. The intent, in ICN, with filenetViewer_properties.jsp was to provide for customization without the need to maintain code through updates. In the past, in P8 Workplace and P8 Workplace XT, customization was done in the actual JSP that launched the viewer, and once those changes were made, the site had to maintain that code through upgrades. This was provided to allow sites the ability to customize viewer startup parameters. In ICN 2.0.2 and earlier releases, an upgrade-supported configuration file was provided for Daeja Viewer configuration (navigator.war/applets/filenetViewer_properties.jsp). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |