1 Feature Summary
Column Definitions
-
Feature: Provides a description of the feature being delivered.
-
Delivered: Identifies whether the feature is Enabled or Disabled upon initial delivery.
-
Scale: Identifies the size of the feature. Options are:
-
Small: These UI or Process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
-
Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
-
- Customer Action Required: You must take action before these features can be used. these features are delivered disabled and you choose if and when to enable them.
New REST API to Abandon Jobs which are Stranded [BDI]
A new REST endpoint to resolve stranded jobs has been added to the Job Admin App. The resource path is:
http://<job-admin-host>/rms-batch-job-admin/resources/batch/jobs/resolve-stranded-job/{jobExecId}
This API can be used to mark a stranded job to ABANDON status. This is helpful in scenarios when a job gets stranded in Running status and when the user is not able to run another instance of the job.
Note that only jobs in the state, Started or Starting, can be marked to Abandon.
Retain Post Deployment Changes in the Application [BDI]
BDI upgrades in the Cloud environment will now retain all the post deployment changes made by the customer. All the changes are retained and forward ported if you choose to upgrade from previous versions.
Auto Purge Batch-Infra [BDI]
This enhancement is to automate data deletion from BDI batch Infra tables. In previous releases, the purging of data from BDI batch infra tables is a manual process which requires either table truncation or a purge script to be run manually on the database to clear older data.
Receiver Services Upgrade [BDI]
Receiver Services have now been upgraded to address the following:
-
Accept JSON as an input
-
DataTransmitter to send JSON to Receiver Service API
-
Backward compatibility of Receiver Service and DataTransmitter
Automated Pre-configure Default Security [DDS]
Dynamic Data Service requires security credentials to be configured to use it with schemas/tables.
Below are the changes introduced as part of this enhancement.
-
A new button named "Initial Security Set up" has been added in the “Designer” tab. This functionality configures access levels, access level permissions, security groups and table level securities for the selected schema.
-
A button click invokes the REST endpoint to set up default security configurations.
-
The Navigation Tree in the "Designer" tab is loaded with available tables if initial security set up is successful.
-
The default configurations that are set up via "Initial Security Set up" can be viewed/updated from the "Admin" tab.
-
This feature is enabled only for Admin roles.
New Service API and UI Feature [JMS console]
The JMS Console API is enabled now to Delete or Drain.
-
The new service, ManageJmsService, has been introduced to drain messages and delete the subscriber.
-
The drain functionality already available in the UI is now also available through the API.
Business to Put any Special Logic on Naming Convention for Sites [RFI]
Currently CFIN limits VENDOR_SITE_CODE length to 15 characters while RMS allows 240 characters for the description of the supplier site. This limits the business to put any special logic on the naming convention for sites. To address this limitation, this release includes a configurable option in RFI to SWAP 'VENDOR_SITE_CODE' with 'VENDOR_SITE_CODE_ALT'. Both the fields in RMS are 240 characters. RFI truncates a description which exceeds 240 characters. Also, it addresses SUPPLIER_SITE_NAME_XREF while swapping this value so that other interfaces do not face an issue.
Retain RFI Configuration during Upgrades [RFI]
This functionality enables RFI configurations to not be overwritten during upgrades. In previous releases, it required manual efforts to update configurations each time the RFI application was upgraded to its next available patch.
Locking Mechanism to Prevent Concurrent Execution [RFI]
The application now uses a locking mechanism to prevent the concurrent execution of timers from two or more processes.
-
By providing an option in the RFI application, such that two separate processes on different nodes/pods do not processes same data, data is not duplicated for downstream applications.
-
The status of adapters will be consistent across all the instances of the RFI application. For example, if a supplier adapter is stopped in one instance, in all other instances of the RFI application, none of the threads proceed further and execute supplier service. This functionality applies the same way for all other adapters.
Consistent Properties across Instances [RFI]
The RFI application properties changed in any instance are reflected in other running instances. Any new instance started afterwards picks already existing properties file from running RFI application instances.
RFI in CFS Supports High Availability [RFI]
The RFI application can run as multiple replicas in CFS. This enhancement in RFI handles concurrent data processing on different nodes/pods. A locking mechanism has been incorporated to prevent data contention and duplication.
New Diagnostic Tab in UI [RFI]
To ensure connectivity from RFI to external systems integrated with RFI, this enhancement was developed to provide a ping that checks connectivity from RFI to other systems integrated with RFI.
The new feature includes:
-
An added Diagnostic tab in the RFI UI which enables the ping to web services consumed by RFI.
-
A listing service name, wsdl URL, user alias , ping button and ping status for each web service.
-
Ping All and Reset buttons to ping all listed services and reset previous ping statuses.
New Manage Configurations in UI [RFI]
The RFI web application provides an option/UI to update the RFI Manage properties at run time. This enhancement provides the following:
-
A new UI - RFI Manage Configurations for customers
-
Provision to update the connection details for external application/services URLs (for example, to update the hostname and port).
-
Provision to update the security details for external application/services (for example, to update the username and password for an alias.
New System Configurations in UI [RFI]
The RFI web application now provides an option to update RFI System properties/configurations except Service URL Configuration and corresponding credentials. The RFI System Configurations screen provides option to edit some RFI properties/configurations. Without this UI, editing these system configurations must be accomplished from the backend and requires a server restart. The RFI System Configurations is available as a new tab under Manage Configurations.
The Configuration includes the following:
-
Auto Purge delay (CFIN)
-
Mailing Address list
-
Scheduler Invoice entry timer interval
-
Scheduler RMS Account entry timer interval
-
Scheduler REIM Account entry timer interval
Options for Users to Select/Update Policies for RFI Service [RFI]
The RFI web application introduced a new option to update policies for Service URL Configurations. Without this option, editing the policies must be accomplished from the backend and requires a server restart.
A new dropdown labeled 'New Security Policy Name' with policies (only policyA and policyC are valid for RFI) is available under 'Update Connection Details’.
Support Initial Load of Suppliers from Financials System [RFI]
The RFI web application introduced a new option to load suppliers exported from CFIN to the RFI stage tables. Previously, this was accomplished through shell scripts, which uses sqlplus to load data. This enhancement provides a UI option to upload supplier files and processes it and loads suppliers into RFI stage tables.
RIB-EXT on CFS is Highly Available in CFS [RIB]
By default, the CFS rib-ext application is configured to run with two replicas (pods). This number can be increased. Any request to the rib-ext-admin-gui will be served from rib-ext-ms-pod-0. All message subscriptions on rib-ext is through the subscribing adapters on rib-ext-ms-pod-0, only to prevent message duplication. This does not impact the way customers external systems call rib-ext, The loadbalancer URLendpoint does not change.
Retain RIB Configuration during Upgrade [RIB]
This enables RIB configurations not to be overwritten during upgrades. Previously, upgrades required manual procedures to update configurations each time the RIB application was upgraded to the next available patch.
Poison Messages in CFS [RIB]
This enables RIB Poison messages to be displayed on the RIB admin new sub-tab "Poison Messages " under RIBLogs tab that displays poison messages. This tab displays poison message files that are not processed (.xml), processed (.processed) and that need human intervention (.humanwork flow). This is a new feature added to process/retry the poison messages.
Upgrade Friendly Multi-Channel Configuration [RIB]
This is an independent utility that generates all the changed files needed to enable multi-channel configuration for RIB.
RICS Applications Repaving [RIB]
RIB displays UI alerts in all RICS web apps for the next upcoming repaving. The functionality allows for the display of repaving alerts in all web apps, so that the user can know of repaving in advance. Repaving UI alerts can warn users of scheduled outages. The UI alerts starts displaying 30 minutes before the scheduled outage by default. The user can configure repaving alert lead time in RIB, BDI and RFI applications.
Re-authorization to Stop Shipment for the Orders [USM]
This enhancement is to stop shipment for the orders specified in the RIB request. As part of ReAuth, at USM, whenever such message types are received, it gets an order id from WMS for customer order number provided in the RIB payload. It then sends a request to WMS with the stop_shipment flag set for the order id returned in the above step.