This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| 6000_case_study:0400_configuration:0700_operations:1200_reserve_item [2022/08/21 22:47] – removed - external edit (Unknown date) 127.0.0.1 | 6000_case_study:0400_configuration:0700_operations:1200_reserve_item [2026/08/13 00:55] (current) – ↷ Links adapted because of a move operation localdev |
|---|
| | [<10>] |
| | ====== "Reserve Item" operation ====== |
| | |
| | This operation is very similar to the "[[6000_case_study:0400_configuration:0700_operations:0900_borrow_items|Borrow Item]]" operation. The ''ReserveItem'' operation will be invoked from the following screens: |
| | |
| | - When a member is being edited and a user sees the form of the member |
| | - When an item is being viewed/edited and a user sees the form of the item |
| | - When the "Item" query has been run and a user sees a list with one or more items |
| | Just like with the ''BorrowItem'' operation we will need to define two processes – ''ReserveItem'' and ''ReserveItem2''. The ''ReserveItem'' process will require the Member object as process input; it will run the query to find an item and then will create the ''Reservation'' object (properly initialized): |
| | |
| | <code aim>PICK FROM Item |
| | CREATE Reservation WITH Reservation.Item=Item, Reservation.Member=Member </code> |
| | |
| | The ''ReserveItem2'' process will require the Item object as process input; it will run the query to find a member and then will also create the ''Reservation'' object: |
| | |
| | <code aim>PICK FROM Member |
| | CREATE Reservation WITH Reservation.Item=Item, Reservation.Member=Member </code> |
| | |
| | //**AwareIM**// will automatically define operations that will invoke the ''ReserveItem'' process from the Member form and the ''ReserveItem2'' process from the ''Item'' form. We will also define the ''Reserve'' operation for the ''Item'' query to handle scenario 3 above. |
| |