1. Overview
The AEM–Workfront connector integrates project management (Workfront) with digital asset management (AEM DAM). This ensures assets created, reviewed, and approved in Workfront flow directly into AEM for publishing.
The connector is available for:
- Adobe Managed Services (AMS) → hosted AEM instance with custom configurations
- AEM as a Cloud Service (AEMaaCS) → cloud-native, always-on AEM
2. Prerequisites
For Workfront
- Admin-level access to configure integrations
- Workfront Fusion (optional, if you need custom automations beyond the connector)
- Workfront Proof enabled for review/approval workflows
For AEM
- Admin access to AEM Author instance (AMS or Cloud Service)
- Permissions to install and configure the connector package
- Metadata schema and DAM folder structure planned
3. Connector Installation
AMS Deployment
- Download the Workfront Connector package (from Adobe Software Distribution).
- Install via AEM Package Manager on the AMS environment.
- Configure endpoints to connect with the Workfront API.
- Work with AMS Support for firewall rules, SSL certificates, and version compatibility.
AEM as a Cloud Service Deployment
- Connector is part of Cloud Manager pipelines.
- Add the Workfront connector dependency in your Cloud Manager codebase.
- Deploy through your pipeline → it becomes available on your AEMaaCS author instance.
- Minimal IT overhead since updates are managed by Adobe automatically.
4. Configuration Steps
- Set up API credentials in Workfront
- Navigate to Workfront Setup → Integrations
- Create a new API client, note down the Client ID and Secret
- Connect AEM to Workfront
- In AEM Author: go to Tools → Cloud Services → Workfront
- Enter Workfront domain, Client ID, and Secret
- Test connection
- Define Metadata Mapping
- Map Workfront custom forms/fields to AEM metadata schema
- Example: “Campaign Name” in Workfront → “Project” metadata in AEM
- Configure DAM Folder Mapping
- Create folder mapping (e.g., /content/dam/projects/2025/)
- Set rules for asset ingestion from Workfront projects
- Enable Review & Approval Workflows
- Workfront Proof → sends approved asset version into AEM
- AEM versioning ensures history is preserved
5. Typical Workflow
- Campaign Planning in Workfront
- Project is created with tasks and assignments
- Assets uploaded or requested
- Creative Work & Review
- Designers upload drafts to Workfront
- Proofing/approvals happen in Workfront Proof
- Sync with AEM
- Approved asset automatically pushed to AEM DAM
- Metadata and taxonomy applied during ingestion
- Publish to Channels
- AEM authors/marketers deliver assets to web, mobile, commerce, or email channels
6. Differences Between AMS and AEMaaCS
| Feature | AMS | AEM as a Cloud Service |
| Connector Setup | Manual install via Package Manager | Cloud-native, part of pipeline |
| Upgrades | Requires coordination with AMS support | Automatic with AEMaaCS releases |
| Customization | Flexible, supports custom workflows | Limited customization, optimized for standard workflows |
| Scalability | Depends on AMS infrastructure | Auto-scale in cloud-native environment |
7. Best Practices
- Plan Metadata Early: Align Workfront forms with AEM schemas before rollout
- Test Integration in Lower Environments: Sandbox → Stage → Production
- Govern Access: Use role-based permissions to control asset visibility
- Leverage Automation: Use Workfront Fusion for advanced use cases (e.g., auto-create AEM folders when a project starts)
- Monitor Logs: Regularly check connector logs for sync issues
8. Common Issues & Troubleshooting
- Assets not syncing? Check Workfront API token validity
- Metadata mismatch? Review mapping configuration in AEM
- Slow performance? For AMS, check firewall/SSL settings; for AEMaaCS, raise Adobe support ticket
- Duplicate assets? Ensure correct versioning setup and avoid manual uploads outside the workflow
The AEM–Workfront connector bridges the gap between creative operations and content delivery. For AMS, it provides flexibility with custom configurations, while AEMaaCS offers a cloud-native, always-updated integration. Implementing the connector streamlines campaign execution, reduces manual effort, and ensures that approved assets flow seamlessly from planning to publishing.
Leave a Reply