IBM Support

IBM Order Management 19.1 Release Notes

Release Notes


Abstract

Resolved issues for IBM Order Management, Release 19.1 and subsequent minor updates.

Content

19.1 Minor Update 3

IBM Order Management

 
Defect Case number Description
580941 Internal A security issue is addressed. For more information, contact IBM Support.
581186 TS001880862 In case of the DB2 database, incorrect error is displayed when value is larger than database column.
581478 TS002039917 An issue with displaying the db query results in IBM Sterling Database Query Client is addressed.
582004 Internal A security issue is addressed. For more information, contact IBM Support.
582057 TS002086398
In Sterling Business Center, when creating a new customer, if the length of CustomerID is more than 15 characters, it throws the following error:
"The length of CustomerID is too long for OrganizationCode generation."
Sterling Business Center now supports CustomerID up to 40 characters.
582670 Internal Unable to enter decimal quantity in backroom pick and pack screen.
582671 Internal Problem: During backroom pickup, more quantity is allowed to be picked than ordered.
Solution: Product code is fixed so that the pickup quantity can be updated only if it is less than the Max quantity.
582974 Internal For items with IS_PICKUP_ALLOWED set to N or BLANK, inventory alert records are created with Delivery Method "SHP" even when the monitor rule assigned to the item is created for only Delivery method "PICK".

19.1 Minor Update 2

IBM Order Management

 
Defect Case number Description
580896 TS001975898
Attribute drop-down list for item was showing value instead of description.
581321 TS001982337
In IBM Call Center for Commerce, the returned order details screen displays return-invoices for unrelated returns when user clicks on "Where is my refund".
581377
TS002022323
 Unable to enter decimal quantity in backroom pick and pack screen.
581550 TS002010126 IBM Order Management Knowledge Center is updated to include the information that to encrypt properties that relay sensitive data such as user IDs and passwords, user must create a custom implementation class that implements the YCPEncrypter interface. Updated documentation is available in Property management guidelines.
581747 TS002055610 Sort screen does not display correctly for pick and pack screens on mobile store.
581773 Internal
When running multi table queries, pagination does not work correctly.
581820 Internal The findInventory API input with a very high ReqEndDate causes infinite loop.
582190 TS002102814
When a sales order is created and the order is shipped and if the invoice is generated but the amount is not collected, the Invoice details screen does not correctly show the balance amount correctly.
582247 TS002120852 In Sterling Business Center item details screen, the Long Description field now supports 500 characters instead of 200 characters.
582339 Internal
Order does not move to scheduled status when the user performs the following steps:
1. Create an Order with one order line with quantity, say 40.
2. Make sure all 40 quantities are available at 40 different nodes.
3. Call scheduleOrder API.
This issue is now resolved. Order moves to scheduled status when user performs these steps.
582411 Internal Added the url pattern for Cognos authentication servlet to IBMID exclusion in web.xml.
582428 Internal The yfs.ubx.endpoint.auth.key property is no longer database-managed.
582511 TS002131770 Corrected the REST API URL used by agent dashboard for default HTTPS port.
582542 Internal Modified validation for web.xml to support certain URLs in ibmid webxml entries.
582560 Internal Added a new validation that prints a warning to console if any custom servlets are found in custom web.xml. This validation is run when customizations are exported from Developer Toolkit, similar to property and log4j  validations.

19.1 Minor Update 1

IBM Order Management

Defect Case Number Description
579778, 580966 TS001928003, TS001892989
Problem:The ExpectedShipmentDate and capacity consumption are not updated correctly when the following steps are performed.
 
