Test Report:
Task 1:
.) Tested different inputs, also invalid inputs (empty fields are now not possible)
.) Tested the outcome of different errorcodes which provide different default solutions
Task 2:
.) Tested the message flow between supportify system and user
.) Found that displayed texts were not intuitive (Changed text to explain better what to do)
.) It was possible that information fields were edited by the user (changed those to readonly)
Task 3:
.) The timer setting for the queue was too long at the beginning (the technical klerk had to wait till he had access to the task in the tasklist in camunda)
.) we didn´t provide enough information at the begining for the technical clerk to be able to build a customer based solution (Names were not forwarded to the technical clerk for instance)
Task 4:
We checked if all the various informations (user name, error code, default solution, error description and (if the needed) the special solution) gathered are available and then made sure it is correctly compositioned. We had some issues with the correct messaging between technical clerk and user
(had to set a business key to send to the correct user process)
Task 5:
.After some testing we found, that we didn´t give the user enough information at the end. For instance it is helpfull to show the user again the error description etc, because after some time the user maybe forgot about the error completly. (And a technical clerk may need some time to find a solution).
Because of that, we extended the presented information to the user (giving an overview over the whole process and its variables), for instance the default solution is also presented even if the technical clerk provided the solution. This is done to provide an overview for the user.
The system is working and deployed on a server.
