Performing eSignature for SetValue ends with a crash

• Related Articles

• RGM: Closing RGM and then performing eSignature change causes crash

  Description In the Recipe Group Manager, it was possible to perform an eSignature value change after the RGM has been closed. This led to an unexpected closure of the Service Engine. The issue has been addressed and the eSignature value change can no ...

• eSignature screen is not opened when setvalue action is done via keyboards (e.g. SETVALUEKBD)

  Description The eSignature screen did not open when the setvalue action was performed using the keyboard. The issue has been addressed and the eSignature screen opens now as expected. To benefit from this fix: Update your zenon Software Platform to ...

• Reproducible Service Engine Crash when using eSignature

  Summary Screen with "closing frame after losing focus" set is closed although eSignature process is still running Description Screen with "closing frame after losing focus" set is closed although eSignature process is still running Issue Number: ...

• Service Engine crash after forcing eSignature multiple times in customer project

  Description The Service Engine closed unexpectedly after eSignature was forced multiple times. The issue has been addressed and eSignature now works as expected. To benefit from this fix: Update your zenon Software Platform to the latest build of ...

• WVS: Support eSignature

  The WVS now supports eSignature screens. Limitations: No temporary login No calling up of the Login screen if there is not yet a user for the eSignature signed in. Attention eSignature in WVS does not support screen type-specific actions, such as ...