Workfront for web page object ID assignment and management | Community
Skip to main content
james-mke
james-mke
Level 3
June 13, 2025

Workfront for web page object ID assignment and management

  • June 13, 2025
  • 1 reply
  • 368 views

Hello community!
We are in the process of implementing Workfront and migrating from Percolate. As part of our migration effort, we had been using Percolate IDs as a lookup element to match metadata from Percolate with content like web pages, emails, and other marketing materials in a PowerBI report. Workfront has their own ID system that will support us in maintaining that similar set of reporting which is great.
Enhancement and clarifications we are trying to work through from our legacy process include:

  • Can Workfront IDs be sent as custom metadata into an AEM Sites page?
  • Should we consider a web page as a "Project" or "Document" in Workfront? Document is appealing as webpages are updated from time to time and having a durable ID is critical for analysis. Project feels more like a what would be used to create or update a webpage.

Thank you for a point of view on what other teams might be using or if this investigation is helpful for you.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    1 reply

    M
    Adobe Employee
    monicacardosoAdobe Employee
    Adobe Employee
    June 19, 2025

    Hi @james-mke, 

     

    Thank you for your question! 

     

    1) Yes; Workfront IDs can be sent as custom metadata to AEM, but it typically depends on your integration platform. If you’re using Workfront Fusion or Adobe I/O, you can pass Workfront object IDs into AEM as part of the metadata payload when creating or updating content.

     

    2) This depends on your team's structure of work and the needed output. I think setting a web page as a document makes the most sense because you can (1) create an interactive proof out of it, (2) attach custom data to it, and (3) it provides a document ID with no additional objects tied to it. For example, a project usually contains tasks or issues and that might be too much for the maintenance of the web page. Instead, a document is 1 object that lives on a project, task or issue and allows you to upload multiple versions to keep track of changes. 

     

    https://experienceleague.adobe.com/en/docs/workfront/using/review-and-approve-work/proofing/create-proofs/generate-interactive-proof-for-website-or-other-web-content 

     

    - Monica 

      james-mke
      james-mkeAuthor
      Level 3
      June 23, 2025

      Thank you @monicacardoso 

      We will be using Fusion, so the ID part sounds doable.

      Thank you for the view on saving a web page as a document.

      Best regards,

       

      James

      Terms & ConditionsAccessibility statement

      Loading footer...