We are encountering an issue where the OIC integration (OOB Accelerator - Admin Data Sync) does not properly handle slashes in work skill values when constructing the REST URL for the PutEqWorkSkills operation.
As part of an Admin Sync attempt to create WACS equipment in OFS, the following error was returned:
<ns2:APIInvocationError xmlns:ns2="http://xmlns.oracle.com/cloud/generic/rest/fault/REST/PutEqWorkSkills">
...
ns2:errorCode404</ns2:errorCode>
ns2:errorPath
<![CDATA[InboundJaxrsResponse{context=ClientResponse{method=PUT, uri=https://.fs.ocs.oraclecloud.com/rest/ofscMetadata/v1/workSkills/WE_STE-RW/STE, status=404, reason=Not Found}}]]>
</ns2:errorPath>
</ns2:APIInvocationError>
In this case, WE_STE-RW/STE is a valid WACS equipment value. However, when it is used directly in the URL path like so:
rest/ofscMetadata/v1/workSkills/WE_STE-RW/STE,
the slash is treated as a path delimiter, causing the request to break and return a 404 (Not Found).
Expected Behavior: OIC should URL-encode the work skill value before making the API call. The slash ("/") should be replaced with %2F so that the final request becomes:
rest/ofscMetadata/v1/workSkills/WE_STE-RW%2FSTE
Related SR: 3-41306552131