Important points about Adobe's new Cloud storage in Workfront

 

  • New version of Workfront — Rolls out on Adobe Cloud Storage, but it's opt-in and admin-controlled. Admins choose when to flip the switch, can pilot with specific groups (up to 10), and test in sandbox before going live.
  • Adobe Cloud Storage replaces Workfront's own storage — Workfront, Frame, and Creative Cloud share one storage layer. This requires one Workfront instance paired with one Frame account in the same IMS org. Storage quota (GB per user) is pooled between the two.
  • Frame.io replaces Workfront Proof as the review screen — Once cloud storage is on, Frame.io's viewer becomes the default review/markup tool, with better commenting/markup tools and a mobile app. The old Workfront Proof still works for legacy storage, with no set retirement date.
  • Frame.io Enterprise adds creative work-in-progress features — internal-only commenting, secure external sharing with watermarks, and direct asset editing for creative teams, while Workfront still handles overall work management.
  • A redesigned "Documents" area — improved version tracking and Creative Cloud app integration, though a few legacy features (like document requests) are dropped.
  • Permissions become centralized in Workfront — access is set once in Workfront and automatically flows through to Frame.io; there's no separate permission system to manage in Frame.
  • Stricter file/folder naming rules — enforced to avoid conflicts across the shared storage system (character limits, no duplicate names in the same project, etc.).
  • Existing automations likely need rebuilding — any Fusion automation built around the old proofing/approval system won't carry over automatically, since the underlying data model and triggers are different. This is flagged as one of the higher-effort migration tasks.
  • One-way object conversion — legacy Workfront projects can be converted to the new cloud storage format, but not moved back once converted.
  • This requires real change management — a phased, multi-month rollout (roughly outlined over ~7 months) with pilot groups, baseline metrics, and documentation for end users, rather than a flip-the-switch change.

    • Comments

    Post a Comment

    Popular posts from this blog

    Error: Number of included segments do not match

    Introduction In this blog, we tackle a crucial issue encountered during the reprocessing of an X12 EDI message. We will get into the root cause of the problem and provide you with a solution to overcome it. Error: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:       Error encountered during parsing. The X12 transaction set with id '103465910' contained in functional group with id '02', in interchange with id '000000009', with sender id '4532345856     ', receiver id '8038025150     ' is being suspended with following errors: Error: 1 (Miscellaneous error) 4: Number of included segments do not match . The sequence number of the suspended message is 1.  Root Cause: The issue stems from a mismatch in the number of se...
    Read more

    REST API Calls with Query Parameters in BizTalk: A Step-by-Step Guide

    Image
     Introduction In this blog, I will provide a comprehensive guide on how to call a REST API that requires query parameters. We'll walk through the necessary steps to set up the environment and make successful API calls. Solution High Level Steps 1. API Overview: We will be using an open API for demonstration purposes. The API endpoint we'll be working with is: https://randomuser.me/api/?results=1 2. Schema Creation: Create a schema named "SourceA" that matches the structure of the messages you'll be dropping in the receive location. To create a JSON response schema, follow these steps: capture the JSON response by running a test in Postman, and then utilize a JSON schema generator to create the desired JSON schema. 3. Field Promotion: In the SourceA schema, promote the field called "results." This field will serve as the variable for the query parameter. 4. Receive JSON Pipeline: Develop a receive JSON pipeline that can receive JSON messages and convert t...
    Read more

    Updating BizTalk SSO DB using BTDF and a simple BTDF deployment

    Image
    Introduction In some cases, it becomes important to securely store key-value pairs, such as configuration data (e.g., usernames and passwords), rather than hardcoding them within a BizTalk orchestration. One effective way to achieve this is by storing these key-value pairs securely in the BizTalk SSO (Enterprise Single Sign-On) database and subsequently reading these values within our orchestration through a simple line of code within a BizTalk expression shape. In this blog post, we will go through the steps to add key-value pairs to the SSO database using the BizTalk Deployment Framework (BTDF). We will also explore how to read these values within a BizTalk orchestration and perform a simple BizTalk deployment using BTDF. Steps Creating a BizTalk Solution, Schema Project and Map project: Let's first create a BizTalk Solution called "SSOPOC" and a project called "SSOPOC.Schema". For this, you need to go to Visual Studio and click on File --> New Project --...
    Read more