saperion version 7.5 service pack 4 patch level update patch level (r90363) - september 10, 2015 6...

Saperion Version 7.5 Service Pack 4 Patch Level

Update

Copyright © 2015 Lexmark International Technology, S.A. All rights reserved.

Lexmark is a trademark of Lexmark International, Inc., registered in the U.S. and/or other countries. All other trademarksare the property of their respective owners.. No part of this publication may be reproduced, stored, or transmitted in anyform without the prior written permission of Lexmark.

2.1 Saperion ECM

1

Saperion Version 7.5 Service Pack 4

Patch Level Update

1 Introduction

This document lists all bug fixes included in the Patch Level for the Service Pack 4 release for Saperion

v. 7.5. Bugs are listed by Patch Level number, then by product area and finally by bug number.

Refer to the documentation and the Best Practice guides in the Saperion documentation portal for more

details regarding each feature. In addition, refer to the current technical specifications at the following

URL for useful information regarding the system.

http://portal.saperion.com/docsxml/downloads/Saperion_Technical_Specifications_75SP4.pdf

2 Important Notes Regarding Patch Level

Installations

2.1 Saperion ECM

Before adding/copying the *scr-businessruleserver, scr-classicconnector, scr-fileplanconverter und

scr-javacoreserver* LIB directories from the patch level, the existing LIB directories must be deleted.

(Be careful with custom JARs when deleting LIB directories). You must also copy the Java Core Server

startup files or merge any changes from customized startup files (start_java_core_server.bat and

start_java_core_server_debug.bat <Install path> scr\scr-javacoreserver\scripts\windows directory).

2.2 Saperion Integration Server

Beginning with Saperion version 7.5.2 Patch Level 1, the Saperion Integration Server requires a manual

update in order to work with Saperion patch-level versions.

Before updating, make sure the Integration Server is shut down. To perform the update, replace the

following Classic Connector program files in the Integration Server library path.

+ authentication-core-7.5.4.jar

+ authentication-keys-7.5.4.jar

+ authentication-otp-7.5.4.jar

+ render-engines-core-2.0.1.jar

+ sacache-2.1.0.jar

+ saperion-common-lang-1.2.0.jar

3 Patch Level (r90363) - September 10, 2015

2

+ scr-classicconnector-7.5.4.jar

+ scr-common-7.5.4.jar

+ scr-connector-7.5.4.jar

The Integration Server library path is:

+ [drive:]\{integration_server_install_path}\jboss\standalone\deployments\sis-server-ear.ear\lib

The Classic Connector program files are contained in the current patch-level distribution.

+ {saperion_7.5.4_patchlevel}\scr\scr-classicconnector\lib

i After the patch is installed, make sure that no duplicate JAR names with different versions exist.

If duplicates exist, delete the JAR with the old version in favor of the new one.


3.1 Supported Java version

The current patch level includes basic testing with Java version 8 update 51.

i We recommend against updating to Java version 8 update 60, due to incompatibility between the

Internet Explorer Java plug-in and the Web Client.

For the Java version with which Saperion 7.5 SP4 was tested for full compatibility, refer to the

corresponding technical specifications.

3.2 RICH CLIENT

3.2.1 DE39393: Not possible to save images rotated in tray

It was possible to rotate documents while still in the tray, but clicking SAVE did not save the change.

3.2.2 DE40124: Multi-format viewer in index form caused archiving

rollback

Archiving of a structure is rolled back when the multi-format viewer is part of the index form.

3.2 RICH CLIENT

3

3.2.2.1 Steps to reproduce

1. Create a structure that contains at least two PDF documents and a document of some

other format.

2. Drag the structure to an application which is linked with an index form that uses the

multi-format viewer (PDF).

3. Enter index data and confirm with OK or Save.

Result: The structure is not archived, and you get the following notice from the broker:

FinishTransaction: Rollback transaction [CSM-VM-01.0000091C,DE070A001C0013]=Ok :

rollback successful

3.2.3 DE42318: Saperion splash screen overlaps all other windows

Saperion Rich Client splash screen overlaps all other windows and does not show a wait cursor.


1. Start the Saperion Rich Client.

Result: When the start was slow, there was no wait cursor to let the user know that Saperion

was still active. Also, the splash screen overlapped all other windows, and could not be

minimized or hidden.

3.2.4 DE42572: Annotation feature inactive on rendered PDF in

index form

When an index form was opened by dragging a PDF document from the tray to the file application, the

annotations feature in the integrated viewer was inactive.

3.2.5 DE45842: Error when moving documents from document tray

to input or open tray

When a document was moved from the document tray to the input or open tray, an error message

appeared.

3.2.6 DE46318: Oracle: Query on root layer of an e-file didn't list

documents

In Oracle, when a query was run at the root level of an eFile, documents in a register with an umlaut

