Content Update Job content-update

The content update job 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.

Overview overview

The content update job updates existing content, including content fragments, pages, forms and assets. The job 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.

The content update job 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 job completes your task. When used with AEM as a Cloud Service, the job creates a new launch so you can review the updates before applying. When used with Document authoring, the job creates a new version.

Capabilities capabilities

You can access the content update job from:

AI Assistant ai-assistant

You can access the job in AEM via the AI Assistant.

Open the AI Assistant from the top-right toolbar to start a conversation.

AI Assistant icon on the toolbar

Configuring the Publish URL configuring-the-publish-url

To instruct the agent where to apply updates you must supply a page link. You may provide either an author URL or a publish URL.

To use a publish (public facing) URL a one-time configuration must be made:

  • Prerequisites:

    • To make the configuration, the user must have System Admin or Product Admin rights.
  • Configuration:

    1. Invoke the Content Update job by requesting a content update for the URL.
    2. The assistant will walk you through the configuration, by asking you a number of questions.
    3. Once complete the publish URL is configured and can be used.

For example:

Content Update job - configure publish URL

Prompts prompts

To initiate content updates you can give a wide range of natural language prompts. You need to specify the public facing (publish) URL, or the author environment URL, of the page you want to update. Some, but not all, of the verbs that are supported; replace, update, remove, change, revised, modify, adjust, delete.

Sample Prompts sample-prompts

Sample prompts include:

  • on <your-publish-URL> update “Your perfect coffee is four questions away!” to “Your coffee, your way!”
  • on <your-author-env-URL> replace the image from “holdingcup.png” to “stairhead.png”
  • on <your-publish-URL> change “Take our Coffee Quiz” button to a more engaging version"
  • on <your-author-env-URL> remove the section “Rewards unclaimed is a Gift missed!”
  • on <your-author-env-URL> update based on the attached

File Upload in AI Assistant file-upload-in-ai-assistant

As well as entering natural language prompts directly, you can also upload a document to request changes.

Use the + icon in the bottom left of the prompt menu to upload a file specifying your requirements. Supported file formats include; PDF, JPG, PNG, DOCX, and others.

Content Update job - file upload

For example, an annotated PDF specifying the requested changes:

Content Update job - annotated PDF

Orchestration with the Brand Governance Agent orchestration-with-the-brand-governance-agent

If the organization has imported their brand policy the Content Update job will use this policy during agentic content updates (see the Overview video).

For a prescriptive prompt such as:

  • on <your-publish-URL> update “Your perfect coffee is four questions away!” to “Your coffee, your way!”

The Content Update job orchestrates with the Brand Governance agent and notifies the user if the provided copy is on-brand or not.

Content Update job - orchestration with the Brand Governance Agent

For more abstract prompts such as:

  • on <your-publish-env-URL> change “Take our Coffee Quiz” button to a more engaging version

During generation the agent will utilize the brand guidelines to ensure that the output is on-brand.

Jira jira

Using the content update job 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:

  1. The public facing URL of the page you need to edit.

  2. The changes needed.

    The job 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

Invoke the Job from Your Ticket invoke-the-job-from-your-ticket

To use the job, add a comment to your ticket. In the comment mention the job with the @ symbol, together with the instructions.

For example:

  • @aemagent@adobe.com process this ticket

How the Job Interacts how-the-agent-interacts

After you issue a command to the job, it responds with comments in the Jira. The comments detail the job’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 job has started.

  • Once the task is completed, the job responds with another comment containing details of the actions taken.

    • The content updates made by the job 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 job:

    Example Jira using the content update job of the Brand Experience Agent

Further refinement in authoring further-refinement-in-authoring

After you choose to edit the page in AEM, it opens in your authoring environment (for example, the Universal Editor or the Page Editor).

In the Universal Editor, the AI Assistant is context aware: you can select elements on the canvas and work on them with the assistant.

Universal Editor - edit text with the Assistant universal-editor-edit-text-with-the-assistant

To refine copy from the Assistant while authoring:

  1. Select the element in the Universal Editor.
  2. Open the AI Assistant from the upper-right corner, enter your prompt, and submit.

Example prompts:

  • Update to Explore the World of Coffee
  • Update to be more engaging for the 30-40 year old age demographic and avid coffee drinker

Select Apply changes (or equivalent) so updates appear on the page.

Activation activation

You can explore AEM Agents through the Playground, or connect with your CSM or TAM to discuss access via the Agentic SKU.

Additional Resources additional-resources

The following resources may be useful as you continue to explore the Experience Production Agent:

recommendation-more-help
experience-manager-cloud-service-help-main-toc