ERP Connector acts as a medium to connect between the ERPapplications and the OpKey portal. It helps connect a specific ID of that particular ERP application environment with the environment of Opkey.
Let us have a look at how the ERP Connector helps connect with the Salesforce Environment.
To be able to view the Salesforce Environment, you can either proceed through the Opkey Surge Portal or through the Salesforce Test Accelerator.
The Environment Settings Tab present on the right-hand corner of the Dashboard of the Opkey Surge will open up a new window of Main Settings.
The Main Settings tab can also be reached by clicking on the left panel “Environment Settings” section on the Quality Lifecycle Management icon.
The connection of Opkey Environment with the Salesforce Environment can be established via
Opkey ERP Connector by providing the credentials to log in to it.
To log in to the Opkey ERP Connector, you need to download it from Google and add it to your Chrome Extension. You’ll now have to launch the ERP Connector from the Settings tab by clicking on the three dots present towards the end of the browser.
Click on the Extensions Tab and select the Opkey ERP Connector. You’ll now have to enter the credentials to launch the ERP Connector.
You’ll then have to click on the Main Setting Tab under the Environment Settings, placed on the right-hand corner of the page.
You’ll have to click on the Salesforce “Add Environment” and fill in the credentials.
On clicking the “Add to Environment” button, you’ll be able to view a pop-up window that will ask you to fill in the credentials.
Once the credentials are provided, you’ll have to Save the details. The created Environment will now reflect in the Salesforce Window.
Click on the Global Metadata Settings and Click on Add to ORG
A pop-up window will open where you’ll have to select the created environment and proceed to click on the Next button.
The window which opens up will ask for the details as shown in the image below.
The window will allow you to schedule the syncing of metadata for each day. The syncing can be scheduled by clicking the Enable Button, which will allow you to select the Time and Frequency for the Syncing.
The syncing can be done manually by simply clicking on the Fetch button. Once you click on the fetching button, the process gets started.
The scheduling can also be done from the Icon present below the Action section as well.
The adjacent tabs can be used for Deleting, Authenticating User, and Fetching Manually.
The tab opens up a window where scheduling can be done.
Once the scheduling is done, the process will start to fetch the data, every day at the specified time automatically.
It will fetch the synced data of that environment as can be seen in the image below.
The changes in the Salesforce portal can be done through the Object Manager tab on the portal.
You can go to Object Manager on Salesforce and click on Create. Select the “Custom Object”.
For the Custom Object,
You can also view the details of the existing object.
For the existing object, you can go to the Details tab and click on the injected page to view the details of :
After the syncing is done, you’ll be able to view the changes done on the object i.e, what has been added or deleted, the impact that has happened on the specific object due to the changes done, which field has been added etc.
This section on Injected page allows you to get details about the count of
Button Links and Action
The Risk analysis section lets the user know the fields which are in risk according to the intensity of
The next section is of Percentage Populated by Field
This will let the user know what are changes have happened in the Test Cases of Opkey.
In the tab of Fields and Relationships, you’ll be able to see the changes performed on the specific custom fields about field details, graph details, one level, and multi-level dependency, etc.
The injected page will show the details of:
The first section is about field details as shown in the image below.
The next section is of Field Impact.
The first graph
The first graph Based on Field Population shows the user, the changes being made on the fields.
The second graph Based on Opkey Test Coverage shows the details of the percentage of impacted Test Cases of Opkey due to the changes done in the field.
This will let you know the impacted fields after the changes are done.
The next section is of Single Level Dependency. This section allows the user to view the one-level dependency of fields.
The next section is of Multi Level Dependency.
On clicking the View Button a new page gets displayed of Multi-Level Dependency.
The diagram shows the multi-level dependency mapped according to the fields, wherever it is used.
Whatever changes will be performed in the records and the fields, will be reflected in the Object.
If the object is present in the Test Cases, then the Test cases will be affected post any modification, for which the Snapshots will provide us with details.
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article