Create a sub-account.
This document outlines the installation and setup for Adobe Sign for SuccessFactors using the SAP Cloud Cockpit.
Extension of SuccessFactors to include Adobe Sign requires an SAP Cloud Platform account with a NEO based subaccount AND a java compute entitlement.
The Adobe Sign for SuccessFactors integration extends SuccessFactors (SFSF) via the SAP Cloud Platform (SCP). We have an integration for Recruiting Management (RCM) that enables the sending of Offer Letters from within SFSF to a single recipient. Signed documents are stored on the Candidate Profile. All signing occurs via email notification.
The installation consists of:
1. Configuring one or more sub-accounts within SCP
2. Deploying an MTAR Solution
3. Configuring the SFSF Application Extension via SFSF Provisioning
This is a very complex setup and really should only be performed by someone with expert level experience with SCP.
When deploying to a subscriber-provider topography, only the provider subaccount is running the webapp. The subscriber account is just facilitating the connection between SCP and the SuccessFactors instance.
1. Access to SFSF provisioning (e.g. https://mysfsfdemo.successfactors.com/provisioning_login)
2. A Java compute unit
There are 2 possible deployment topologies:
With either deployment strategy, you will need to deploy the Adobe Sign MTAR file. The solution is packaged as a Multi-Target Application Archive (MTAR) and contains both stand-alone and provider/subscriber options.
More detailed documentation from SAP:
Create a sub-account.
Before deploying the MTAR, you will need to connect the subaccount to your SuccessFactors instance.
Deploy the MTAR file as a Solution.
Once deployed, the Solution will complete the installation of the Recruiting and Onboarding Tiles within your SuccessFactors instance.
Create a provider sub-account and deploy the MTAR to it.
Create a subscriber sub-account. You will need one for each SuccessFactors instance. Make a note of the “Technical Name” for this sub-account (e.g. hiwyrm997q)
From the provider sub-account, click into the solution you’ve deployed. You will see an “Entitlements” menu on the left.
Create an Entitlement by providing the global technical name of the to-be subscriber sub-account.
On the subscriber subaccount, select Solutions. You should see the AdobeSign solution as a tile under “Solutions available for Subscription”.
Before you can subscribe to the solution, you need to connect this subscriber subaccount to your SuccessFactors instance.
Click on it and then choose Subscribe. There’s no need to provide a MTAR description file. Just select Subscribe.
Once subscribed, the subscription solution will complete the installation of the Recruiting and Onboarding Tiles within your SuccessFactors instance.
Within SuccessFactors, you can now move the Adobe Sign Recruiting and/or Onboarding Tiles from “not-used” to the default.
See Admin > Tools > Manage Home Page.
For each subscriber, select the adobe sign solution and open the Entitlements option from the cockpit and press the New Entitlement button:
In the Create Entitlement panel, enter:
When done, click Save
From the Subscriptions menu click on the adobesign application:
From the Destinations menu, configure a new destination:
Typically, 500 errors indicate the lack of database setup.
Please verify your database is available and configured.
This is a wide family of error codes.
Find and inspect the system log files.
Problems may be rooted in resource availability (database) or access rights (entitlements).
You may need to disconnect the entitlement from SuccessFactors and create a new one.
If everything appears to be set up properly, stop and re-start the java app on the provider.
Follow the installation instructions for Recruiting.