in its name were not shown.

To fix this, the following parameter must be set in the archief.ini file.


4

[ODBC.Setup32.<Datasource>]

ODBCUpperChar==

3.3 WEB CLIENT

3.3.1 #34879: Unique field condition was ignored during archiving

With a DDC with a unique field, when a document was archived twice with the same index values, no

error message or other information was shown.

3.3.2 DE40551: Web Client server script didn't work with client

EventScript

When you create an OnItemDrag event, the result list server script for the Web Client doesn't work.


1. Create a server script for the Web Client that creates a menu.

2. Test the script in the Web Client.

Result: Works.

3. Add an OnItemDrag event to the form for the result list.

Result: Menu is no longer shown in the Web Client. To reproduce the bug again, restart

the server.

3.3.3 DE43849: Cancel and... button did not work

The “Cancel and…” button was not working.

3.3.4 DE46788: It was possible to open index form for locked

document

Users were able to open the index form for a locked document, but were not able to save any changes.

The error message appeared behind the index form. This has been fixed so that for locked documents,

the error message appears and the index form does not open.

3.4 WORKFLOW

5

3.4 WORKFLOW

3.4.1 DE40135: Problem when reassigning workflow to receiver

When a workflow was forwarded to a role assigned to only one substitute, and the substitute selected

“Reassign to receiver” before the original receiver was back, the workflow stayed with the substitute role,

and was not forwarded to the actual substitute.

3.4.2 DE40448: Workflow ended with error when invalid user in API

When an invalid user is entered for Activity_GetUser, the workflow ends with an error, and there's no

entry in the XFDOCVECTOR for the DFUID from the document.


1. Create a simple workflow, with Start, User Task and End.

2. In the User Task, add a user selection per macro.

3. Create a simple macro GetUser ("<username>") which returns a nonexistent user.

4. Run the workflow.

Result: An "Invalid User" error appears and the workflow locks. There's no entry in the

XFDOCVECTOR for the DFUID from the document.

3.5 SAP

3.5.1 #50409: The convert tool for R/Link certificates was improved

The maxusersize and maxinisize were increased to improve performance.

3.5.2 DE40712: Wrong file extension when downloading with SAP

Web Viewer

When a PDF watermark was applied to a TIFF file archived in R/Link, and then downloaded with the SAP

Web Viewer, the .tif file extension was appended to the file, instead of .pdf.


1. Archive a TIFF document via R/Link.

2. Add a PDF watermark to it.

3. Display the file in the SAP Web Viewer and then download it.


6

Result: The .tif file extension was appended to the downloaded file, instead of .pdf.

3.5.3 DE45167: SAP Web Viewer enlarged SAPNote window to full

screen

In the SAP Web Viewer, when the text field for the SAP Notes was clicked, the text field enlarged to fill

the screen. This has been fixed so that the text field stays at its normal size.

3.5.4 DE47165: Sending mails from SAP Viewer failed with

LiveConnect call

It was not possible to send email from the SAP viewer, due to a failed LiveConnect call.

3.5.5 US75225: Concurrent access in R/Link improvement

Synchronization performance was improved for concurrent access.

3.6 API - COM/UBI

3.6.1 DE46852: oUtil.Replace caused memory overrun

When using iUtility.Replace, if the “new” parameter was longer than the “old” parameter, the target string

was not long enough and this resulted in a memory overrun.

3.6.2 US71395: It is now possible to select multiple rows with

iMask.SelectDocByUid

You can now use the iMask.SelectDocByUid method to pass multiple UIDs. Use semicolons ( ; ) to

separate each UID. For more information, refer to the Saperion documentation.

3.7 CORE SERVER

3.7.1 DE40114: Problems when correcting incorrect database

entries

Changes were made to make it possible to update index data via the database.


7

4 Patch Level (r89921) - August 10, 2015


The current patch level includes basic testing with version 8 update 51 of Java, the latest version available

when testing started. For the Java version with which Saperion 7.5 SP4 was tested for full compatibility,

refer to the corresponding technical specifications.

4.2 RICH CLIENT

4.2.1 DE39587: ENTER key didn't begin search

In some circumstances, pressing the ENTER key did not begin a search.


1. Open two query forms (non-embedded).

2. In the first form, open a document for indexing.

3. In the second form, enter a search criterion and click ENTER.

Result: A line break was added in the search field, instead of the search being carried out.

4.2.1.2 New "ModalIndex" parameter

To prevent the above error, you can now open index forms modelessly by setting the "ModalIndex"

parameter in the program.ini file in the [Setup] section. The default setting is TRUE (modal).

Example

[Setup]

ModalIndex=TRUE

4.2.2 DE40342: Editing the module user settings in the EventScript

window resulted in logout

When the module user settings were edited in the EventScript window, and the window was then closed,

the user was logged out and had to log in again.


8


