3744833 - Unable to route or sign performance form via api during signature step when form is not in API user's inbox

• Attempting to route or sign a Performance Management form via API while the form is in the employee acknowledgement (signature) step.
• Error message: "Form not found".
• Error message: "No form found".
• signForm API succeeds only when the form is in the calling user's inbox.

• Product: SAP SuccessFactors Performance & Goals
• Webservices, OData APIs

1. Move a Performance Management form to a signature step so it resides in a user's inbox who is expected to sign.
2. Use the signForm API using a different API user that does not have the form in its inbox.
3. Observe the API response with "No form found" or "Form not found".
4. Repeat the call with a user who has the form in their inbox and observe that the API succeeds.

This is expected behavior: the API cannot sign forms on behalf of other users.
The signForm operation imports a signature and can only be performed by a user who has the form in their inbox.

1. Ensure the form is in the inbox of the user who performs the API call before invoking signForm.
2. Do not attempt to sign or route a signature-step form via API using a user who does not have the form in their inbox; this is not supported.
3. Have the actual signer authenticate the API request or complete the signature in the user interface when the form is in their inbox.
4. Review and confirm required API permissions and limitations for Performance Management form entities as documented in the API reference.

• Refer to: API Reference: sendToNextStep (OData v2)
• Refer to: API Reference: Performance Management Form Entities (OData v2)

signForm, sendToNextStep, performance management form, signature step, employee acknowledgement, form not found, no form found, api limitation, odata v2, inbox requirement, cannot sign via api, routing restriction, PM form, SuccessFactors API, sign via api , KBA , LOD-SF-PM-API , Webservices, OData APIs , Problem