Releases: spryker/oms
5.0.0
Included commits: 4.0.3...5.0.0
Improvements
Use the new Mail bundle. Also the Locale which is used by the customer is taken into account now.
- Added commands to send order confirmation mail and order shipped mail.
- Use new Mail bundle.
- Use customers Locale.
4.0.3
Included commits: 4.0.2...4.0.3
Bugfixes
The interface for the facade was missing some methods.
Since this is now the single source of truth regarding the specifications for the facade API all facade methods must be always completely covered here.
- The interface for the facade now contains all facade methods.
4.0.2
Included commits: 4.0.1...4.0.2
Bugfixes
The legend for the OrderItem matrix mentions <1d | 1d-7d | >7d
, but in fact the items for exactly 1 day where included in the first column.
- The one second leap was fixed so the matrix and the order item overview page are in sync now with the legend for those rare cases of exactly "one day" in the past.
4.0.1
Included commits: 4.0.0...4.0.1
Bugfixes
Fixed issue with transitions between different (sub) processes. It does not throw an exception anymore.
4.0.0
Included commits: 3.0.9...4.0.0
Adds availability handling in OMS. When item is in state with reserved
flag it tracks reserved item quantity.
Added new extension point (plugin) ReservationHandlerPlugin
which is triggered when item moves to state with reserved
flag.
3.0.9
Included commits: 3.0.8...3.0.9
Bugfixes
So far Process::getManualEvents()
only contained the real manual=true
events. They did not include the onEnter=true
ones, which can lead to problems if the latter are not moved forward due to errors or exceptions. They become un-triggerable and must be manually reset from the database level.
- All "on enter" events now also get a button for manual trigger in case something goes wrong and they need to be manually re-triggered.
3.0.8
Included commits: 3.0.7...3.0.8
Bugfixes
A regression with event triggering was introduced with the last release. Only the last subgroup was triggering the following events.
- All processed items will now get merged back together again and run into the following event trigger.
3.0.7
Included commits: 3.0.6...3.0.7
Warning
This contains a regression. Please use 3.0.8 instead.
Bugfixes
The CommandByOrder items were not all moved forward as expected. Only the primary item was. This is a regression from the last patch release.
- The stack of items returned by the command is now always the same one as going into the command for CommandByOrder cases. This resolves the regression.
3.0.6
Included commits: 3.0.5...3.0.6
Warning
This contains a regression. Please use 3.0.8 instead.
Bugfixes
When multiple items with CommandByItem commands are moved and one threw an exception all were reset.
- Now only the failed ones will be reset, the successfully processed ones will be moved forward as expected.
3.0.5
Included commits: 3.0.4...3.0.5
Bugfixes
- Fixed state machine lock scaling issue, instead of just the string a hash is used to avoid length issues.
- AbstractSpyOmsStateMachineLock entity was extending wrong base entity and now extends the correct one.