On the Orders View screen all orders are fetched/displayed based on the date criteria the user has selected e.g. A user selects ‘Today’ on the New Orders group and they are presented with all orders from today. That’s fine in a lot of cases but if Today I had for example 2000+ Orders then the fetch from the database is painfully slow and slows uCommerce down for all backend users.

I would like to suggest adding pagination which allows the user to choose how many orders per page they want to see and allow them to paginate through the pages.

Should be a very simple feature to introduce with big benefits.

Currently, all methods on the TransactionLibrary have signatures with a gazillion primitives. Yet several (all?) build a message object and push it through a pipline, and then does a few infrastructural things like assigning associations and saving.

I'd really like to just pass the message object already instead of passing primitives. Even with our own view model, it'd be easier to use AutoMapper for instance instead of passing each and every property. Not to mention mind which ones we actually use. (What's all these nulls in that method call?)

An example would be EditBillingInformation. I'd really like an overload where I can just pass the AddAddressRequest object. It'd be fine if the method assigns the existing address and purchase order. Or even separate those two "infrastructural bits" from the concrete "message" or "command".

(Ref. Clean Code, Refactoring & other nice books - more than three arguments for a method is too many. Refactor them in to a parameter class. ;) )

Hey guys, we are dealing with a problem here while trying to edit/remove product definitions:

1. Go to Commerce Settings / Product Definitions and create a new definition
2. Go to sitecore Content Editor and check for the two new templates that were created just fine.
3. Then we try to edit those templates by updating the layout and/or sub-layouts at the standard values item and save the changes.
4. Then open up the presentation/details again and you will notice no changes at sight, meaning no changes were saved.
5. Then go to the commerce settings/products definitions again and remove the new created item there.
6. Then go back to sitecore content editor and you will see the two templates are still there.
7. Then try to remove them manually and you will notice nothing happens.

So wondering if it could be something going wrong with unicorn or is there something else?

We are working with:

- Sitecore.NET 8.2 (rev. 161221)
- uCommerce-for-Sitecore-7.5.0.17040
- Latest code pulled from https://bitbucket.org/uCommerce/avenue-clothing-for-sitecore

Any thoughts?

Thanks,
Ruben.

I’m adding a bit of workflow to the order statuses in a shop.
I was positive there was a few built-in tasks, but I can see I made my own the last time I did this.

Is there really no “ChangeOrderStatus(newId)” or “AdvanceStatus” tasks to just re-use in the castle config?
Would that be a nice addition to the built-in tasks to pick from?

The current process is:
“New order” to either “Processing” or “Changed”.
When “Changed”, the system sends n e-mails, and moves the order back to “Processing”.
This could’ve been set up easily with two bundled tasks, one which we have:

<!-- Need this one -->
<component
id="ChangeStatusTo.Processing"
service="UCommerce.Pipelines.IPipelineTask`1[[UCommerce.EntitiesV2.PurchaseOrder, UCommerce]], UCommerce"
type="UCommerce.Pipelines.Orders.ChangeStatus, UCommerce.Pipelines">
<parameters>
<newStatusId>2</newStatusId>
</parameters>
</component>

<!-- example -->
<component id="ToChanged"
service="UCommerce.Pipelines.IPipeline`1[[UCommerce.EntitiesV2.PurchaseOrder, UCommerce]], UCommerce"
type="UCommerce.Pipelines.Transactions.Orders.OrderProcessingPipeline, UCommerce.Pipelines">
<parameters>
<tasks>
<array>
<value>{{SendEmail.Changed}}</value>
<value>{{ChangeStatusTo.Processing}}</value>
</array>
</tasks>
</parameters>
</component>