Mobility Transaction Manager - inbound and outbound transactions

The Mobile Transaction Manager (MTM) is a back office function in the Toolbox. To access MTM, you must have 'MobilityCore-Adm' role in IFS or 'Toolbox' role set in the user maintenance of the Toolbox.

MTM currently shows inbound (information from M3 BE to mobile app) and outbound (information sent form the mobile app to M3 BE) transactions.

Inbound transactions:

The dispatch of work orders are currently covered in this view. You can filter the transaction list on 'user', 'work order operation', 'date', and 'status'. The details show a list of all M3BE API calls for the specific transaction. The user can further extend the view to show both input and output fields for each single M3BE API call.

Outbound transactions:

As for inbound transaction, you can filter the transaction list on 'user', 'work order operation', 'date', and 'status'. You can resend one or more failed transactions directly from MTM. The previous failed transaction will then get a 'resend' status as well as the new transaction will be displayed in the transaction list. It is currently not possible to edit the failed transaction data before resending it.

Detail view:

The detail view shows the transaction fields sent from the mobile app. The information from the mobile app transaction is converted to one or more M3 BE API calls. You can see the details of the corresponding M3 BE API calls.

For both inbound and outbound transactions, when working with API logs, you can download the complete API log to a text field format.