Definitions are supported on Product Catalog Group and Product Catalog with version 7.8.0.17285 and on.

Shipping Methods are still slated to get the same treatment.

Great suggestion. Definitely something we'd like to add to Ucommerce.

The LUX Framework aims to make extensibility easier and more granular than what's the case today. You'll be able to create all cockpits (like today) and new property editors at the lowest level (like today), and also add new sections to existing UIs (this is the big one).

It's all done in Angular 2 and Twitter Bootstrap 4 using Google Material Design Guidelines to make sure there's a stringent form to OOTB cockpits as well as clear guidance to app developers.

As for the timeframe, I always shy away from sharing deadlines as more often than not I end up being wrong :)

LUX is one of two main priorities for the product team. We are a few sprints and have a working prototype of the framework, which needs more core capabilities implemented like dialogs, validations, and other core services. Once done we will proceed to building PIM cockpits followed by OMS cockpits.

With the current progress the LUX framwork should be completed at the end of Q2 with the first PIM cockpits to be shipped in beginning Q4.

I have to caveat all that by saying that while the priority of LUX will not change, I cannot guarantee any of the timeframes.

Hi Al,

We are working an a brand the back-end UI, which will include a new OMS experience. Focus is on bringing everything to the client and dealing with large amounts of information.

The LUX framework is actively being worked on at the moment with first priority to ship new PIM experiences and OMS as the next priority.

I didn't notice "new orders". Read that as "orders" :)

Obvously new orders should reflect new information if the customer addresses are used.

Generally the member is used only for login from uCommerce' perspective. Address info should be stored as just that and associated with the customer object, which in turn is associated with the member profile.

Which information would you like to see reflected on the customer/customer addresses from the member and how do the changes occur on the member, e.g. changes in back-end, performed via API updates, or something different?

There's a very simple API to advance from one status to the next on IOrderService called ChangeOrderStatus. It will automatically call the configured pipeline. Your point that it should be wrapped in a task is a good one.

We're looking to create a more Google-like experience when searching in the backend meaning all fields will be searchable from a single input field. I believe this will neatly solve this.

Excellent idea. As we revamp the backend, we also look into the existing functionality of the individual foundations. I will add this to the feedback for Marketing Foundation.

Great idea! I will add it to our backlog. You don't have to wait for us to complete it though.

It's possible to add new target, which prevents a user from triggering a discount when that same discount was previously triggered by the customer.

Basically the new target would look through discount´s on previous orders and match those with the discount it is configured for. If a match is found it would opt the customer out of the discount.

Using this approach you get the behavior you're after, not just for promo codes, but for any type of discount.

Docs for building a new target is available at http://docs.ucommerce.net/ucommerce/v7.1/extending-ucommerce/marketing-foundation/add-a-new-advertise-and-act-target.html

Hope this helps.

Great idea. Will add it to our feedback board for triage.

Awesome idea. Thanks for suggesting it.

Awesome idea. Thank you for suggesting it.

I'm a little torn on this.

I'm not sure it's a great idea to allow product with no prices to be added to the cart.

On the other hand it does allow for using the cart for other purposes than straight sales.

Thoughts?

You can do this via the API today.

Here's an example of doing a "Recently Browsed Items List". The concept is similar to the wish list with the difference being that the customer is maintaining the wish list and the system is automatically maintaining the recently viewed list.

http://www.publicvoid.dk/BuildingARecentlyBrowsedItemsListWithUCommerce.aspx

Great idea. Appreciate the feedback.