1. Open the EventScript window "Scripts..." and select a script.

2. Click the [Module...] button.

3. Edit something (or not) and click [OK].

4. Close the EventScript window.

Result: You are logged out.

4.2.3 DE40446: Wrong [WindowPositions] entry caused query form

problem

A wrong entry for the query form appeared in the [WindowPositions] section in the user-specific

archief.ini, and caused the form to open only as a diminished box.


1. To mimic the error, in the archief.ini of your test user, make an entry such as the following:

[WindowPositions]

Query-Querymaskenname=1

2. Log in as the user, and open the query form in the client.

Result: The form appeared as a small box.

4.2.4 DE40824: Embedded viewer ignored compression setting

when saving file

When a document was saved from inside the structure window in the embedded viewer, the viewer

prompted to save without compression. Even when the PicCompression parameter was set to 1 in the

user archief.ini, this setting was ignored.

4.2.5 DE41404: Cursor didn't appear in text field in index form

when "Display for Indexing" was selected

When "Display for Indexing" was selected in the System Configuration dialog box, the cursor didn't

appear in the text field in the index form. When the option was deselected, the cursor behaved as

expected.


1. In Saperion, in the "System Configuration" dialog box, select "Display for indexing."

4.2 RICH CLIENT

9

2. Drag a document from the document tray to an application.

Result: The index form opened but the cursor was not placed in any text field.

4.2.6 DE41906: Drag & drop in eFile handling caused unintended

multiselect actions

When selecting multiple documents in an eFile application for dragging, additional documents were

included in the selection and dragged to the new location as well. In addtion, the selection in the results

list expanded.


1. Add various documents to a register.

2. Open the register in an eFile application.

3. Open a results list and click the mouse to select a document, but don’t let go of the mouse

key. Drag the document.

Result: Multiple documents were selected.

4.2.7 DE42755: Fulltext index field of text retrieval/retrieval Unicode

showed no results after editing application file

After editing an archived document (application file) in a result list in a query form in the Rich Client,

the fulltext or fulltext Unicode fields were no longer filled.


1. Create a DDC with fulltext and fulltext Unicode index fields.

2. Create an application with an index and a query form for the Rich Client.

3. Activate the fulltext property in the ODBC database source in the Saperion MMC.

4. Edit the index form again, by defining filetext for the two fulltext fields.

5. Edit the query form again, by adding the fulltext fields.

6. Restart the Saperion server.

7. Archive a PDF or text file in the application, and close the dialog box that opens.


10

Result: The fulltext fields in the result list were empty. This didn't happen with image files.

4.2.8 DE45668: Selecting documents in results list did not work as

expected

When a document was selected in the results list using Shift+ or Ctrl+ right mouse button, all documents

above the selected one were also selected when dragging the mouse up and to the left.

4.2.9 DE45707: Window position was lost for index forms

Every time the same index form was reloaded, it appeared in a new position. The window position was not

being saved. This has been fixed so that the index form appears in the previous position when reloaded.

4.2.10DE45981: Not possible to sort embedded result list with

macro data source

It was not possible to sort an embedded results list when the data source was a macro. This has been

fixed so that Saperion can now return the query string instead of the cursor object, thus allowing the

results list to be sorted by the user at runtime.

4.3 WEB CLIENT

4.3.1 DE42594: Field validation failed for empty multi-select lookup

table fields

The field validation for multi-select lookup fields failed when the entry was deleted and the field was

called up.

4.4 API - COM/UBI

4.4.1 DE44719: (Classic Connector) Evaluation of ACLs did not work

The Classic Connector ignored ACLs set on users, groups and roles. This has been fixed.

4.4.2 DE45934: (Classic Connector) Wrong return code logged in

core server log

A wrong return code was being logged in the core server log.

4.5 CORE SERVER

11

4.4.3 DE45966: The iUtility.Replace method sometimes led to a

memory error

In some cases, using the iUtility.Replace method led to a memory leak which resulted in a client crash.

The leak has been fixed.

4.4.4 US77873: New property "iPage.PageNo" returns current page

number for TIFF images

A new property, "iPage.PageNo" has been added. It returns the page number of the page being displayed

in the viewer object.

The following sample macro displays the current page number and executes the "Next Page" command.

Sub GetPageObject()

Dim viewer As Object

For Each viewer In Mask.controls()

'msgbox liste.name

If viewer.type = 13 Then ' type 13 is viewer

MsgBox viewer.page.document.PageNo

viewer.page.execute 2010

End If

Next

End Sub

4.5 CORE SERVER

4.5.1 DE45267: Starting the MMC wrote "unsupported error 67" in

core server log

Starting the MMC resulted in an “unsupported error 67” being written to the core, client and MMC logs.

The core server log was locked. For the core server to log again, a new log file was created.

4.5.2 DE45789: Permanent denial of service if network not available

