SAP Knowledge Base Article - Public

3768201 - Values Entered in Offboarding Custom Tasks Are Not Populated in Offboarding Forms - Onboarding

Symptom

Customers configure custom fields in Offboarding custom tasks and map those fields to Offboarding forms used in an e-signature process.

After completing the custom tasks, the expected values do not populate the mapped fields in the generated Offboarding forms or documents. As a result, the documents may display blank fields even though the information was entered in the custom tasks.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental. 

Environment

SAP SuccessFactors Onboarding

Cause

The system design supports mapping custom task fields to Onboarding and Offboarding forms for e-signature scenarios. However, Offboarding has a process sequencing limitation.

In Offboarding, the Document Flow step cannot be configured after the Offboarding Tasks step in Process Variant Manager. Instead, Offboarding Tasks and Offboarding Documents are triggered in parallel.

Because of this behavior, the Document Flow is initiated before the custom task data is available, preventing the mapped values from being transferred to the generated documents.

The following process sequence is supported:

  • Offboarding Tasks can be executed after Document Flow.
  • Document Flow cannot be executed after Offboarding Tasks.

As a result, using data captured in Offboarding custom tasks as the source for Offboarding document generation is subject to this process limitation.

Resolution

This is currently a product limitation in Offboarding.

Currently, Offboarding documents and Offboarding tasks are designed to execute in parallel and do not provide the same sequencing capabilities available in Onboarding.

While Onboarding supports scenarios where data collected during tasks can be reliably used during subsequent document generation steps, Offboarding is not currently designed to provide the same functionality.

Workaround

A possible workaround is to redesign the process variant to indirectly force the Document Flow to occur after Offboarding Tasks.

Example Configuration

  1. From the Start trigger, configure:
    • Review Offboarding Information
    • Offboarding Tasks
  2. Configure the Document Flow step to be triggered from the Review Offboarding Information step.

Important! For this workaround to succeed, users must ensure that all Offboarding Tasks are completed before the Review Offboarding Information step is completed.

If the Review Offboarding Information step is completed first, the Document Flow will be triggered before the task data is available.

Enhancement Requests are already submitted for this subject! You can vote in these enhancements following the link to the Influence Portal: SAP SuccessFactors Onboarding - All Requests

See Also

Keywords

Values, Entered, Offboarding, Custom, Tasks, Not, Populated, Forms, Custom, Data, Collection , KBA , LOD-SF-OBX-OFP , Offboarding 2.0 , Problem

Product

SAP SuccessFactors Onboarding all versions