WF Fusion | Export Custom Form Details | Adobe Higher Education
Skip to main content
I
IsaacWu
Level 2
October 15, 2025
Resuelto

WF Fusion | Export Custom Form Details

  • October 15, 2025
  • 2 respuestas
  • 509 visualizaciones

Hello,

 

I have a Fusion scenario that converts incoming Issues into Projects. I have a branch on the scenario that:

  1. Applies the same custom form to the converted project (Misc Action module)
  2. Gets the request details (Read a record module)
  3. Copies request details from the issue to the custom form that is now on the converted project (Update a record module)

I'm having trouble figuring out which modules to add to now:

  1. Export the custom form details present on the project
  2. Upload the document to a document folder

 

Is this possible to automate? Let me know if there's any more details I can provide. Thanks so much for your insight!

Mejor respuesta de ChrisStephens

Ok, so generating the property export with Workfront's API is a multi-step process. Step 1 is generating the pdf, and then step 2 is attaching it to your object (project/issue).

  1. Creating the pdf
    1. Make a custom api call to the CTGY endpoint. You will need to use the api-unsupported version.
    2. The method should be PUT
    3. The QS is action=exportCustomData
    4. The body is
      1. objID={your object ID you want the data from}
      2. objCode={the object type you want the data from, i.e. project, task}
      3. categoryIDs={simple list of the category IDs you want data for, if you want the overview include "overview", if you want all include "selectAll"}
  2. Attach the pdf to your object
    1. Make a custom API call to the DOCU endpoint.
    2. The method should be POST
    3. The body should be
      1. name=your file name.pdf
      2. objID=the object you want to attach the file to
      3. handle=the response you get from the 1st call
      4. docObjCode=the type of the object you want to attach the file to
      5. currentversion=
        1. version=1
        2. fileName=your file name.pdf

 

2 respuestas

lgaertner
lgaertner
Level 9
October 16, 2025

Hello Isaac,

 

First of all I am not sure, If I understand your issue right, but why don't you copy the custom data from the request to the new project within the conversion step in your scenario?

 

And where do you want to export the "details present on the project" to?

 

Regards

Lars

    I
    IsaacWuAutor
    Level 2
    October 16, 2025

    Hi Lars,

     

    Thanks for pointing that out. I've removed the redundant modules and have the conversion copy the custom form data from the issue to the project.

     

    I want to export the custom form data as a PDF and send it to a folder within the project so the assigned team can create a proof of it for review. 

     

    Thank you for your insight! 

    ChrisStephens
    Community Advisor
    ChrisStephensCommunity AdvisorRespuesta
    Community Advisor
    October 16, 2025

    Ok, so generating the property export with Workfront's API is a multi-step process. Step 1 is generating the pdf, and then step 2 is attaching it to your object (project/issue).

    1. Creating the pdf
      1. Make a custom api call to the CTGY endpoint. You will need to use the api-unsupported version.
      2. The method should be PUT
      3. The QS is action=exportCustomData
      4. The body is
        1. objID={your object ID you want the data from}
        2. objCode={the object type you want the data from, i.e. project, task}
        3. categoryIDs={simple list of the category IDs you want data for, if you want the overview include "overview", if you want all include "selectAll"}
    2. Attach the pdf to your object
      1. Make a custom API call to the DOCU endpoint.
      2. The method should be POST
      3. The body should be
        1. name=your file name.pdf
        2. objID=the object you want to attach the file to
        3. handle=the response you get from the 1st call
        4. docObjCode=the type of the object you want to attach the file to
        5. currentversion=
          1. version=1
          2. fileName=your file name.pdf

     

      Términos y condicionesAccessibility statement

      Loading footer...