Save and Save & Return behaviour in Add Voucher Batch screen
Refer to Product Ideas
Zendesk Ticket: https://ungerboeck.zendesk.com/agent/tickets/378532
Account: MCEC
Region: APAC
Articles used in your research: None that specifies the behaviour of Save vs Save & Return button on Add Voucher Batch screen
General
Business impact if not resolved: User believes that save & return should redirect them back to the voucher processing window
Short Summary of issue (issue description): Incorrect behaviour of save and return button
Macro Vertical: Convention Centers
Debug Environment:
Customer DB Location: Hosted
Database: QESample254
Server: Debug-Sydney,1433
Version: 25.4.9560.32366 (20260305)
V30 Link: https://qe.ungerboeck.com/25_4/app85.cshtml
User Login: nicole // nicole
Recreation Steps:
1. Log in with nicole // nicole
2. From the main menu, search for voucher processing
3. Click on Add Voucher Batch
4. Then click on Save at the bottom. Notice that you get directed to the Add Voucher window.
5. Cancel out and click on Add Voucher Batch, this time, click on Save & Return. You also get directed to the Add Voucher window.
Observed vs. Expected Results: Classic UX gives you the save and the OK button where either one will bring you to the Add Voucher window. I think that the word "Return" in the new UX is confusing users as they are expecting it to return to the voucher processing window.
What does the client want to accomplish: They are saying that it's a bug, but I think that it is the expected behaviour as it has been working this way since the classic UX.
Attachments - Video recording of me testing in both Classic and New UX
https://share.birdie.so/o/2aesWGBR
-
Ryan Ungerboeck do you have any insight on this. May need to ask Carissa to weigh in.
-
Its working as expected (as you note, we've always done this going back to v19 even) - but my guess is that they use the “Add Voucher from Purchase Order” and thus they end up closing this page all the time. v19 had both functions in the same page so it wasn't really an issue there.
I'd follow up and determine is the problem that it opens the Add Voucher page or that it doesn't open the preferred Add Voucher from PO page. -
Hi Ryan Ungerboeck After calling the customer, you are right, the problem is more around them preferring to have the add PO items to voucher option instead. 90% of their vouchers are done via PO items. I believe this would be an enhancement.
-
It would be - but I also recognize this as an annoying workflow issue.
I can see a couple of options when we consider it:
1.) An organization setting for default voucher page (easy)
2.) Detecting or allowing a preference at the user level somehow that a user usually enters vouchers from a PO (hard / risky)
-
While I'd like to have the ability at some point to bring back the workflow actions (Save and Add New / Save and ….) and make them highly usable to the users as primary actions on the pages - for the time being (recognizing that there are 2 preferred default add voucher pages) - I have added a parameter to specify this default Add page in 26.1.
Add the following in 26.1:
Application: AP
Parameter: XDAW
Description: Default Add Voucher Page
Value: PUR
PUR - Defaults to Add Voucher from PO
anything else - Defaults to standard Add Voucher
Please sign in to leave a comment.
Comments
6 comments
Date Votes