The Universal Action Component (also referred to as the Execution Manager) is a custom Lighting Web Component (LWC) that allows you to initiate an active Connector Function (with a mapped Outbound Data Event) directly from a Salesforce record. You can add the UAC to your Lightning Record Page and once you have created a Base Data Event Object and completed the mapping steps, that Connector Function will become available for use in the component. In the event that you are using multiple Connectors, each different Connector will have a tab and the select box will display only the endpoints associated with that object.
You can add the component to your object's Record Page in the Lighting App Builder using the Setup Menu > Edit Page in the main navigation panel at the top right when you are on the desired page.
From the App Builder page, choose the 'Components' tab in the top left and scroll down to the 'Custom - Managed' section. Locate the 'nexusConnectorExecutionManager' and drag it onto the page where you would like to have it. For this example we add it as a sidebar component in a 2 column layout, but you can choose the best location. Refer to the Salesforce documentation for any additional questions about using the Lightning App Builder regarding page activation and component visibility.
Once added to the page and saved, this component has been built so that it will ONLY be visible when an active Nexus Connector has at least 1 active Connector Function that has had an 'Outbound' Data Event mapped to this object as a 'Base' Data Event Object. Likewise, as stated earlier, it will display ALL of the Connectors and Functions that have also been mapped to this object (hence the 'Universal' in the 'Universal Action Component).
Note: Use of the 'Execution Manager' can be replaced by making the callout execution from either a FLOW or via Apex Code. See Nexus - Execute Function from FLOW or Apex Class for more details.
Clicking the Execute button on the component will start the API transaction and has subscribed to a Push Topic on the Request Message. This allows for the component to track the status with a progress bar. If everything is configured properly, most connectors will proceed through 'Sent', 'In Progress' and finally 'Complete' or 'Error' stages. If there is an error, then the message should be displayed. Sometimes this can make troubleshooting easier if the problem is with something like missing data on the calling record. In this example, the API was expecting a 'Contact Name', but the mapped field on the Account record was blank.
After adding the value, we can attempt the callout again without ever leaving the Account record...
..and re-submit the callout. This time the callout was successful and we received a 'Complete' status so the component reloaded the page and the data that was updated on the calling record (in this case, an External Account Number) is now populated...
Note: Unfortunately, not all errors are immediately obvious and require a deeper investigation into the root cause by checking the Request Message files. Check the Connector's documentation for help in troubleshooting common problems.