What's new 7.4

  • Litium 7
Litium 7.4 is a minor release to the major version Litium 7. It contains substantial improvements on web API:s, the search function and the API documentation.

Highlights

See the release notes of Litium 7.4 for a complete list of fixes.

Litium Connect

Litium connect is a webapi based framework that allows building integrations with external applications to collaborate with Litium.

 

Litium Connect.png

Some key beifits are:

  • Reduced deployment, upgrade and maintenance costs

  • Easy deployment and upgrade 

  • Ease of maintenance 

  • Applications as SaaS and Web API connectivity 

  • Applications may run on a separate process or on a remote machine 

  • Applications can be made using different technologies  

  • Can build towards a remote instance of Litium, i.e Litium need to be installed in the developer machine 

  • It is possible to build applications to Litium version agnostic 

  • Hubs: Build applications towards standard business domain contracts

 

Litium API documentation available on the documentation site

The API documentation is updated with a richer content, you can reach it directly from our docs site docs.litium.com/api-reference.

Litium Search

This will ensure that all application nodes will get the exact same result for the same search query and will remove the possibility that the search index for each application will get out of sync. Litium Search is powered by Elasticsearch.

Admin web API 

The Admin web API is built to perform update, delete, create actions on all enties in the domain.

Permissions in PIM 

The feature will result in a better control of who can get access to products, categories and make changes. It is s also possible to limit which products are shown to specific user groups on the public site.

Swagger API Docs

Allows the development team to visualize and interact with the API’s resources without having any of the implementation logic in place. Read more here.

Breaking changes in how two way relationships are managed

Due to the complicated nature of batch processing two way links between entities, we have made changes on which entity owns the link. Instead of the two entities keeping track of the link, it will be limited to only one of them. These links became complicated in batch processes where we modify both end of the entities, for example when we modify a BaseProduct and a Category that has link to each other in the same batch, both sides will be tracked thus causing the error.

  • Person <-> Organization: It will be the Person that "owns" the link and will have that pointer.
  • BaseProduct <-> Category: It will be the Category that "owns" the link and will have the pointer. If you have write permission to the category you can place the base product in the category.
  • BaseProduct <-> ProductList: It will be the Product List that "owns" the link and will have the pointer. If you have write permission to the product list you can place the base product in the product list.
  • BaseProduct <-> Price list item <-> Price List: Price lists item should be it's own main entity on the same way as inventory item with inventory item service.

Note! Category and Product List will be exceptions of the rule that the child will owns the relationship.

Breaking changes in how to create custom panel

The system no longer supports custom panels written in WebForms. Please refer to how to create custom panel article for more information.

Breaking changes in how to create custom widget

The system no longer supports custom widget written in WebForms. Please refer to how to create custom widget article for more information

Removed features:

Web log

Updated   2021-05-28