for some time

In some circumstances, after a network error, the Saperion core server was unable to reconnect, and a

permanent error was logged.


12

4.5.3 DE46029: Denial of service after unhandled exception at

Event#142

A denial of service after an unhandled exception in the Java Core Server has been fixed.

4.5.4 DE46103: COLD transfer hung as a task in the MMC

When doing a COLD transfer with the MMC, the task would hang, and the DRD file was logged as invalid.

4.6 WORKFLOW

4.6.1 DE41640: "Several recipients" option was grayed-out in

Workflow designer

To address multiple users in a workflow using a macro, you must activate the "several recipients" option.

However, since this option was grayed-out in the workflow designer when a receiver macro was selected,

the option was easily overlooked.


1. In the Rich Client, create a workflow and create a new user task.

2. In the "Workflow user task" dialog box, click Next.

3. Select the "Selection macro" and select a macro (or not).

Result: In the "Workflow user task" dialog box, in the "Receiver Options" area, the "several

recipients" options were grayed-out.

4.7 SAP

4.7.1 DE39245: Jadice Web Viewer displayed text on colored

background in poor quality

When Jadice Web Viewer displayed text on a non-white background, the text appeared in poor quality

and was not readable.

4.7.2 DE40353: Jadice Web Viewer print single page / last page did

not work

In the Jadice Web Viewer, single documents were not printed, while in documents with multiple pages,

the last page was not printed.

5.1 API - COM/UBI

13

5 Patch Level (r89462) - July 10, 2015

5.1 API - COM/UBI

5.1.1 DE41857: (UBI) IApplication.getEffectiveUserIds did not work

In UBI, iApplication.getEffectiveUserIds did not work.

5.1.2 DE45598: (UBI) IDocument.GetProperty did not return more

than 1024 characters

In UBI, using IDocument.GetProperty resulted in only 1024 characters being returned.

5.2 RICH CLIENT

5.2.1 DE40227: Fulltext recognition in big text files leads to Rich

Client and API call hang


Doing a fulltext extraction for large files using either FileText in the Rich Client or via API call caused the

client to hang. Sample file size was approximately 574 Mb.

5.2.2 DE41620: Picea skin switched to Classic skin after logging

back in

Picea skin switched to Classic skin after relogin, even when the skin was defined to be Picea. This is

because Picea was discontinued some versions ago. This has been fixed by removing the Picea skin from

the Saperion settings.

5.2.3 DE41854: Document tool tip was superimposed on Windows

application

When the Saperion Rich Client was open and another Windows program, such as Notepad, had focus, a

tool tip was shown in the Saperion results list and could be superimposed over the Windows program.


1. Open the Rich Client and run a query in an application.


14

2. Open Windows Notepad and write some text.

3. Mouse over a document in the results list.

Result: A Saperion tool tip was shown, although the Rich Client didn’t have focus.

5.2.4 DE42257: Email client character encoding detection did not

detect Saperion emails as UTF-8

Saperion did not depict special characters correctly in Saperion email, in email clients such as Outlook or

Thunderbird. Saperion emails are supposed to be encoded as UTF-8, but the emails were displayed with

the default encoding (Western European). UTF-8 encoding only seemed to apply to the email subject.


1. Send email to a workflow. The email should contain diacritical marks such as umlauts

and accents.

2. Check the emails in a mail client such as Outlook.

Result: Corrupted characters appeared where the diacritical marks should have been.

5.2.5 DE43334: No longer possible to display linked documents in

separate viewer

It was no longer possible to display linked documents from the result list in a separate viewer window,

neither for View nor Edit.

5.2.6 DE43871: No longer possible to change user status

It was no longer possible to change user status by navigation to Saperion > Settings > Current User,

without setting a new password.

5.2.7 DE45102: Multipage TIFF could not be created for e-mail

The multipageImageComponent and CollateImage parameters worked as expected (multipage TIFF was

created), however, when sending the object, the pages were attached to the e-mail separately instead of

combined in one multipage TIFF file.

5.3 WEB CLIENT

15

5.3 WEB CLIENT

5.3.1 DE41046: Multiple selection in multivalue fields didn't work

in index forms

Multiple selection in multivalue fields didn't work in index forms.


1. In the Web Client, activate a multivalue field.

2. Select multiple values in that field in an index form.

Result: You couldn't.

5.3.2 DE43361: (Snowbound) Creating annotations only stored the

new annotation

When using Snowbound Virtual Viewer 1.6, new annotations were stored but previous ones were deleted.

5.3.3 DE43445: Not possible to disable author information on

stamps

In the Web Client and Classic Connector, the author information was always disabled on stamps. There

was no way to disable it.

5.3.4 DE44141: When access to SER Connector failed, LoadDoc

plug-in error was logged

When accessing SER Connector objects failed, the following error was logged:

