Skip to content
This repository has been archived by the owner on Nov 13, 2021. It is now read-only.

Releases: treolabs/treopim

3.2.3

12 Jun 13:26
665c1c5
Compare
Choose a tag to compare
Merge pull request #88 from treolabs/t-76023

76023

3.2.2

11 Jun 08:37
593f4ac
Compare
Choose a tag to compare

bug fix

3.2.1

11 Jun 08:08
749c7e5
Compare
Choose a tag to compare

bug fix

3.2.0

07 Jun 12:10
2057cb3
Compare
Choose a tag to compare

refactoring

3.1.6

06 Jun 08:47
Compare
Choose a tag to compare

Update dependencies

3.1.5

06 Jun 08:06
Compare
Choose a tag to compare

TreoPIM 3.1.0 is now released and available for download.

Major Changes

The modernized catalog functionality is introduced: now a catalog is a container for your products arranged by certain criteria, i.e. it is a set of data at a given time compiled to be transferred via certain channels.

Enhancements

  1. Channels are now linked directly to the product.
  2. Products have a mandatory "Catalog" field.
  3. Each product is unique within the catalog.
  4. A catalog is now duplicated together with all its products. If you need to create a new catalog on the basis of the existing one, open the desired catalog and click the "Duplicate" button. Also the product duplicating functionality is improved, i.e. a product can now be completely (100%) duplicated.
  5. When a catalog is deleted, so are all products related to this catalog.
  6. You should select a root category (or categories), which means that all catalog products may have only those categories that are related to the selected category trees. On the other side, for products you can select only those categories that are related to the catalog.
  7. Categories have either Global or Channel scope, which is defined on when the category is being created or edited on the product detail view page. For the Channel scope, you should also select channels for the desired categories. When adding a category to the product, you can assign this category to one or all channels and define its transfer via export or any other means of communication.
  8. Attributes have either Global or Channel scope, which is defined on when the attribute is being created or edited on the product or product family detail view page. For the Channel scope, you should also select channels for the desired attributes. The Channel Attributes panel is removed, so now there is only one Product Attributes panel on the product page. By default, an attribute has a scoping. The uniqueness of the records is checked at the scoping and channel level. The ability to create either Global or Channel attribute is introduced.
  9. The ability to filter your products by scopes (Global or selected channels) is added to the product detail view page. Now you can select a desired channel in the filters list to display only the items (attributes, categories, etc.) related to the selected channel.
  10. Due to the well-developed migration architecture, your upgrade from 2.x to 3.1 will be done smoothly, i.e. your previous architecture of the existing data will transfer into the latest version with no problems ensuring the migration of all necessary data.