hotwax / receiving Goto Github PK
View Code? Open in Web Editor NEWHotWax Commerce Receiving App
Home Page: https://receiving.hotwax.io/
License: Apache License 2.0
HotWax Commerce Receiving App
Home Page: https://receiving.hotwax.io/
License: Apache License 2.0
Only Approved POs can be received. Right now we don't show the status of the PO which makes it hard to know that can and cannot be received.
There should be a badge on the end slot of the find screen with a badge that shows the status.
On the detail page, next to the internal order id badge, there should be an order level status badge.
For items, the receive all button should be replaced with a "completed" badge when the item status has changed to completed.
This feature will help the users to easily navigate through the app
Add parent product name and ERP_ID from good identifications
When using receive all for purchase order details page, if there are already shipments received for the PO, still value prefilled for quantity is the po item quantity.
When using receive all for purchase order details page, if there are already shipments received for the PO, the receive all feature should prefill quantity deducting the received shipment
Adding items to a shipment of any type should be restricted to users with "FULFILL_SHIPMENT_ADMIN" permission which is described as the "shipment admin permission."
If a user doesn't have this, they will be restricted doom using the "add to shipment" function in the ionic receiving app.
Information on the PO details page is not displayed correctly like po received qty
All the information should be displayed correctly.
0 received
should be displayed.Select two POs having same product in which one of the POs does not have any received history
received
is getting displayedUsers can currently only receive inventory for purchase orders; there is no manual control for users to close the PO. When the promise date arrives, the PO automatically expires. Manually closing a PO communicates to the system that the respective PO's inventory has been received and will not be received again.
Only users with order edit permissions can close a purchase order from the Purchase Order detail page.
To help UX developers add link to figma file in the readme me:
https://www.figma.com/community/file/885791511781717756/Ionic-5-Material-UI-Kit-(Community)
After receiving the shipment, it is still visible on the shipments page.
After receiving the shipment, it should not be visible on the find shipment page.
Clicking on the shipment item "received" chip should open up the receive history model with history for just that item.
Even though partial or all inventory has been received, the progress bar doesn't reflect that.
If a partial amount or or the entire expected quantity has been received, the progress bar should be full. If more inventory than expected has been received then the progress bar should turn to the danger color.
log into app and view a PO.
Users should be able to go back and view a shipment even after it has been received, canceled, or completed. This helps in reviewing or verifying data incase they need to be reconciled.
On the list page, all results show show up regardless of status. On the detail page, users won't be able to edit these items with clear indications that this shipment has been completed etc.
Clicking on the internal id chip on the detail page for POs should copy the content to the users clipboard.
There should also be an icon in the chip which shows that it can be copied.
warning: 'emitter' is defined but never used (@typescript-eslint/no-unused-vars) at src/store/modules/order/actions.ts:8:8:
6 | import { hasError, showToast } from '@/utils'
7 | import { translate } from '@/i18n'
> 8 | import emitter from "@/event-bus";
^
9 |
10 |
11 | const actions: ActionTree<OrderState, RootState> = {
warning: 'state' is defined but never used (@typescript-eslint/no-unused-vars) at src/store/modules/order/actions.ts:51:25:
49 | commit(types.ORDER_CURRENT_UPDATED, state.current )
50 | },
> 51 | async addOrderItem ({ state, commit }, payload) {
| ^
52 | const product = {
53 | ...payload,
54 | quantityAccepted: 0,
warning: 'commit' is defined but never used (@typescript-eslint/no-unused-vars) at src/store/modules/order/actions.ts:109:34:
107 | return resp;
108 | },
> 109 | async createPurchaseShipment({ commit }, payload) {
| ^
110 |
111 | let resp;
112 | try {
warning: 'commit' is defined but never used (@typescript-eslint/no-unused-vars) at src/store/modules/product/actions.ts:65:36:
63 | return resp;
64 | },
> 65 | async fetchProductInformation( { commit }, payload) {
| ^
66 | let productIds: any = new Set();
67 |
68 | payload.order.map((item: any) => {
warning: 'commit' is defined but never used (@typescript-eslint/no-unused-vars) at src/store/modules/shipment/actions.ts:65:26:
63 | }
64 | },
> 65 | receiveShipmentItem ({ commit }, data) {
| ^
66 | const payload = data.shipment ? {
67 | shipmentId: data.shipment.shipmentId,
68 | locationSeqId: data.shipment.locationSeqId
5 warnings found.
If the No Shipments found
toast is displayed and you switch to PO or Settings page, RangeError: Maximum call stack size exceeded
is thrown in the console.
Call stack error should not be there in the console.
No Shipments found
toast is displayed.Current readme file is not understandable. Make it similar as the readme file of preorder app https://github.com/hotwax/preorder.
When receiving at a larger warehouse style location, retailers often need to specify locations within a facility during receiving since it impacts inventory management.
When the quantity is prefilled with 0 and the user has not received the item, the quantity is passed is 0 causing action failure:
Both quantity to accept and quantity to reject cannot be zero.
Even when a shipment Id is present, it shows the HotWax Commerce generated Id on the find shipments page.
When an external Shipment Id is present, it should be visible on the shipments page.
Step to reproduce
Login to https://receiving-uat.hotwax.io/ with a valid username and password.
Navigate to the return tab.
Enter the quantity in the input field.
Expected - After entering the quantity Receiving button should be enabled.
All find screens should have dedicated empty states that show the user relevant information instead of a load more button when there is no more data to load.
When there are no more shipments to load, the current toast makes it feel like a bug. There should be no toast if there are no more shipments to load, instead it should switch to the empty state
As moment is in maintenance mode, replace moment by luxon.
https://ionicframework.com/blog/announcing-ionic-v6-1/
What's new:
Virtual Scrolling Compatibility
Sheet Modal Breakpoint API
Control When Your Modals Dismiss
Disable Specific Dates
Gesture Events for Range
Custom Item Counters
https://github.com/ionic-team/ionic-framework/releases/tag/v6.1.15
When clicking Load More Purchase Orders
on PO list page and no more jobs found then no toast message being displayed
When there are no more POs found then a toast with message No more Purchase Orders found
Load more Purchase Orders
buttonAdd autofocus on ion-inputs of all details page
When changing the qty value and receiving the PO, qty received not being updated and qty field does not reset.
PO details should be updated automatically without refreshing the page
When hosting app, we could provide specific aliases that maps to specific instance baseURL. This will ease accessing app for non hotwax domain instances
To use dxp-components to implement product Identifier.
When hosting app, we could provide specific aliases that maps to specific instance baseURL. This will ease accessing app for non hotwax domain instances
The client wants to see the Transfer Order number on the shipments Find page and the Shipments detail page. The transfer order number will be saved in the ShipmentAttribute entity.
The transfer order number should be visible on the Shipment Find page and the Shipment Detail page.
Load More Purchase Order
button and if no more orders found then there is no message displayed to the usersLoad More Purchase Orders
buttonWhen the user is receiving more than was ordered in a PO, or was expected in a Shipment, the progress bar should turn red/danger so that the user knows they are doing something unexpected.
Once search results have loaded, there is no way to refresh them without switching to another page and coming back. There is should be an option to pull and refresh on all pages.
Use the new Shopify CDN compatible image component to fetch optimized images from Shopify instead of full size images.
Currently, when showing the history for PO, then the most recent action on the PO is displayed at the bottom, but we can sort the po history list on the basis of date to display the most recent action on top, so that it will be more easy to understand.
When logged-in on a particular instance, then on purchase order page, orders gets listed if exist and then after logout and login again with some other instance, and if there are no purchase orders available then the previous PO gets displayed.
On logout the list of POs, returns and shipments should be cleared.
We have a new settings page UI pattern that should be implemented into the receiving app. Reference for it can be found here:
hotwax/import#60
Use the cards that apply, all may not apply
Add a custom theme file like in Clienteling app.
This will allow any brand to customize the look and feel of any app.
Also change heading fonts to Montserrat and body font to Open Sans
When going to the login screen and entering the correct credentials. The screen flashes and it stays on the same page.
After entering the correct credentials, users should be able to log in to their accounts.
Currently we are only showing the user id not the users full name.
Need to show the user's full name which is more user friendly and readable.
The added arrival dates on the PO find page and the PO detail page will give good information without logging into the OMS.
The PO find page and PO detail page should display the estimated arrival date for the purchase orders. If there are multiple items in a PO, the earliest arrival date amongst all should be visible on the PO find page.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.