OpenDoc: PlugIn LoadDoc not called, failure at InterServer.LoadDoc

The logging has been extended so that a proper analysis can be done when this error is logged.

5.3.5 DE45155: SER Connector displayed only first page

The SER Connector only displayed the first page of multipage documents of the type image/jpeg,


16

5.3.6 DE45156: SER Connector did not support the

mergeMultipageTiff parameter

When using the SER Connector to work with single page TIFF files, the mergeMultipageTiff parameter

did not work.

5.3.7 DE45173: Workflow context menu not shown

When a user task was in the group inbox, and a group member tried to move the work item to his

personal inbox, the context menu was not shown.

5.3.8 DE45336: Error when displaying documents from result list in

preview

An error was written when stepping through the results list and previewing the documents.

5.3.9 DE45413: Multi-search default string separator verfication

failed

During searches using the multi-search field in a form, the string separator verification failed. Multi-value

handling in the old lookup control was also affected.

5.3.10 DE45476: SSO with SAML does not work when SAML

response is not sent to receiver

Single sign-on (SSO) did not work when the SAML response was not sent to the receiver in the Web

Client.

5.4 CORE SERVER

5.4.1 58050: ODBC log messages did not include constraint

violation parameter values

The constraint violation parameter values were not inlcuded in the ODBC log messages. This made it

difficult to correct the logged error.

5.4.2 DE40990: Java Core Server terminated with unhandled

exception

In rare instances, the Java Core Server terminated with an unhandled exception.

5.5 STORAGE/PLUG-INS

17


5.5.1 DE42872: Plug-in names in dir.smd file were being read

When a plug-in was being loaded, the name was read from the medium.ini file as well as the dir.smd

file. If the name in the dir.smd didn't match that of the plug-in used, access failed. This has been fixed

so that a parameter can be set to only read the name from the medium.ini.

[Compatibility]

UsePluginFromMediaDB=FALSE

Set to FALSE, the plug-in name is not read from the dir.smd. Default is TRUE.

5.6 LDAP

5.6.1 DE43810: Couldn't create users in LDAP context with

high-ascii characters

When you have an Organizational Unit (OU) in your LDAP context, and the LDAP context contains a

high-ascii character such as "ü", no users are added during synchronization.

5.7 SAP

5.7.1 DE39243: R/Link ArchiveLink command "DocGet" returned

data but no document

The R/Link ArchiveLink "DocGet" command only returned information about the document, but not the

document itself.

5.7.2 DE45158: SER Connector SAP ContentType not set correctly

The SER Connector ContentType was not set correctly. Documents could still be displayed, but they could

not be retrieved using R/Link (404 Error).

5.7.3 48310: R/Link temp files were not removed

During read and store operations, R/Link temp files were locked and could not be removed until R/Link

was restarted. The temp files are now removed automatically, and a restart is no longer necessary.

6 Patch Level (r89093) - June 15, 2015

18


6.1 API - COM/UBI

6.1.1 DE42971: (ClassicConnector) API license not used

The Classic Connector logon used the default index license instead of an API index license (type 16).

6.1.2 DE44430: Hibernate queries failed in a multi-tenant system

Hibernate queries failed in a multi-tenant system when the DDC name is part of the field name.

6.1.3 DE44458: (Classic Connector) ReadDocument error in

multipage TIFFs

Using the readDocument function rendered the last pages of some multipage TIFFs incorrectly

6.1.4 DE44517: (Classic Connector) Session timeout check didn't

work

The Classic Connector session timeout was counting from the login time, instead of from the last activity.

6.1.5 US71382: New property for getting docLoadOriginal status

The document property Document.OriginalFormat (Long) was added to determine whether an image is

archived using docLoadOriginal TRUE or FALSE.

Property return Definition

1The image was archived with DocLoadOriginal=TRUE. The original TIFF file exists in

the repository.

0The image was archived with DocLoadOriginal=FALSE. TIFF image is loaded by

Saperion and converted to the Saperion internal image format.

For more information, refer to the "Client-side COM objects" chapter in the Development manual.

6.2 CORE SERVER

19

6.2 CORE SERVER

6.2.1 DE45051: (Classic Connector) Memory errors when

documents were loaded

Under certain circumstances, memory errors occurred when documents were being loaded or saved.

Memory management has been stabilized and these errors eliminated.

6.2.2 US72115: Business Rules Server couldn't render

The Business Rules Server (BRS) was not able to render documents. New render engines were built into

the BRS to resolve this problem.

6.3 RICH CLIENT

6.3.1 DE39239: Printing TIFF documents into existing structure

didn't work

It was not possible to print TIFF documents that were printed to the document tray, into a

previously-archived structure. The action resulted in a rollback and an error message.

6.3.2 DE40115: Multi-client DDC without SysAclUserList could be

used to create applications

