How should the administrator configure the Project custom form to make sure the value is passed to the project on conversion?

A customer sets up a calculated field on a request form. A user manually converts the request to a project and selects a template from the available active templates.

How should the administrator configure the Project custom form to make sure the value is passed to the project on conversion?
A . Add a new field with the same name but make it a text field.
B . Add the same field will a different calculation
C . Add the-same- field but leave the calculation blank

View Answer

Answer: C

Explanation:

When converting a request to a project in Adobe Workfront, it’s important to ensure that custom fields and their values are correctly passed from the request form to the project form. To achieve this, you need to add the same custom field on the project form, but in this case, the calculation should be left blank because the calculated value from the request form will be passed over and does not need to be recalculated at the project level.

Same field: The field needs to be exactly the same (same internal name) so the data can flow between the request and the project during the conversion.

Blank calculation: By leaving the calculation blank, you ensure that the field will accept the value from the request without overriding it or attempting to recalculate it.

For more details on setting up custom forms in Workfront and handling calculated fields during request-to-project conversions, refer to the Adobe Workfront Form Customization Guide.