Configuration:
1. Application Install locale/timezone is UTC (GMT+00:00 and node say, NODE1 locale/timezone is PST (GMT-07:00).
2. NODE1 has a working calendar of 08:00 to 22:00 and end of shift is enabled.
3. Inventory capacity is defined for NODE1.
 
Steps:
1. Current working date and time at NODE1 is 2019-03-01 21:00.
2. Create an asap order for an Item at NODE1.
3. The ExpectedShipmentDate for order at NODE1 on scheduling is 2019-03-02 22:00 and capacity consumption is recorded for date 2019-03-03.

Solution: To see the change in behavior for ETS and capacity consumption when node locale/timezone is different from Install locale/timezone, perform the following steps:
1. Set the "yfs.useNodeLocaleTimeForCapacityCheck" property to true.
2. Create a slot group with non-overlapping slots which are in sync with Node working hours (08:00-22:00).
3. Create Inventory resource pool with defined slot group.
4. Upon scheduling, orders for NODE1 will have ExpectedShipmentDate and capacity consumption based on Node working hours as per Node locale.
581134 TS001981311 The getInventoryReservationList API fails with Null Pointer Exception when an item does not exist in the system.
578983 TS001695479 Invalid date error is displayed when a user performs the following steps:
1. Creates a locale with country code as "GB" and language as English ("en").
2. Creates a user with locale created in step1.
3. Logs in to the Application Console with the user created in step 2 and navigates to the Alert Console.
4. In the Alert Console,  enters date in the dd/mm/yyyy format and presses Enter.
581730 Internal Null Pointer Exception is thrown when disabling transaction cache for an Entity.
581151 Internal
Capacity updates are determined when promising APIs are called in an update mode. For example, reserveAvailableInventry and ScheduleOrder APIs. The existing behavior is to update the capacity as soon as the change is determined during processing. When an update in capacity is required, lock is obtained for resource pool consumption during this calculation and is released only with transaction commit. Due to this behavior, other process that requires an update capacity for same resource pool used to wait for long time.
581506 TS002048913 Updated the email address lookup for first time login using IBMID and the email address stored in YFS_USER to be case insensitive. Email address is always stored as lowercase now, and changed to lowercase before comparision for lookup.
581612 Internal Removed the console errors in the front end and added proper error messages for server side errors apart from invalid query.
576505 TS001563534
The multiAPI call with get and modify API fails and throws the  "java.lang.IllegalStateException" error when the transaction cache is enabled for a particular entity.
581711 TS002069434 1. Invalid input error is made more generic, to accommodate errors which require checking the server logs.
2. JSP input exception pop-up throws the error action coming from the server directly to the user.
581352 Internal If a query on the standby database is rejected due to it being a HADR standby database, the Database Query Client tool runs the queries on the primary database. This behavior occurs when a query that contains a CLOB or BLOB column is run.
580987 TS001964570 The catalog index build fails intermittently when the agent is run with multiple threads.

19.1

IBM Order Management

Defect Case Number Description
576226 TS001870907

The IBM Order Management application is enhanced to avoid queries to the YFS_CUSTOMER_CONTACT table for normal users (who are not customer contact users) while applying access filters as part of data security.

For more details, please refer to the What's new topic in product documentation.
574947 TS001366496
Problem: Users need a unique identifier to track and record asynchronously closed payment transactions.
 

Solution: PaymentCollection user exit output object is enhanced to accept asyncRequestIdentifier when a transaction is closed asynchronously. This identifier can be passed in the recordExternalCharges API input to record the response for the original transaction for which the response is getting recorded.

AsyncRequestIdentifier must be passed along with ReducePendingAsyncronousAmounts as Y in the recordExternalCharges API input to store AsyncRequestIdentifier against the newly recorded transaction, and to reduce the requested amount on the payment method. A response for an asynchronously closed transaction must only be recorded once in the system. Trying to call recordExternalCharges twice for the same AsyncRequestIdentifier will record the duplicate transaction in yfs_charge_transaction, but the corresponding requested amount on the payment method will not be reduced.

AsyncRequestIdentifier is an optional attribute, if NULL or not passed the recordExternalCharges will not store AsyncRequestIdentifier against the payment transaction.
577404 TS001654917
When a french locale user logs into Call Center for Commerce application and tries to cancel partial qty from an order line, "invalid format" error message is displayed.
575871 TS001179366

If a user with @ in the userid tries to login to SMA UI, the user was not able to view any menus.
579331 TS001861309 Added a new UCD process "Purge Configurator Repository"  to enable SI users to clear or purge the contents inside models, rules, tenants, extensions and properties. This process purges or deletes contents of the configrepo directory from the cloud environment.
579332 TS001861316 Added a new UCD process "Export configurator repository" to enable SI users to copy the contents of the configrepo directory from cloud environment to drop server.
579335 TS001861335 Added a new UCD process "Import configurator repository" to enable SI users to import the configurator repository from drop server to cloud environment.
579338 TS001861346 The existing UCD process is fixed to configure swagger for Omni-Configurator application. It allows connections to the configurator Swagger URL using localhost.
579340 TS001773592
The Java SDK not included in the WebSphere Liberty docker image that is used for deploying Visual Modeler application.
578558 TS001816121 Property Pool tab in the debug window lists all the properties initially, but it disappears when a selection is made.
579343 TS001944354 To access IBM Field Sales (IFS) UI, navigate to https://<servername>:<portno>/ifs.
579347 TS001945334 Introduced a new UCD process "Update Visual Modeler" to enable SI users to update the Visual Modeler application with customizations.
579349 TS001950361
Following UCD processes are added:
 
  • Purge configurator repository - Process to remove models and rules. You can select if you want to remove rules or models or both. The process will remove the rules or models from the IBM Order Management cloud configurator repository.
  • Export configurator repository - This process exports the contents of the configurator repository (models, rules, properties, tenants, and extensions) to your drop server location /home/ClientID/{env_name}/configrepo. You can choose what you want to export. {env_name} can be replaced with the name of the target environment where the process is run from. If you run the process from DEV environment, the files are copied to the /home/ClientID/dev/configrepo directory. If you want to export models from one cloud envirnment to another, run this process followed by the Import confgurator repository after copying the repository to the correct location on the drop server.
  • Import configurator repository - This process imports the configurator repository from drop serve to the IBM Order Management cloud environment. You need to create a folder structure similar to /home/ClientID/{env_name}/configrepo folder and store the models, rules, properties, tenants, and extensions directly inside this folder. {env_name} can be replaced with the name of the target environment where you want to import the repository. You can choose what you want to import. You also have an option to restart the server for the changes to take effect.
  • Update Visual Modeler - Use this process to update the Visual Modeler with customizations. You need to package the customizations from your local environment inside the projects folder <VM_SDK>/projects/<project_name> as a JAR file.
NOTE: You must not have the <project_name> folder as the root folder in the JAR file. The UCD process extracts the JAR file directly in the <VM_SDK>/project/<project_name> directory.
579352 TS001944327 Added a new UCD process "Import configurator repository" to enable SI users to copy the ddm-config.xml file to the configrepo/tenants/<tenant_code> directory from drop server to the target cloud environment.
579471 TS001861451 The missing Cache Management APIs are added to the product.
580055 TS001867712 Problem: Visual Modeler application supported only DDM: SELECTION CRITERIA, which has a limit of 240 chars.

Solution: Product is enhanced to support multiple "DDM: SELECTION CRITERIA" such as "DDM: SELECTION CRITERIA 1", "DDM: SELECTION CRITERIA 2", and so forth. Using this approach we support unlimited characters.

NOTE: The Visual Modeler UI only shows "DDM: SELECTION CRITERIA" property, other properties must be added as per the requirement.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PEW","label":"Sterling Order Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
01 November 2021

UID

ibm10959801

Page Feedback