When you had a multi-client DDC that didn't contain the SysAclUserList function, every client could

create applications and queries with the DDC.

6.3.2.1 Steps to Reproduce

1. Create a multi-client DDC with no SysAclUserList function.

2. Create an application for each of two clients.

3. Archive a few documents with the first client.

4. Create an ACL with all administration rights for the first client.

5. Add the ACL to the documents.

6. Log in as the second client, run a query on the application.


20

Result: Documents were displayed without a lock symbol and were accessible. However, when you logged

in to the first client with a user with no ACL rights and ran a query, the lock symbol was shown.

6.3.3 DE40124: Multi-format viewer in index form caused archiving

rollback

Archiving of a structure was rolled back when the multi-format viewer was part of the index form.


1. Create a structure that contains at least two PDF documents and a document of some

other format.

2. Drag the structure to an application which is linked with an index form that uses the

multi-format viewer (PDF).

3. Enter index data and confirm with OK or Save.

Result: The structure was not archived, and the broker displayed the following notice:

FinishTransaction: Rollback transaction [CSM-VM-01.0000091C,DE070A001C0013]=Ok :

rollback successful

6.3.4 DE40258: "User must change password at next login"

function caused hanging user sessions or licenses

Selecting "User must change password at next login" could lead to an internal user session not ending.

The sessions were not cleared out by the session timeout. This could lead to all licenses being used up.


1. In the Saperion user management, select the "User must change password at next login"

check box for an internal user.

2. Open the Web Client and go through login process.

3. Close the user profile dialog by clicking "Cancel".

4. Check session in the MMC.

Result: The user session hung instead of ending, which sometimes lead to all licenses

being in use. Even when you used the Task Manager to end the Rich Client, the session

remained active and was not cleaned out by the session timeout as expected.

6.3.5 DE42278: "Previous Link" button didn't work

When you opened a link from inside a document, it was not possible to return to the original document

using the "Previous Link" button.

6.4 WEB CLIENT

21

6.3.6 DE42354: Creating a global media pool caused exception in

MMC when no pool existed

When attempting to add a global pool in the MMC after installing, the Saperion snap-in failed with an

error message.


1. Complete a new installation.

2. In the MMC, add global pool.

Result: The Saperion snap-in failed, with the following error message.

EXCEPTION unhandled: WHOLE-OVERFLOW at FolderDialogs.445

6.3.7 DE44540: Writing/reading fulltext metadata took minutes

when fulltext contained Euro character

Reading or writing fulltext metadata took minutes when the fulltext contained the Euro character (&80h).

6.4 WEB CLIENT

6.4.1 DE39456: Decimals rounded to 3 places in floating point fields

In floating-point fields, decimals with more than three places were rounded up to only three places.

6.4.2 DE40779: Some searches in multivalue fields returned

incorrect results

When searching on a value in a multivalue field, the Web Client only returned hits when searching for

the complete value. Searching for parts of the value, with or without wildcards, returned no hits.


1. Create a DDC with a "character" index field, and select multivalue field. Do not define a

separator, so that comma is used by default.

2. Create an application consisting of index and query form.

3. Archive a document with the application, and, in the multivalue index field, enter multiple

index values, such as "house" and "child", separated by commas.

4. In the Rich Client, run a search on "hou" or "chi". Then run the same search in the Web

Client.


22

Result: In the Rich Client, the corresponding result was shown in the results list. In the Web Client, the

same search returns no hits. Even when wildcards were used ( * ), or with "ExactMatch=false" set in the

webclient.properties file, the Web Client didn't find anything. The Web Client only found results when

the complete word was entered as the search criterion.

6.4.3 DE42164: Performance issue with workflow inbox with

multiple workflows

When running 20-30 workflows simultaneously on a document, and then right-clicking a workflow in the

Web Client, the context menu took about 10 seconds to open.

When only one workflow was being executed on a document, performance was fine.


1. Start a lot of workflows on one document.

2. Activate Hibernate and ODBC logging.

3. Right-click in a workflow in the inbox to open the context menu.

Result: When 20 to 30 workflows were started, the context menu took approximately 10

seconds to open.

6.4.4 DE42594: Field validation failed for empty multiselect lookup

table fields

The validation of lookup table fields in multiselect mode failed with a ZK Framework error if the field

was empty when called.

6.4.5 DE43370: Workflow history window didn´t scale, had no Close

button

When resizing the Workflow History window, instead of scaling properly, content was cut instead of being

scaled and no Close button was available.

6.4.6 DE43371: Double-click events in Workflow inbox were not

being caught

The EventListener wasn’t catching double-click events in the Workflow inbox.

6.5 WORKFLOW

23

6.4.7 DE43881: Not possible to create multivalue entries in a lookup

table

When a multivalue field was used in a lookup table that called another lookup table, it was not possible

