Interim fix JR52714 includes updates to JSP files related to Sterling integration. Since
not all environments are integrated with Sterling, these fixes are not automatically enabled on your
environment.
Before you begin
Install the cumulative interim fix JR59483.fep. JR52714 is included in
the cumulative interim fix.For information about
how to install an interim fix, see
About this task
JR52714 fixes an issue where an order details service call that includes the
ModificationType input parameter does not return the JSON response in the
expected format. This fix ensures that users can see order history details on the Order Details page
when side-by-side integration is enabled between WebSphere Commerce and Sterling Selling and
Fulfillment Suite 9.4.
Procedure
-
Compare and merge store-related changes that are included with this fix.
-
Go to the
Store_archivedir/Snippets/Order/SterlingIntegration
directory.
-
Open the SBSOrderDetails.jsp file for editing.
-
Locate the following code snippet:
<c:set var="orderCancelAllowed" value="false"/>
<c:if test="${not empty orderJSON.Modifications}" >
<c:forEach items="${orderJSON.Modifications['Modification']}" var="modification">
<c:if test="${modification.ModificationType eq 'CANCEL' and modification.ModificationAllowed eq 'Y'}">
<c:set var="orderCancelAllowed" value="true"/>
</c:if>
</c:forEach>
</c:if>
-
Replace the code snippet with the following code:
<c:set var="orderCancelAllowed" value="false"/>
<c:if test="${not empty orderJSON.Modifications}" >
<c:set value="${orderJSON.Modifications['Modification']}" var="modification"/>
<c:if test="${modification['CANCEL'] eq 'Y'}">
<c:set var="orderCancelAllowed" value="true"/>
</c:if>
<c:remove var="modification"/>
</c:if>
-
Save and close the file.