System Requierements Version 2023.1

10. Report Engine Report

10. Report Engine Report creation is based on the Open Source tool JasperReports. JasperReports is a Java library, which can be implemented in any project. The API allows the creation, manipulation and execution of report designs. The report engine is integrated on the application server, which facilitates and speeds up access to reporting data. A runtime installation on clients is not required. The client should, however, have an Acrobat Reader installation to view the reports supplied by the server in PDF format. Where other formats are required, the matching apps should also be installed. Designers of new reports must have access to the REPORT database scheme, which should be implemented either on the central database server or on another computer that is accessible for report designers (poss. based on the free Express Edition). A CURSOR-CRM client and the named access (via JDBC) to the REPORT database/instance must also be provided. 11. Groupware Connection A Groupware system can be implemented either via a client-side Outlook connection, which communicates with the Outlook client via the MAPI interface, or by way of a Groupware server (MS Exchange or IBM Lotus Notes). The client-side Outlook interface option has established itself as standard where Rich Clients are used. To ensure the rich client access to Outlook, the following group policy settings must not differ from the default value: User Configuration -> Guidelines -> Administrative Templates -> Microsoft Outlook 2016 -> Security - > Security Form Settings -> Programmatic Security ■ ■ Configure prompt for Outlook object model when accessing an address book ■ Default value: Prompt users based on computer security Configure prompt for Outlook object model when reading address information ■ Default value: Prompt users based on computer security In he case of a Web Client or the inbox manager, a server-side interface technology is used, i.e. the data is not synchronized via the Groupware client, but directly with the server instead. In the case of MS Exchange, the mail interface requires the Exchange Web Service API (EWS API). Alternatively, mail can be sent and imported via a mail server that supports the SMTP and IMAP protocols and where the corresponding services are activated on the groupware server (note: IMAPS with SSL or TLS possible). The appointment and task synchronization is implemented via the API of the Groupware system. In the case of MS Exchange, the Exchange Web Service API is used, where at least Exchange 2013 must be available in order to use the server-side appointment and task synchronization (e.g. on the Web Client). The EWS interface is supported only with the authentication method "Integrated Windows Authentication" (NTLM or Kerberos). In a Lotus Notes connection, the CRM system accesses the Domino server via the DIIOP protocol. Furthermore, an internet password must be set and database browsing via the internet must also be permitted. Authentication therefore occurs by way of the so-called internet password in the Notes user document of the NAB (name and address book). System Requirements | Author: Gebriyel Varli |Date: 14.10.2022 | 15

12. Office Suite Use MS Office 2013, 2016 or 2019 for your Office area implementation. The Integration with Office 365 is tested and approved in case of local installation. However, no connection exists for the web/online versions of MS Word and MS Excel. 13. Telephony Integration Server-based CTI integration For a telephony integration, you can use a server-based CTI (Computer Telephony Integration), which is available in the Web Client and Rich Client. The telephone system is accessed directly via a communication module provided by our partner Clarity AG. We recommend installing the CTI server on the same machine as the application server. However, if installation on a separate machine is desired, the following requirements must be met: ■ ■ ■ ■ 2 CPU cores with min. 2.7 GHz >= 4 GB RAM >= 100 GB hard disk space Network connection to the application server: >= 1 GBit/s (LAN) ■ >= Windows Server 2012 ■ Fully implemented RFC-compliant CSTA, JTAPI or MS-TAPI interface to the telephone system. Alternative connections require technical examination. CTI uses the quick start bar in the CRM system to e.g. log and track missed calls. Client-side TAPI interface With the conversion of the Rich Client to 64 bit, a client-side TAPI connection is no longer possible, therefore the use of server-based CTI integration is recommended. System Requirements | Author: Gebriyel Varli |Date: 14.10.2022 | 16