to create additional lookup values.

6.4.8 US68463: Custom rendering of result list in Web Client

We have renamed and deprecated the following methods with this patch level release. The old methods

will be available until the release of Saperion version 8.0 in 2016.

For more information about the methods, refer to the Web Client JavaDocs.

Deprecated method Replacement method

getSelectedItem getSelectedListItem

getSelectedItems getSelectedListItems

setDocumentRead(DraggableListItem) setDocumentRead(ResultListItem)

setDocumentUnread(DraggableListItem) setDocumentUnread(ResultListItem)

6.5 WORKFLOW

6.5.1 DE41767: Groups not activated for workflow pool could be

selected as receivers

Groups that were not activated for workflow pool usage could be selected as workflow receivers. This

has been fixed so that the user can now only choose groups that are also workflow participants.


1. In Saperion, have two groups, one with workflow pool active, and the other without an

activated workflow pool.

2. Address a workflow to the first group.

Result: The workflow is shown in the group tray. Expected: Groups would not be shown

3. Address a workflow to the second group.


24

Result: The workflow wasn't shown anywhere and thus could not be worked on.

6.6 SAP

6.6.1 DE39245: Jadice Web Viewer displays text poorly

When Jadice Web Viewer displayed text on a non-white background, the text appeared in poor quality

and not readable.

6.6.2 DE40353: Jadice Web Viewer problems with printing

In the Jadice Web Viewer, single documents were not printed, while in documents with multiple pages,

the last page was not printed.

6.6.3 DE41360: ArchiveLink server information request reported

errors

The ArchiveLink server information request reported invalid repository errors in the log. These are now

marked as “Notice” instead of “Error”.

6.7 IXOS

6.7.1 DE44195: Connector wrapper logs password

The IXOS Connector wrapper logged the technical user password in the wrapper.log (IXOS version 1.1.3).

6.7.2 DE44196: Registry file could not be imported

The IXOS registry file could not be imported into the Windows registry because it was not ANSI-encoded

(IXOS version 1.1.3).

7.1 API - COM/UBI

25

7 Patch Level (r88730) - May 13, 2015

7.1 API - COM/UBI

7.1.1 Session timeout parameter

Use the session timeout with all Classic Connector processes that run continuously. The default setting

is 8 hours (2880 seconds). In systems where Classic Connector processes run longer than 8 hours, the

timeout must be increased accordingly.

Example

SessionTimeoutSec=2880

7.1.2 DE41745: Classic Connector: Multiple threads

Running multiple threads simultaneously caused a Java exception. The Classic Connector can now

handle multiple threads.

7.1.3 DE42534: Using Document.SaveChanges with multi-page

TIFF results in large files

When Document.Load was used to load a previously-archived document, and another multi-page file

was added to it with the same InsertImage command and then Document.SaveChanges was executed,

each page was the size of the complete original file. This filled up the medium very quickly. This has been

fixed so that page size is around 40Kb, as expected.


1. Execute the following macro:

sub Import_grosse_Rechnung

dim oCur as object

dim oDoc as object

dim ok as boolean

const sFile = "C:\temp\EINGANGSRECHNUNG.tif"

set oDoc = Application.CreateDoc

oDoc.DBname = "Test1"

ok = oDoc.SetProperty("Name", "Storniert2")

'ok = oDoc.SetProperty("Barcode", "20150402005")

oDoc.InsertFile "C:\temp\Hallo_Welt.txt"

'oDoc.InsertFile sFile

ok = oDoc.Store

'exit sub

7 Patch Level (r88730) - May 13, 2015

26

msgbox "Store: " & cstr(ok)

ok = oDoc.LoadLink

oDoc.InsertImage sFile, 0, false, false, true

ok = False

' ok = oDoc.Store

ok = oDoc.SaveChanges

msgbox cstr(ok)

set oDoc = Nothing

end sub

Result: A file per page was created on the medium, and each file was as large as the original

multi-page TIFF file.

7.2 CORE SERVER

7.2.1 59010: Non-standard separators in multi-value fields

When non-standard separators were used in multi-value table fields, and the DDC was changed (for

example by adding a field) and a check-out was done, the entries in the multi-value table were separated

incorrectly.

7.2.2 DE40105: Module and COM users were not added to macros

in the Legacy server

When adding a task and selecting a macro in the Legacy server, it was not always possible to save the

module or COM user information in the MMC. This action has been disabled in the MMC. Use the Rich

Client to save module or COM user information.

7.2.3 DE42295: Log messages were not written to the log file in

high-load situations

Log messages were not written to the log file in high-load situations.

7.2.4 DE42781: Uncommitted transactions while uploading

documents

When a batch of documents was dragged to an application in the navigation area, an uncommitted

transaction remained on the server until the last document in the group was archived.

7.2.5 DE43047: Server tried to initialize missing printers

