How do I map the request custom form and its data to a Program? | Community
Skip to main content
Srinija_N
Srinija_N
Level 7
June 4, 2026
Question

How do I map the request custom form and its data to a Program?

  • June 4, 2026
  • 3 replies
  • 44 views

How can I dynamically capture custom form, fields and values submitted on a request and map them to a Program? 

The goal is to convert requests into Program while carrying over all its custom form data. The requests can be from different queues with different custom forms.

3 replies

ninoskuflic
ninoskuflic
Level 5
June 4, 2026

Hi, you can convert a request to a project, but not program. With Fusion, you can do XYZ such as create a custom program and attach custom form data from a request. So when a trigger happens (e.g. a request status is set to closed), Fusion would then take a look at the custom form on a request, attach it to a newly created program and copy paste values. 

If this solved your issue, please mark it as solved so others can find the solution faster.
Srinija_N
Srinija_NAuthor
Level 7
June 5, 2026

We need this custom automation of Request to Program conversion.

Our idea was the same, but the requirement is to dynamically attach custom forms from the request and then dynamically map the fields and its value. We are thinking of using GET HTTP call to get the custom form details of the request and then do a POST HTTP call on the program, but not sure how efficient it would be.

Just want to know if someone has done this, or any other ideas from the community here.

If this helped to solve your problem, please mark it as 'solved' so others can also find the solution faster. Thanks!
ninoskuflic
ninoskuflic
Level 5
June 5, 2026

You do not need to do this via custom HTTP modules, you can do all of it with native Workfront modules inside of Fusion. 😀

If this solved your issue, please mark it as solved so others can find the solution faster.
D
devanshu16
Level 2
June 5, 2026

I've built this using native Workfront Fusion modules and it's working in production. Here's my approach:

1. GET OPTASK/search to fetch the issue and extract custom form category IDs 2. Tools module to map category IDs and store template ID as variables 3. Convert Object (Issue → Project) passing the custom forms and template ID dynamically 4. Second GET OPTASK/search to fetch all parameterValues (field values) 5. JSON Transform on parameterValues 6. PUT project to write the custom field values back onto the newly created project 

No custom HTTP calls needed, all native Workfront modules. It works across different queues with different custom forms since the form IDs are dynamically extracted per issue.

That said, it is a fairly long chain and I'm also curious if anyone has found a more elegant approach, would love to hear if there's a cleaner way to handle the parameterValues mapping!

J
Jasonmiller2334
Level 1
June 7, 2026

You can capture the request’s custom field values via API/automation, then use a field-mapping layer to transfer them to the corresponding Program fields during conversion. Using field IDs rather than field names helps support multiple queues and different custom forms.

Terms & ConditionsAccessibility statement

Loading footer...