IBM Sterling Order Management 20.1 Release Notes

When many concurrent requests are made to REST APIs in IBM Sterling Order Management, slowness is observed due to contention on the YFS_USER_ACTIVITY table. This contention is because, during authentication of REST APIs, the record in the YFS_USER_ACTIVITY table that corresponds to the supplied token is updated to prevent token expiration due to idle timeout.

Solution:  A new absolute token timeout is introduced for REST API calls. This is applicable for standard authentication where the token is passed in the request. When an absolute token timeout is enabled during authentication, token validity is calculated based on the configured absolute token timeout. Thus, there is no need to lock the corresponding record in the YFS_USER_ACTIVITY table.

1. Use the following xapirest property to configure token timeout in milliseconds for a specific user that is used to make the REST API call.
   servlet.token.absolute.timeout.<userid>=
   
   The absolute token timeout value is not set by default. To enable the token timeout value, you must set it as greater than zero.
2. Use the following xapirest property to configure global token timeout in milliseconds for all users that are used to make the REST API call.
   servlet.token.absolute.timeout=
   
   The absolute token timeout value is not set by default. To enable the token timeout value, you must set it as greater than zero. If the user-specific timeout is configured, then that value is given preference over this global timeout. 
3. To do a dummy update to the record in the YFS_USER_ACTIVITY table that corresponds to the supplied token, set the following xapirest property value to true. servlet.token.absolute.timeout.modifyrecord=false.
   
   By default, this property is set to false. Hence no updates are done to the YFS_USER_ACTIVITY record. When this property is set to true, the record is updated if a successful lock is obtained without waiting.

Demand details are not updated when multiple demand records are present for unique demand combinations.

TS002212347

The ChargeCategory, Tax, and Tax percentage attributes are required for repricing logic to compute tax changes.

Solution: Whether YFSRecalculateLineTaxUE or YFSRecalculateHeaderTaxUE user exit is implemented or not, ChargeCategory, Tax, and Tax percentage attributes are required for repricing logic to compute tax changes.

For Real-time Availability Monitor in activity mode, bundle parent is monitored at all nodes of the distribution group if the component item has an activity for any node in the distribution group.

When an order is modified such that an applied free gift rule is no longer valid, the free gift line is cancelled but the promotion is not marked as invalid on the order. In IBM Sterling Call Center, the promotion is incorrectly shown as available on certain screens.

TS003576501

1. Application Install locale or time zone is set to UTC, which is GMT+00:00 and the locale or time zone of the node, NODE1 is Chile, which is GMT-04:00.
2. NODE1 has a working calendar of 09:00 to 20:00.
3. Inventory capacity is defined for NODE1.
4. The yfs.useNodeLocaleTimeForCapacityCheck property is set to true.
5. If the current working date and time at NODE1 is 2020-04-30 08:00, and if the user calls the findInventory API with ReqEndDate="2020-04-30T23:00:00" and ReqStartDate="2020-04-30T00:00:00", the findInventory API fails to find inventory availability.

Bundle items get back-ordered when fourth integration is enabled because IBM Sterling Order Management attempts to create a temporary reservation for the parent item, which does not have inventory in fourth as it is just a logical item.

Sterling Business Center application is enhanced to support overriding of inventory capacity to zero.

In the Order Summary screen of the IBM Sterling Call Center, when the number of order lines is 10, which is the default pagination size or multiples of 10, the Next button is enabled. Clicking the Next button results in a No Records found to display error.

Solution: In the Order Summary screen of the IBM Sterling Call Center, when the number of order lines is 10 or multiples of 10, the Next button is now disabled.

1. Creates a node such as NODE1, adjust the inventory capacity, and adjust inventory for ITEM1 at this node.
2. Sets the configuration in the sourcing rule sequence that only those nodes with XX% capacity in the next Y days are considered.
3. Creates a reservation for ITEM1 at NODE1 by using the reserveAvailableInventory API.
4. Creates more reservations or orders such that the capacity cut-off criteria that is set up in the sourcing rule is met.
5. Creates an order by using this reservation for ITEM1.
6. Schedules the order. The order is back ordered.