When the render option was activated without a printer being installed, the server attempted to initialize

the printers, which failed.

7.3 INTEGRATION SERVER

27

7.2.6 DE43503: Invalid hMem

When a document was updated via Classic Connector, the ArcMem.log file contained an invalid hMem

for unlock.

7.3 INTEGRATION SERVER

7.3.1 DE41402: Integration Server: Inconsistent events on eFile

plans

In an eFile project, adding or moving documents into registers resulted in inconsistently different events

for the Integration Server, depending on how the document was added.


1. File new document directly from file system (such as Explorer) into Saperion eFile register

using drag & drop.

2. File new document from Saperion tray into Saperion eFile register using drag & drop.

3. Also copy existing document into another register using <CTRL> + drag & drop.

4. Move existing document into another register using drag & drop.

5. Observe events (shown in wrapper.log)

Result: Expected events, such as CreateDocumentEvent, UpdateDocumentEvent and

LinkDocumentToFolderEvent, were frequently missing from the log.

7.3.2 DE43368: Integration Server workflow event not fired

Integration Server workflow events were not fired when the workflow was handled by the Legacy server.

7.4 RICH CLIENT

7.4.1 DE40018: eFile could be deleted even if it had registers

An eFile could be deleted even when it had registers. It is now only possible to delete eFiles that don't

contain registers.

7.4.2 DE40125: Editing structure from within the viewer behaves

unexpectedly

Editing unarchived files with the viewer and its thumbnail view worked until the file was saved or the

thumbnail view was closed.

7 Patch Level (r88730) - May 13, 2015

28


1. On a structure page, double-click in the document tray to open a document.

2. In thumbnail view in the viewer, delete some documents.

Result: The document structure changed in the tray as well as in the thumbnail view.

3. Closing thumbnail view, you are prompted to save the document. Click "Yes".

Result: The thumbnail view remained. Closing it again resulted in another prompt to save

the document.

Clicking "No" resulted in thumbnail view closing, and the document no longer contained

the deleted page and could be archived.

7.4.3 DE41900: Individual profile settings did not match

When using a profile with limited access, functions that were not available to the user were marked

in bold text. Functions are now only bold once they have been activated for a user with corresponding

privileges.


1. Create an access profile that includes „Index“, „Query“, „Display/Print” and “Edit”.

2. Log in to Saperion.

Result: In the ribbon, the Administration options were in bold text, even though these

functions were not available for the defined user.

7.4.4 DE42294: 100% CPU when in high-load situation (wait event

in media database)

100% CPU when in high load situation (wait event in media database).

7.4.5 DE42535: Favorites folder could be deleted

When the last "favorite" was deleted via Folder > Edit > Delete, the "Favorites" folder itself could be

deleted.


1. Run a query in any Rich Client application.

2. Make the query a favorite by navigating to Sart > Search > to Favorites.

Saperion automatically switches to the Favorites folder in the Rich Client workspace.

3. Delete all existing favorites by navigating to Folder > Edit > Delete.

7.5 WEB CLIENT

29

Result: Once all the favorites were deleted, the Favorites folder itself could be deleted via

Folder > Edit > Delete.

7.4.6 DE42644: No filtering on dynamic outliner item with "("

When an item in a dynamic outliner contained an open parenthesis “(“, the item was not filtered.

7.4.7 US64499: GUI for selective encryption

It is now possible to select a client and corresponding encryption profile in the “Global pool” dialog

box in the MMC.

7.4.8 US68604: GOST-based algorithms can now be used

It is now possible to use the GOST algorithm when encrypting with Saperion.

i The default value of the “AllowEncryption” parameter was change from TRUE to FALSE.

7.4.9 US69101: No longer possible to copy encryption profiles

To avoid problems arising from changed passwords in existing encryption profiles, the ability to copy

encryption profiles was disabled.

7.5 WEB CLIENT

7.5.1 DE40259: Linked documents could not be reopened in the

viewer

After viewing a document with one linked document in the viewer, and then closing the viewer, it was

not possible to open the document again without opening another document first.


7.6.1 DE43413: Verify failed due to NetApp retention mapping

Verify failed due to NetApp retention mapping after January 19, 2038. Saperion now remaps the retention

mapping to the correct date.

7 Patch Level (r88730) - May 13, 2015

30

7.6.2 US69623: Problem with ICM plug-in

When the ICM plug-in was not available, objects ended up in the error queue. Executing a verify caused

them to disappear.

7.7 LDAP

7.7.1 DE42865: LDAP synchronization aborted with SyncObject

error

For certain Active Directory configurations, LDAP synchronization aborted with a SyncObject error .

7.8 SAP

7.8.1 DE42758: Multiple certificates listed in MMC

Clicking on a certificate in the Certificates tab in the MMC caused a list of certificates to display, instead

of only one.