This is bound to be complex because of the asynchronous nature of the transaction calls. The ideal user experience is:
initiate transaction
sign
be notified it was submitted
know they're waiting for it to complete somehow via a spinner or something.
know what values are going to be affected.
easily see what the status is or if errors have occurred.
understand what transactions are currently pending.
The above "UX wants" will inevitably bleed into the DevExp, so I'll leave the above code sample as a starting point and we'll see where it goes from there.
Implement the Code context:
This is bound to be complex because of the asynchronous nature of the transaction calls. The ideal user experience is:
The above "UX wants" will inevitably bleed into the DevExp, so I'll leave the above code sample as a starting point and we'll see where it goes from there.