Hier finden Sie Anwenderberichte und Informationsmaterial rund um die CRM-Lösungen der CURSOR Software AG.
CURSOR ist seit mehr als 30 Jahren auf Software und Beratung für das Kunden- und Geschäftsprozessmanagement – CRM und BPM – spezialisiert. Mit Softwareentwicklung, Beratung, Softwareeinführung, Schulung und Support erhalten Sie ein umfassendes Leistungsspektrum aus einer Hand. Herausragendes Merkmal ist die Flexibilität der Anwendungen. Ob on-premise oder aus der CURSOR Cloud: Branchenspezifische und individuelle Anforderungen werden exakt abgebildet, Anpassungen können jederzeit umgesetzt werden.
Unternehmen der Energiewirtschaft (Produkte: EVI für Energieversorger, Stadtwerke und Energiedienstleister und TINA für Netzbetreiber), Banken und Finanzdienstleister sowie Dienstleistungs- und Industrieunternehmen (Produkt: CURSOR-CRM) profitieren so von exakt an ihren Anforderungen ausgerichteten Geschäftsprozessen.
4.2 Rich Client ■ ■ ■ >= Dual Core with min. 2.5 GHz >= 4 GB RAM (CRM application requires around. 500 MB for regular users and up to 800 MB for admins and power users that process large data quantities) Network connection (per client) to the application server: >= 100 MBit/s ■ The latency of a network line between Rich Client and JBoss application server must not exceed 8 ms, otherwise the Web Client must be used. ■ ■ >= 1,5 GB hard disk storage space for the client software incl. caches and Java runtime environments. The client software must be stored locally. Client initiation via a network drive will at times result in severe speed losses. Java Runtime 17.0.4, free ■ Windows 10 or Windows 11 ■ Screen resolution min. 1280 x 1024 px Note Due to the lack of support of vector graphs, the Rich Client does not support scaling of text, apps and other elements. A meaningful use of the Rich Client is therefore not or only to a limited extent possible on the MS Surface tablet PC, similar devices or 4K monitors. You should ensure for performance reasons that the computers are not running in power save mode, which means that the recommended default mode "Balanced" must be set. Notes on the storage requirements of the Rich Client 1. Processing large data quantities A selection of 40,000 datasets in case of a task list with 15 columns will result in the storage requirement on the client to temporarily increase by 50 MB and to then significantly decrease again, which means an actual increase around 10-15 MB. In order to guarantee the best performance for this selection, the temporarily required 50 MB should be readily available. More detailed tests with multiple levels and 40,000 datasets each have resulted in a Java heap storage requirement of around 350-380 MB, resulting in an overall storage requirement of 500 MB incl. a "MaxPermSize" (storage for permanent object generation) of 128 MB. 2. Using the Browser View component In the standard version, the option of integrating a web application in Rich Client masks (or on the desktop) will require 10-20 MB storage space on the Java client. Depending on user behavior and the number of implemented Browser Views, the generated Chrome instances will use several hundred MB of main storage on the client computer, which is around the same storage requirement for loading these views in the internet browser. This is an important consideration, specifically in terms of main storage assignment in terminal server/Citrix environments. 4.3 CURSOR App ■ iOS >=14 System Requirements | Author: Gebriyel Varli |Date: 14.10.2022 | 10