as you should know, a Hardware-Reset happens within the PCAN-Basic only at CAN_Initialize. If while communicating, a bus error occurs then the only way to reset a hardware is re-initializing the used channel (calling CAN_Uninitialize and then calling CAN_Initialize again).
Until the version 1.2.2, a reset was issued only if there was no other application (a PCAN-View, for example) connected to the same channel. This was so because a reset can disturb any communication being done from the other application. In this case, if your application causes any bus error, a PCAN-View connected to the same channel would prevent your application from doing the reset.
Beginning with the version 1.2.3 the behavior of this reset is different. Now it is done even if another application is connected to the channel, if the status of the bus is other than OK (bus-heavy, bus-off, etc).
The decision for changing this was taken because the most of you use the PCAN-View for checking and/or monitoring the communication being done using your own software...
.. and, because a bus error indicates already that the communication was perturbed, a reset wouldn't put the things worse
.