Hi @Kim_Hodnett , Could you also mark this as correct, so its helps community with finding the solution in the future. Thank you in advance, appreciate it. Best regards,Ivan

Hi @OmahaOmaha , This functionality can be achieved by using Single Line Text field and adding it to the custom form, and then populating the value via fusion once you have created the URL. Basically on an Issue custom formAdd field called Project overview or some name that worksCreate URL as alread...

Hi @HannahSc8 , There is no such option out of the box. Even though once converted to project request is linked to its resolution, meaning when the project is finished the request is also marked as resolved, but I guess you already know and are not looking for this functionality. Project resolution ...

Hi @LukaszMatyszewski , In short, unfortunately this does not happen automatically. We had a similar use case where our values were changing and discovered the hard way that we need to have additional automation to make sure things are in sync. Basically those External lookup fields are saved as Str...

Hi @LukaszMatyszewski, As far as I remember this was always like this, at least the past 2 years that I am actively working with those fields. Per documentation https://experienceleague.adobe.com/en/docs/workfront/using/administration-and-setup/customize/custom-forms/design-a-form/design-a-form#add-...

Hi @CharlieHam , Per official documentation https://experienceleague.adobe.com/en/docs/workfront/using/manage-work/requests/create-requests/create-submit-requests#create-requests-by-emailing-into-workfront this is working as intended. NOTE HTML formatting is stripped when the request enters Workfron...

Hi @Kim_Hodnett, I have refactored this a bit, added new lines, removed some extra spaces and it works normally/as intended I would say. Could you please try this displayname=Current Task listdelimiter=<div> listmethod=nested(tasks).lists type=iterate usewidths=true valueexpression=IF({numberOfChild...

Hi @Maggie_Gilbert  Following the above example and guessing you want to keep similar functionality I think it could be something like this IF(ISBLANK({DE:Requestor Override:name}),IF(ISBLANK({convertedOpTaskOriginator}),{owner}.{name},{convertedOpTaskOriginator}.{name}),{DE:Requestor Override:name}...

Hi @DylanNight , I did not do this directly but I did something similar, one more question did you also try to convert the JSON string into an array using the Parse JSON module?If this did not work I would wrap the array in an object before parsing so something like{ "array":[ { "I...

Hi @DylanNight , Could you also check if on the Planning Module input you have this message Can contain at most 1 item(s).If yes this might be the limitation.If no then the next thing to check is the array itself, per error message it seems like they are expecting array of objects and you are sendin...