Disclaimer

This document is only collection of author’s notes, experiences and point of views. It is not, in any meaning, either complete description of the topic nor official RTB documentation. It may be inaccurate, incomplete, obsolete, misleading or completely wrong. It may even cause loss of data or damage system integrity. It may not comply with company codex, values, presentation style or economic interests or may reveal company secrets.

As such, it is absolutely prohibited to distribute this document outside of RTB & Co. GmbH. Such an action may result into legal acts against both the sender and the company. It is only intended, after review of technical and presentational correctness and accuracy, to be used as an information source for official documentation.

Always contact documentation department for information about current presentation style and allowed formats before creating customer’s documentation.

Environment

Component Version

Java

21

PostgreSQL

16

Tomcat

10

24.0.0

Database upgrade can take long time, depending on the database size. Temporarily scale up the server may speed up migration.

Payment database table support partitioning

Motivation

The table where payments are stored grows rapidly (currently it has ~ 110 000 000 rows). This make query slower because of big sizes of indexes and other data structures. To address this issue PostgreSQL offers an instrument called table partitioning.

See more details in payments partitioning document.

Migration to partitions

Following steps are optional. If your system is small and performance is good you can skip it.

It migrate to partitions follow instructions here.

Features

  • Extension of ID card bonus aka "Badesee" bonus. Add expiry date and max. number of usage per day to ID card bonus. See more in feature documentation on in PCON-2726.

GDPR

cleanup

Clean up of car license plates can be set individually per Area. Go to Area  Legal  Clean LPN. A positive value > 0 must be entered to activate the feature. The number means how may days a license plate number will be kept in the database. If filed is left empty, the feature is deactivated for this Area. Property pcon.gdpr.eviction.lpn was removed.

LPN visibility

There is a new role View LPN, which must be assigned to user be able to see LPN in various listings and exports. This role does not affect enforcement API, which always delivers LPN independently from this setting. Property pcon.gdpr.protect was removed.

Small changes

  • Links to logbooks in menu re-ordered.

24.1.0

RAO

Added support for partner RAO. Because it must have a counterpart on Windows it requires a configuration. Add following properties and supply real values how to connect the counterpart:

pcon:
  partner:
    rao:
      url: http://192.168.1.100:20000

24.1.1

  • Updated translation to italian language.

  • Fix autocompletion in login form.

  • Remove error indicator on RAO configuration.

24.1.2

  • Fix performance issue by fetching filters. It caused nonfunctional logbooks.

24.1.3

  • Transfer sale point (PDM number and name) and means of payment to RAO (ParkIS).

  • New texts for status message 204.

24.1.4

  • Additional payment data in export API.

  • Use new API from Feratel.

24.2.0

  • Implementation of a new interface from Feratel [PCON-2854]

  • Fix revenue widget [PCON-2882]

  • New reasons for message 204

  • Italy need some new info for API, just now: ParkingMinutes:123, PagoPaID:123CDF564TYB [PCON-2887]

24.3.0

  • Bonus extension for Italy. Now it can be selected if a start or end of park time is considered.

  • Fix performance issus on database.

24.3.1

  • Fix handling of special characters in communication with RAO.

24.3.2

  • Add support for residential parking in Zagreb.

24.3.3

  • Extend embedded timeouts for connection to 3rd party services. RAO is very slow and exceeds timeout frequently.

24.4.0

  • New partner Allgäu Walser Card.

  • Fix sorting of partner zones.

  • Support passwords revealing for partner configuration.