HU-GO instructions for operations in confluence

If a value is WAITING_3RD_PARTY_INTEGRATION - it means object was registered using Postman, but the client did not add the object to his HU-GO account; - In such case needed to contact customer or service provider and inform them that this object registration is not finished, customer should finish registration or purchase tickets manually. Either way, we should get information if registration will be finished or if we need to delete an object from the HUGO registration.

If a value is ENABLED - it means an object is added to the client’s HU-GO account and functionality will be working. - The next step is to check if a device is sending data and if sending records according to requirements. Further steps in the chapter "Got alerts that vehicle is in Hungary and no data was received from an object that entered Hungary"

If a value is DISABLED client removes an object from his account for Hu-Go, or was deactivated from our partners from Cargo-Track. - Contact customer or service provider inform them that service was disabled, and ask to clarify if service enabling is still required. In order to reenable, an object needs to be deleted and then added again following all the necessary steps (HU-GO instructions for operations). In order service is not required: delete it (see “HU-GO deactivation” section HU-GO instructions for operations).

Ask client to confirm which one of the names is the correct one.

Check by IMEI of said object in DBeaver database (see “Checking object registration status”HU-GO instructions for operations) and note the plate number name.

If the object in DBeaver database has an outdated or incorrect plate number name, delete it (see “HU-GO deactivation” section HU-GO instructions for operations).

Ask the client to delete the object from his HUGO account as well.

When you have received confirmation that the object is deleted from client's HUGO account, add object again to HUGO (see “Adding object to HU-GO functionality” HU-GO instructions for operations). Be aware that due to synch delays, you might get errors when adding the object again, wait for 30 minutes, and if problems persist open a consultation.

Send object credentials to a client so he can register it again in his HUGO account.

Make sure the object has the correct name in LCM as well.

Actions from support are finished.

In order to reenable, an object needs to be deleted and then added again following all the necessary steps (HU-GO instructions for operations).

In order service is not required: delete it (see “HU-GO deactivation” section HU-GO instructions for operations).

If there is missing data for the mentioned period, device should be troubleshooted and checked, why data was not sent. The aim would be to retrieve the records from the device, so that the route could be seen in the History and tickets could be bought automatically. If it is impossible to retrieve missing data from the device, send a reply to the notification that data cannot be retrieved. In this case we will have to send travel history of the object in Hungarian territory to Roadtax so that they could buy the missing tickets manually;

If all data for the mentioned period can be seen on TrustTrack, it means that there might be issues with TrustTrack - Roadtax API connection. For this reason GUI Incident should be created with the mentioned object and mentioned period, so that SW RnD could check the issue.

If HU-GO diff file was uploaded;

If configuration was not overwritten by the one without HU-GO settings

If device FW version is not older than 03.18.04 (if it was older, FW must be updated and device CFG with correct HUGO settings should be updated).