Change in Eloqua Integration Workflow
- Vijay Alexander
Current Workflow:
For Eloqua Integration jobs in Integration (Create/Update Eloqua Integration & Integrate with Eloqua) we have a Get Eloqua Token button.
Once the user enters the details in the API section and clicks on Get Eloqua Token, a new window is opened to fetch the Eloqua Token.
After Sign In the page confirms the login details.
On Accept, the token is generated.
Currently, the token is directly saved into the Processr database. Once the user is back on the Processr configuration page, the user need not click on the Save button to save the changes.
New Workflow:
Once the user enters the details in the API section and clicks on Get Eloqua Token, a new window is opened to fetch the Eloqua Token as previously. The user follows the same steps as above.
Once the user is back on the Processr configuration page, the user needs to click on the Save button to save the changes.
What has Changed & Why:
Earlier the Get Elogua token triggered page directly saves into the Processr database without the user clicking on the Save button which was wrong. After the new implementation, the generated token will be passed on to the Processr Job & once the user clicks on Save, the token is stored.
This workflow will be re-used in Processr migration also which should be the correct behavior.
Impact on Existing User details / Token: No
Update the Zendesk article:
It is not needed. For any job changes we need to click on Save to Save the details. Earlier it was directly saving the token. Now the Save happens through the processr job. It is understood for a user that after getting the Get token, the user needs to click on Save to save the details.