Creating onboarding tasks requires role-based permissions to ensure the right users can access and manage these tasks. Additionally, establishing an onboarding program is necessary for assigning specific tasks to new hires within the program's framework.

The restart feature in SAP SuccessFactors Onboarding allows administrators to restart an onboarding process for a new hire, typically when errors occur or data needs to be corrected. This feature is managed through a specific Metadata Framework (MDF) object that controls the process flow.
According to the SAP SuccessFactors Onboarding Implementation Guide:
* TheONB2Processobject (Option A) is the primary MDF object used to configure and manage the onboarding process, including the restart feature. This object stores process-related data and settings, such as the process status and conditions for restarting. Administrators can configure rules or settings within this object to enable process restarts, either manually or automatically, based on specific triggers.
Option B (ONB2ProcessTask) is incorrect because it manages individual tasks within the process, not the overall process restart. Option C (ONB2ProcessTrigger) is incorrect because it is used for initiating processes or tasks, not for handling restarts. Option D (ONB2ProcessVariant) is incorrect because it defines variations of the onboarding process, not the restart functionality.

In SAP SuccessFactors Onboarding, if no specific responsibility group is assigned to a task, the Hiring Manager is assigned by default. This assignment ensures tasks are not left unassigned and that the hiring manager takes responsibility for completing or overseeing the onboarding process.

For onboarding to be initiated, a candidate's status must be set to "Hireable." This status confirms the candidate is eligible for onboarding processes to begin, aligning with the hiring workflow in SAP SuccessFactors.

Custom tokens can be added to onboarding email templates by mapping fields in the document template to Onboarding fields, creating templates through Document Generation, and using {fieldID} format in the email content. This allows for dynamic data to be included in onboarding communications.