IMPORTANT Actions and Considerations

REDWOOD MOBILE ANNOUNCEMENT - 25C

WMS Redwood Mobile merges modern Redwood user interface patterns with the breadth and depth of functionality built into the RF application to give the best of both worlds to customers. In addition, it also includes a much more robust back-end architecture that is much more resilient than the old SSH-based architecture.

We are happy to announce that in a future release (currently targeted for 25D), we plan to release a published and supported Redwood Mobile API that customers and partners can use to build custom mobile applications and extensions. This mechanism is much more robust and resilient than extensions built using screen scraping technology that can be unreliable at times.

HOW THE API WORKS

The following is the general sequence of events in how such an application would work. More details will be published later.

NOTE: This API is not currently available and is targeted for 25D.

  • Customer or partner front-end screen makes a REST call get_next_rwmobile_page
  • API returns a JSON representation of the data on a mobile screen
    • This representation merely describes the fields and data in each field, along with action keys (control keys) available on that screen
    • It assumes a certain basic layout of the mobile screen which will be described later
    • It does not contain any design or rendering elements, such as CSS
  • The customer/partner front-end UI renders the fields represented in the JSON
    • CSS and other design considerations are up to the front end
  • The front-end accepts user input, whether its data typed into a field or an action key and then invokes the same API, passing in this user input
  • The sequence repeats, until the user exits the application

NOTE: The use of undocumented APIs is not supported and the behavior of such APIs can change unexpectedly at any time. Published APIs on the other hand will have a good level of backward compatibility, with any breaking changes announced far in advance, giving customers and partners time to adjust.

Authentication

The API is an lgfapi and therefore supports the same authentication methods used by other lgfapi’s, which are:

  1.  Basic auth and
  2. Oauth token based authentication with
    1. ROPC grant type, and
    2. Authorization code grant type, added in 25C

Customers can either build a login page for their mobile applications and obtain the Oauth token, or they can use the WMS login page and use SSO in combination with the authorization code grant type, if they want to avoid having their own login page.

LIMITED SUPPORT OF SCHEDULED JOBS - 'run_script' and 'run_python_script'

In continuity of your scheduled job requirements, WMS currently maintains the 'run_script' and 'run_python_script' scheduled jobs for a limited support timeframe. If you have previously used the 'run_script' and 'run_python_script' scheduled jobs, you can continue to run the same in the interim. However, the addition of new 'run_script' and 'run_python_script' jobs is not supported.

NOTE: As a part of the deprecation of legacy processes/features, the 'run_script' and 'run_python_script' scheduled jobs are planned to be deprecated in 26A.

Recommendation: Transition from the use of the 'run_script' and 'run_python_script' scheduled jobs to the available alternatives that are supported in future releases.

ERROR MESSAGE ADDED FOR lgfapi_create_access GROUP PERMISSION

POST APIs normally require create access to perform actions. This has now been enforced in certain APIs that did not enforce it in the past. Note that ADMINISTRATOR role users automatically get all permissions, so such users will not see any change in behavior. Users in lower roles that are not part of groups with the required permissions will see a change in behavior.

We have added an error message for Employee users for APIs related to pick-pack, repack, replenishment, and manufacturing. Now, when the group permission "lgfapi/lgfapi_create_access" is disabled, Employee users will receive a "PERMISSION_DENIED" error code when attempting to post to these APIs.

For users with Employee access who need to POST to APIs:

  1. Enable the the group permission "lgfapi/lgfapi_create_access."

NOTE: If the group permission "lgfapi/lgfapi_create_access" is disabled, Employee users will receive a "PERMISSION_DENIED" error code when attempting to post to these APIs.