[ConvergentCharging] sessionId computation changes between start and update of transaction

[mehdijouan]

When a transaction is opened in emobility, a session is opened in convergent charging. The sessionId is computed by ConvergentChargingPricing.ts as the hash of:

consumptionData.userID + consumptionData.chargeBoxID + consumptionData.connectorId + this.transaction.timestamp;

When the transaction is updated in emobility, the session should be updated. The problem is that the computed sessionId for the update is different of the one computed during the start.

[mehdijouan]

During the start of the transaction, it has not been saved yet and its timestamp is of type string. When fetching it from the DB it is a Date type. It leads to the following difference when concatenating values :

• 5c62a24a084dd543fd640ff3SIMU12019-09-06T16:33:06+02:00 during the start of the transaction
• 5c62a24a084dd543fd640ff3SIMU1Fri Sep 06 2019 16:33:06 GMT+0200 (Central European Summer Time) for each update

The solution proposed is to check the type of timestamp prior to compute the sessionId to always have the same behavior.