Content Update Skill content-update
The content update skill of the Experience Production Agent automates content production to accelerate everyday tasks for Adobe Experience Manager (AEM) as a Cloud Service and Edge Delivery Services.
The content update skill updates existing content across the CMS, including content fragments, pages, forms and assets. The agent can perform actions such as updating, removing, replacing, or adding content elements to keep experiences accurate and current. Inputs can be natural language description, and when used with Jira PDFs and screenshots can provide input too.
Overview overview
The content update skill transforms the details that you provide, either through natural language or visuals, into content updates on your page. You supply the URL of a page that needs updating, together with details of what needs updating, and the agent skill completes your task.
Capabilities capabilities
You can access the content update skill from:
AI Assistant ai-assistant
You can access AEM Business Agents via the AI Assistant.
Open the AI Assistant from experience.adobe.com, then start interacting by specifying your prompt in natural language using the Ask AI Assistant anything field:
Sample Prompts sample-prompts
To initiate content updates you can give a wide range of natural language prompts. You also need to specify the public facing URL of the page you want to update. For example:
-
modify the following page https://www.your-url.com/sale Update the main hero heading to “Black Friday Mega Sale - Up to 70% Off”, Change the countdown timer to show “Ends in 48 Hours”, Remove “Sign up for updates”, Change all “Shop Now” buttons to “Grab the Deal”"
-
https://www.your-url.com/laptops/your-laptop-model Update banner copy to “Save 300 USD Today Only”, Update pricing from 1,299 USD to 999 USD, Remove financing option banner
-
https://www.your-url.com/your-sneaker Update stock status from “Low Stock” to “Back in Stock - Limited Quantities”, Change the size selector to highlight available sizes in green, Remove the “Coming Soon” badge
-
https://www.your-url.com/your-sneaker Update the product images to show new colorways
Jira jira
Using the content update skill with Jira allows you to create a ticket with instructions that automate your edits.
Create a ticket create-a-ticket
Create a Jira ticket (of any type).
There are two essential details needed in the Description field of your ticket:
-
The public facing URL of the page you need to edit.
-
The changes needed.
Currently the skill supports the following range of formats to describe your changes:
- Natural Language in the ticket description
- for example “Change the headline from X to Y”
- Annotated PDF attached
- for example, create a PDF of your page and add annotations detailing what you want changed
- Comments in attached PDF
- for example, create a PDF of your page and add comments detailing what you want changed
- Annotated screenshot attached
- for example, take a screenshot of part of your page and add annotations detailing what you want changed
- Microsoft Word file attached, containing natural language changes
- Natural Language in the ticket description
Invoke the agent from your ticket invoke-the-agent-from-your-ticket
To use the agent, add a comment to your ticket. In the comment mention the agent with the @ symbol, together with the command it should execute; for example:
@aemagent@adobe.com process
Currently, the agent understands the commands:
process- process the requestcancel- cancel a processing requestretry- re-process a requestfeedback- apply feedback to a previous generationreprocess- reprocess the original request
How the agent interacts how-the-agent-interacts
After you issue a command to the agent, it responds with comments in the Jira. The comments detail the agent’s progress, and actions taken.
In the case of a process command to trigger updates, the responses might follow the sequence:
-
The initial comment confirms that the agent has started.
-
Once the task is completed. the agent responds with another comment containing details of the actions taken.
- The content updates made by the agent are non-destructive - this means that they are made to a preview instance.
- The comment contains links to the updates, so that you can review and publish as required, or assign the Jira to whoever will be responsible.
-
The following image shows an example Jira that triggers the
processcommand for the content update skill:
Activation activation
To activate and gain access to the Experience Production Agent with Jira you need to email Adobe. To get started you can contact:
experience-production-agent@adobe.com- or reach out to your account team
To speed up the process it helps to provide the following information:
-
For AEM as a Cloud Service
-
You need to provide your:
- Organization ID
product_idprofile_id
-
These values could be found using the following steps:
- Your administrator needs to visit https://adminconsole.adobe.com/
- Select Adobe Experience Manager as a Cloud Service
- Select the appropriate AEM instance
- Select the profile that allows read and write operations for the content in question
- Grab the browser URL
- Extract
product_idandprofile_idfrom the URL.
For example, https://adminconsole.adobe.com/products/profiles/users
-
-
Edge Delivery Document Authoring
-
Provide your Adobe team with the following information:
-
Relevant domains
-
Relevant Github information:
- Org
- Repo
- Branch
-
-
Limitations limitations
Currently the limitations for the Content Updater are:
- File uploads can be used when interacting with Jira, but are not supported when interacting with the AI Assistant.