Select TI-1966 in the “Ticket Item” look-up field;
Enter 5 in the “Return Quantity” field;
Click on the “+” to save the form;
Expected Result
The system should either:
1. Show a new form screen with the input values you have previously entered blank;
2. Once a e-form record is added, refresh the screen and take you to the summary e-Form screen;
Actual Result
The screen refreshes retaining all the input values you have entered previously, but the “+” sign is no longer present. This is confusing for the user since they are unsure if the e-form record has already been added. Also, for Weatherford, we have a validation rule which prevents users from adding a return quantity that is greater than the input – used quantity. Since the field values are not cleared when the screen refreshes, the validation rule will fire in certain conditions, making the process even more confusing.
Analysis
Matt: We need to add a “Save and Close” button to the form edit screen that would take the user back to the previous page. So for a parent form, the user would return to the “Form” creation screen with the “+” available. For a child form, they would be brought back to the place where they could initiate another child form with a single click.
The save and close addition is needed rather than changing the current save behavior because if the form has a sub form or a report template, it would require the user navigate back into the record to create a sub form or generate a report template. We want to avoid that. Save and close should just account for both cases.
Mingle Card: 6183 Steps to Reproduce
Expected Result
The system should either:
1. Show a new form screen with the input values you have previously entered blank;
2. Once a e-form record is added, refresh the screen and take you to the summary e-Form screen;
Actual Result
The screen refreshes retaining all the input values you have entered previously, but the “+” sign is no longer present. This is confusing for the user since they are unsure if the e-form record has already been added. Also, for Weatherford, we have a validation rule which prevents users from adding a return quantity that is greater than the input – used quantity. Since the field values are not cleared when the screen refreshes, the validation rule will fire in certain conditions, making the process even more confusing.
Analysis
Matt: We need to add a “Save and Close” button to the form edit screen that would take the user back to the previous page. So for a parent form, the user would return to the “Form” creation screen with the “+” available. For a child form, they would be brought back to the place where they could initiate another child form with a single click.
The save and close addition is needed rather than changing the current save behavior because if the form has a sub form or a report template, it would require the user navigate back into the record to create a sub form or generate a report template. We want to avoid that. Save and close should just account for both cases.
Related Cards
Impact Analysis
Developers: Fill in this area during code review.
Test Plan