Description:
In order to maintain the most robust product possible, it is essential to maintain and monitor catalog entries and their changes. Similar to a change history in other popular products, there needs to be ways to track corrections.
Currently there is a tendency to view information in developer mode within the browser, but this option does not cover all information and does not provide reliable certainty about the status of a catalog offer.
It would therefore be very helpful if a debug mode could be activated for system administrators. This could be used to output the start conditions in an order process as JSON, similar to a filled spec template JSON, without actually having to send an order.
Similar to a stop indicator in a program code where the system stops and outputs information.
This would also help development to understand outputs such as GUI variables better and faster. Depending on the control required when an error occurs, this would be similar to checking an md5 sum. You get a “before/after” comparison for your offers, which can help some customers understand whether internal changes have been made.
This would also help to dispel false assumptions that updates or system peculiarities are responsible for incomprehensible situations.
Example/Use case(s):
A customer has an error during the ordering process, one of the employees may have adjusted something without seeing the effects this would have. Another employee makes an update at the same time. Now it is suspected that the update could have had an influence, but the correction is the cause. A comparison of a control JSON (before/after) would clarify that, for example, the resource pool is suddenly different and that the update cannot be to blame.