IMPORTANT Actions and Considerations
The following are important actions and considerations to review for 26B:
- Expose Vendor Name in Purchase Order UI
- Unreferenced Legacy Groups from Reason Code View - Assign to Groups UI
- SaaS App - Support OAuth token for ERP Cloud
- Deprecation of SSH-Based RF
EXPOSE VENDOR NAME IN PURCHASE ORDER UI
We have introduced a “Vendor Name” column on the Purchase Order header UI. You can now search for the corresponding purchase order by Vendor Name.
UNREFERENCE LEGACY GROUPS FROM REASON CODE VIEW - ASSIGN TO GROUP U
The following legacy groups are now unreferenced from the Reason Code View - Assign to Groups UI and are removed from the Groups field LOV:
- INVENTORY_LEGACY
- WAVE_LEGACY
- INBOUND_LEGACY
- OUTBOUND_LEGACY
SAAS APP - SUPPORT OAUTH FOR ERP CLOUD
Today, the ERP Cloud SaaS app uses username and password login. In 26B, we’ve enhanced our system to switch to OAuth, so that the API can call Fusion APIs directly with OAuth authentication.
Authentication Logic for SaaS App "ERP_CLOUD": If App Parm3, App Parm4, App Parm5, and App Parm8 are populated, the system will use OAuth Authentication. Parameter Definitions for OAuth :
- App Parm3 - Client ID
- App Parm4 - Token URL
- App Parm5 - Scope
- App Parm8 - Client Secret
DEPRECATION OF SSH-BASED RF
Starting in January 2026, new customers will not be offered SSH-based RF. Redwood Mobile WMS is the replacement. Even now, all new customers are being encouraged to use Redwood Mobile WMS from the beginning.
Existing customers can continue to use SSH based RF for a further year. It will be retired starting January 2027 per the following schedule:
- January 2027 – Cohort 1 customers
- April 2027 – Cohort 2 customers
- July 2027 – Cohort 3 customers