-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
W-17246664 Enabling API Catalog #373
base: latest
Are you sure you want to change the base?
Changes from all commits
bed6094
4a6230e
2b59014
97f21b6
978cfd5
461f509
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
= Enabling API Catalog | ||
|
||
Enable a connected Salesforce organization to access and sync Anypoint Platform APIs into API Catalog in Salesforce. This capability is enabled in Anypoint Platform Access Management by an Anypoint Platform organization administrator. | ||
|
||
[[enable-disable-api-catalog]] | ||
== Enable or Disable API Catalog in Anypoint Platform | ||
|
||
include::partial$include-nav-steps-org-admin.adoc[] | ||
|
||
. Click *Salesforce*. | ||
. In *Capabilities Managed in Anypoint Platform*, click *Settings* for *Make MuleSoft Anypoint Platform APIs Available in Salesforce*. | ||
. In *Settings for Anypoint APIs in Salesforce*, click *Continue*. | ||
. In *Settings*, select the Anypoint Platform business groups that allow the Salesforce organization to import Anypoint Platform APIs into its API Catalog, and click *Save Settings*. | ||
+ | ||
[NOTE] | ||
Within the selected business groups, you can import only APIs that have specs published in Exchange with active instances into Salesforce. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There are quite a prerequisites that have to be met for APIs to sync into API Catalog. I wonder if we could be a little less specific here and cross-reference the API Catalog "Before You Begin" (Name and link tbd) content in help.salesforce.com? Something like: The alternative might be to duplicate all of the prereqs here, which becomes a maintenance issue. It's a bit of a moving target now. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also, import should be changed to sync throughout the content and the UI text. |
||
. In *Capabilities Managed in Anypoint Platform*, switch between *Enabled* or *Disabled* in *Make MuleSoft Anypoint Platform APIs Available in Salesforce*. | ||
+ | ||
image:connected-salesforce-org-api-catalog-enabled.png["Connected Salesforce organization with both Invocable Actions and API Catalog enabled"] | ||
+ | ||
The Salesforce organization administrator can then sync APIs into their catalog. | ||
+ | ||
For details about syncing APIs and using API Catalog in Salesforce, see xref:general::api-catalog-in-salesforce.adoc[]. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Will this link be replaced with a link to the topic in Salesforce Help? I have the planned link, but need to get the topic ID approved by a content strategist before I share it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @bjoson-mulesoft Yes, it will need to link to the Salesforce help content. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @valkyrie69, the best link in the Salesforce help will be https://help.salesforce.com/s/articleView?id=platform.api_catalog.htm and the title is API Catalog. |
||
. After the APIs are synced, the Salesforce administrator selects individual API instances and operations and converts them into invocable actions so Salesforce developers can access them. | ||
bjoson-mulesoft marked this conversation as resolved.
Show resolved
Hide resolved
|
||
+ | ||
A client ID is created. | ||
bjoson-mulesoft marked this conversation as resolved.
Show resolved
Hide resolved
|
||
. An access request for the Salesforce developers selected by the Salesforce administrator is sent to the Anypoint Platform owner of that API through API Manager. | ||
+ | ||
After the request is accepted, Salesforce developers can start using the API. | ||
|
||
== See Also | ||
|
||
xref:connecting-salesforce-orgs.adoc[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now these options don't seem to match what's in QAX. Is there a new design for this I should be using for the review?