I was thinking if it is only me, or it is common for everyone? :-)
When I complete the order in the shop frontend - I than go back to the admin panel, find the order among other new orders in "NewOrders" folder, but when I change order status I have only 3 options, and there are 7 total folders... If I change status to "processing" the order should have moved to "processing" folder acordingly... but there is no such folder.
And basically when you have an order that you just changed the status to processing, (refresh orders node) , I can't find it anywhere, except when I eventually search for this specific order - than I find it by OrderNumber and can than change the status to whatever...
I find it a bit confusing, or it supposed to be like that? Maybe I can add more options to what new order status can be changed?
The processing order status is an internal one, which shouldn't be exposed via the interface (it's not in uCommerce 3). You can have it not show up by modifying the order status table in uCommerce_OrderStatus. If you don't want the status to show up just change the value in the "AlwaysAvailable" column to "false".
What if I want to make use of the "Processing" status? My client has a physical workflow, where the orderconfirmation is sent when and only when it's confirmed that the items is in stock. The natural thing to do is to change the status of the order from new to processing and have the pipeline send the orderconfirmation.
Does anything break if I use the "Processing" status like this? Is it significant that "NextOrderStatus" is NULL for "Processing"?
Do I have to create a new orderstatus for this purpose?
You can certainly go ahead and use the processing order status in the manner you describe. It's there to support async payment gateways like Amazon and Google Checkout.
AlwaysAvailable makes it show up in the change order status list for all statuses.
NextOrderStatus determines which status are available given the current order status, e.g. "New Order" might have status "Cancelled", "Completed", and "Requires Attention" so they each refer back to "New Order" and in turn are made available in the UI when a user changes order status in the backend.
Processing order status folder
Hello Guys,
I was thinking if it is only me, or it is common for everyone? :-)
When I complete the order in the shop frontend - I than go back to the admin panel, find the order among other new orders in "NewOrders" folder, but when I change order status I have only 3 options, and there are 7 total folders... If I change status to "processing" the order should have moved to "processing" folder acordingly... but there is no such folder.
And basically when you have an order that you just changed the status to processing, (refresh orders node) , I can't find it anywhere, except when I eventually search for this specific order - than I find it by OrderNumber and can than change the status to whatever...
I find it a bit confusing, or it supposed to be like that? Maybe I can add more options to what new order status can be changed?
Regards,
Dmitrij
Hi Dmitrij,
The processing order status is an internal one, which shouldn't be exposed via the interface (it's not in uCommerce 3). You can have it not show up by modifying the order status table in uCommerce_OrderStatus. If you don't want the status to show up just change the value in the "AlwaysAvailable" column to "false".
Here's some more information on how order status works in uCommerce: Understanding uCommerce Order Statuses.
Hi
What if I want to make use of the "Processing" status? My client has a physical workflow, where the orderconfirmation is sent when and only when it's confirmed that the items is in stock. The natural thing to do is to change the status of the order from new to processing and have the pipeline send the orderconfirmation.
Does anything break if I use the "Processing" status like this? Is it significant that "NextOrderStatus" is NULL for "Processing"?
Do I have to create a new orderstatus for this purpose?
You can certainly go ahead and use the processing order status in the manner you describe. It's there to support async payment gateways like Amazon and Google Checkout.
AlwaysAvailable makes it show up in the change order status list for all statuses.
NextOrderStatus determines which status are available given the current order status, e.g. "New Order" might have status "Cancelled", "Completed", and "Requires Attention" so they each refer back to "New Order" and in turn are made available in the UI when a user changes order status in the backend.
is working on a reply...