Release Notes: Contracting in SFDC
As part of our ongoing efforts to improve our system integrations and streamline our onboarding process in Portal 3.0, we have decided to
move the contracting process back to Salesforce, with the onboarding process picking up in Portal 3.0 only once an agreement has been
sent out and signed via Salesforce.
What does this mean for me?
Your process in Salesforce continues to be the one you’ve been using! You’ll be creating accounts and opportunities in Salesforce, creating
quotes off of the opportunity, sending Adobe-generated agreements out for signature, configuring PLIs, etc. Once the customer has signed
their contract, you’ll move over to Portal 3.0 to begin the onboarding process.
What’s different in Portal 3.0?
Without the need for a Portal contract, your onboarding process will be account creation, user creation, creative uploads, and campaign
launch. DSP integrations and pixel creation will happen as soon as the Portal account is created, without needing to wait for a linked Portal
contract to be signed. Then you’ll be able to move straight to user creation and/or creative uploads!
The process for campaign setup and creative uploads will not be changed.
What will happen to my existing Portal 3.0 contracts?
Accounts that are already running on Portal 3.0 will continue to run and there is no action required for those accounts or contracts.
Contracts previously created in Portal 3.0 will continue to be accessible there and amendments for those contracts can still be created in
Portal 3.0.
Why the move?
The onboarding process in Portal 3.0 was a bit disjointed at times, with certain operations happening in SFDC, others in Portal 3.0, and
users needed to go back and forth between the two systems in order to get their customers fully onboarded. With the updated process,
users will be entirely in SFDC until they have a signed contract, at which point their process picks up on the Portal side, leading to a more
streamlined approach.
What is happening in the background?
Once there is a signed (via Adobe) agreement in SFDC, the system will create an SFDC contract object and will then send a trigger to Portal
3.0 to “replicate” this contract in the Portal database. This process happens in the background and replicated Portal contracts will not be
viewed by users, this is essentially a cache on the Portal side that allows us to work with the data more seamlessly and have downstream
Portal services (i.e. campaign setup, reporting, billing/reconciliation, etc.) to pull from the Portal contract’s data rather than reading from
SFDC each time and necessitating further SFDC <> Portal integration touchpoints. Everything downstream stays the same, so no additional
work was required to get these services ready for the updated process.