Fixes:
WebClient (Server): LDAP login failed if umlauts were used in the password.
WebClient (Server): LDAP login with an empty password performed an unauthenticated/anonymous bind that many LDAP servers (incl. AD) accept, which would grant login without a password and now is prohibited.
WebClient (Server): login via POST was blocked by CSRF token check.
WebClient (Server): Newly added columns monthly copy and scan volumes in report 'Capacity Utilisation' were not correct.
WebClient (Server): A sort link in the table header of report 'Capacity Utilisation' was missing.
WebClient (Server): The reports 'Page counter per month', 'Page counter per quarter' and 'Page counter click volume per month' caused an exception if device data of a non existent device was used.
WebClient (Server): A customer specific version of report 'Counter overview' now also shows device specific start and end date within the selected period.
Server: Reminder mails to enter counters manually have been sent 1 day later as configured.
Server: Marker status mails for printer groups were not sent as configured.
Client: Updating SNMP v3 context name via Server GUI did ignore empty strings.
HTTP Server: solved refusing display of some pages and tables due to CSRF token problems.
Feature:
WebClient (Client): Spanish and Portuguese UI and online help.
WebClient (Server): Spanish and Portuguese UI and online help.
WebClient (Server): CTRL-ALT-A on report pages allows dealers to use report "consumables" for single device history.
Client: The number of days of unsuccessful transmission after which a client stops sending can now be adjusted in the DFOPTS2.INI file. The default value is 30.
Mailer: Separate log file accmailer_EVATIC.log for Evatic thread.
Mailer: Separate log file accmailer_RECEIVER .log for receiver thread.
Mailer: New INI Parameter in accserver.ini at [Mailer Process] LogLevel, Default ist 3 (Error: 1, Warning: 2, Info: 3, Debug: 4).
REST API: GET /dfmserver/v2/devices/{deviceId}/counters now supports an optional parameter "date" to get the last known counter values at a specific date.
REST API: New endpoint GET /dfmserver/v2/customers/{customerId}/counters retrieves the counters of all devices of the customer, optionally with a parameter "date" to get the last known counter values at a specific date. To identify the devices externally, some master data of each device is returned.
REST API: GET /dfmserver/v2/devices now also returns "pagesPerMonth" which is the recommended page load per month of a device.
REST API: New endpoint /dfmserver/v2/devices/{deviceId}/events/{eventId} returns the information of a specific event, identified by its Id.
REST API: Logging has now changed. At least one log file is now created for each day. The name is composed of <$apiSettings[‘logfile’]>_YYYYMMDD_N.log where YYYYMMDD represents the date and N is a sequential number starting at 1. If the $apiSettings[‘max_logfile_size’] limit is reached during the day, N is incremented and another file with the same date is created. The new variable $apiSettings[‘max_logfile_ttl’] specifies the number of days after which old log files are deleted. The default is 90 days.