Overview
The Approve Purchase Orders App is a typical example of the approval process. It uses the Split Screen pattern and shows a list of purchase orders and the corresponding details. Users can search for certain purchase orders and either accept or reject them. Once the purchase order has been approved or rejected, it disappears from the list.
Note: You can find the source code for the UI in your WebIDE environment. Please follow this step by step guide.
Technical Documentation
There is a detailed technical documentation available for the Approve Purchase Order App. The check out this link.
Purchase orders details | |
Purchase order details displays all necessary information about an individual purchase order the user has selected from the master list. On top of the form view the screen includes purchase order header data such as delivery details. On the lower part of the screen, the table shows all line items in the purchase order. For the user’s convenience, the number of line items is visible in the table header. All data is read-only |
Purchase orders details | |
Purchase order details displays all necessary information about an individual purchase order the user has selected from the master list.On top of the form view the screen includes purchase order header data such as delivery details. On the lower part of the screen, the table shows all line items in the purchase order. For the user’s convenience, the number of line items is visible in the table header. All data is read-only | |
Approve/reject Purchase Order | |
After selecting a purchase order and checking the details, the user can either accept or reject it.A dialog opens and allows the user to explain this decision. |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
34 | |
17 | |
16 | |
15 | |
11 | |
9 | |
8 | |
8 | |
8 | |
7 |