Professional Documents
Culture Documents
5
Copyright © SAPERION AG
Disclaimer
The content of this manual, including all images, tables, and drawings are the intellectual property of SAPERION AG.
All rights are reserved. Altering or deleting copyright notes, distinguishing marks and/or control numbers, or drawings is
prohibited.
SAPERION AG grants the use of the contents for contractual purposes only. The contents of this manual are subject
to changes without requiring SAPERION AG to provide prior notice. The users of the manual are obligated to inform
themselves, at regular intervals, about the availability of modified versions or other details concerning the offered products
and services in the Internet at www.saperion.com and to take such information into consideration during use.
All devices and program names and other products from SAPERION, as well as the corresponding logos used in this
manual are trademarks or registered trademarks of SAPERION AG in Germany and other countries worldwide. All other
product and service names are trademarks of the respective companies.
The information in this manual is provided by SAPERION AG and its affiliated group companies ("SAPERION Group").
The SAPERION Group assumes no liability for errors or omissions in this manual. The only warranties for SAPERION
Group products and services are those that are set forth in the express warranty statements accompanying such products
and services. Nothing in this manual should be construed as constituting an additional liability.
Copyright © SAPERION AG
SAPERION AG
Steinplatz 2
D-10623 Berlin
Sales 781.899.1228
Fax: 781.899.1244
Email: usa.sales@SAPERION.com
Web: http://www.SAPERION.com
Table of Contents
For more details about functionality, please refer to the "Best Practice" sections and other documentation
in the SAPERION documentation portal. In addition, please refer to the current Compatibility List for
further information regarding the system itself.
1. Discontinued Features
Please note the features that are discontinued as of SAPERION ECM version 7.5.
2. System Requirements
Before installing, make sure that your computer meets the system requirements.
1
1 Version Notes
1.2.3 Databases
Database ODBC Driver
SAPERION ECM Java Core UBI API Universal Importer Version 3 Web Client
Server incl. Classic Connector
2
2.1 General Notes
3
3 New Features and Components
i The revision history in the Rich and Web Clients now includes the very first version (creation).
+ MainInstanceId
+ TokenId
+ LastEscalationDate
4
3.1 SAPERION ECM Process Modeler
To manage the business rules and configure tasks, the Integration Server has a graphical user interface,
which makes it easy to manage complex rules in a clear and straightforward way. In addition, the
Integration Server includes a series of configurable standard tasks, which can be used for event
monitoring, logging, document indexing and more. Because of its high flexibility, its ease of configuration
and its scope and performance, the Integration Server is a suitable replacement for the SAPERION
Business Rules Server.
5
3 New Features and Components
LEAD-compressed images in the Web Client. The legacy server can also be used to execute all core server
tasks (EventScripts) with a 64-bit server.
Additionally, the command "Refresh system files" is available in the MMC; it can be used to refresh data
during runtime without restarting the server.
+ ACLs, index values and comments can be specified before archiving, using a script
+ A script can also be used to display pop-up forms as index and query forms, as well as to listen
for button events
+ It is now possible to set (string) variables to dynamically gather and save data when storing a
document. This can be done via script or input field.
+ Applet
Document can be sent as link, attachment or PDF. Multiple elements can be sent as a .zip file.
Works only with Outlook.
6
3.9 Web Client
+ Mailto:
Document can be sent as link, and multiple elements must be sent as a .zip file. Works with any
mail client. Web services must be installed.
7
3 New Features and Components
during an update to preserve the user's settings and then copied back into the application directory after
the update is done.