Add AEM asset approval prerequisite to integration doc (#69)#87
Open
ZLeventer wants to merge 2075 commits into
Open
Add AEM asset approval prerequisite to integration doc (#69)#87ZLeventer wants to merge 2075 commits into
ZLeventer wants to merge 2075 commits into
Conversation
added 30 commits
August 13, 2025 23:14
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #69 — Assets in AEM must have Approved status before they appear in Marketo Engage. Users were completing the integration setup but couldn't see any assets because this prerequisite was undocumented.
Added an
[!IMPORTANT]callout near the top of the setup instructions.Test plan