Just Sitecore Things

• Plugins
• Controllers and Commands
• Pipelines
• Blocks

• Independent features
• Only accepted way to extend Commerce Engine
• Don’t remove default ones just like that ;)

• Controllers works in the same way as usuall
• Commands are invoking inside the controllers
• Commands invokes Pipelines

• You can create your own pipelines and hook into pipelines defined in other plugin
• Similar to standard Sitecore pipeline mechanism
• In SXC9 they are in the code not XML
• Aggregate SXC Blocks
• Comparing to XML approach No „ShowConfig.ASPX” but JSON preview
• In Commerce, there is no config patching facilities. Instead we can create our custom plugin and can patch our Blocks through the code.
   

• Equivalent for Sitecore processors
• Chaining calls
• Remember about returning element

• Controller
• Command
• Pipeline
• Blocks

We also should remember about mentioned earlier registration piplines and blocks in the configuration classes. You will have it also below in the examples of code.

At this point we already have known general overview of ways which are possible to extend or customize xCommerce. We did extension of an entity via xCommerce composer tool. But we also have mentioned that there are ways to customize platform from code. We saw 2 main ways, by Policies and Composition, what means the best way - to create independent plugins.

Let's take a look on both of them.

At the beginning what you need is:

Sitecore Commerce Engine SDK, example:




1. Policies

By definition:

A named, versionable and variable set of data that can be used as facts within behaviors to influence behavioral outcomes. source

Policies is the simplest I think approach, but we should avoid using it. Why? Because it has an influence on internal xCommerce code, which can be changed e.g during upgrade. To have less stress and work we shouldn't touch internal xCommerce thing but extend it via composition approach.

Policies you can find in this place inside the SDK solution



Let's assume that we would like to extend our Customer entity. What we should to do is to find this entity in policies and add your custom field.


Yes, we did it! we have added a new property! Is it enough?
- Well, not exactly. We still need create a way to make it visibile outside.

But how to do that?

You still (like in a composition) create you feature project (plugin) and define there a few elements of your change. But...it's still less work than in composition. Usually, needed for you would be , command and controller. In policies like in composition approach your are adding new properties of entity as a new components. Difference is that, when you are changing policy this components are higher in hierarchy of childviews of your entity and you don't have to do much, to later gets them in Sitecore.
By composition approach those components will be buried much more lower to get it.

Now we understand that we have to think about chain of commands and controllers which uses it in xCommerce and extend those places with our custom property. Hence you have to think where you should to go to. To make it very useful is DotPeek, where you can find whole process flow.

Some custom command to make possible to get it like:



And a controller:


So we can say that xComerce part is done. Now we have to go to Sitecore side and try to receive new parameters.

Sitecore side:

Depend what your are doing, in our case it's customer so let's check registration controller which we use and would like to extend with custom fields. In our scenario is our custom controller written with some changes, which gets custom properties pushed by xCommerce in Customer component.









That's it. It's much more faster way to achieve customization of xCommerce entity - but remember that you are changing internal commerce files ! :)

Cheers!

1. Code approaches

• Composition
• Entities can be extended by adding components to the Components property on the entity.
• Components are just classes that are injected into the entity by a plugins with pipeline and blocks
• It's a independent way to add something more, without relation to other plugin or other elements.
• Policies
• In simple understanding we can treat Policy like a config or setting file in some way. You can for instance add a new field for the customer entity etc.

• DateTime
• Decimal
• Integer
• Boolean

• Manage Tags
• Link to entity
• Associate Items definitions

• Source item
• Reference item