You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While creating an order, If a User select classified delivery as an order type, buyer and seller info field should be available to him. The field will contain the buyer's/seller's name, phone no.
In case of buyer, the delivery address should be his default address.
In case of seller, the pickup address should be his default address.
There is an UserRef field on the PersonInfo class at TaskCat, not sure what value should populate this field.
Need review on this before start implementing.
The text was updated successfully, but these errors were encountered:
I think this is to be discussed when I roll out the full feature
The UserRef field:
The plan is to make an admin just use userref to populate buyer and seller info if and only if he is a user of GO! fetch. I would hopefully ignore all the other fields if you put an userref and just populate the name and everything else needed from the system automatically.
Default addresses for the order:
The plan is to use something like this.
If you create a classified delivery order you're supposed to give a from and to field (duh)
A guy can sell or accept things from different address. Its okay to have the same address now or different anyway, I wouldn't mind and I dont want really a default feature here (may be from frontend), not so much in backend.
Background
While creating an order, If a User select classified delivery as an order type, buyer and seller info field should be available to him. The field will contain the buyer's/seller's name, phone no.
In case of buyer, the delivery address should be his default address.
In case of seller, the pickup address should be his default address.
There is an UserRef field on the PersonInfo class at TaskCat, not sure what value should populate this field.
Need review on this before start implementing.
The text was updated successfully, but these errors were encountered: