You can do that either through a Customization using Studio Developer or a BPA Workflow that intercepts the default value for TransportTaskLine

https://docs.ifs.com/techdocs/24r1/040_tailoring/500_business_process_automation/080_workflow_examples/#populate_default_values

Hi ​@henros,

If your cloud version is 24R2 or higher, then you can set the default value for any field (standard or Custom) through Page Designer. 

For earlier versions, as ​@SimonTestard mentioned, the requirement can be achieved through a simple BPA workflow.

Please have a look at ​@dsj blog for simple BPA configuration.

https://dsj23.me/2024/02/05/ifs-workflows-think-big-start-small/

Regards

Abdul Rehman

Thanks ​@Abdul and ​@SimonTestard . I have tried to create this. See workflow:

However, I cant seem to find any fitting Call names on the projection action. Is it possible I have to use Data action type instead of Call action type?

HI ​@henros,

Please refer to the screenshots below.

1. Add a Projection call for Process Enrichment

2. Add a Script Task in the Workflow

3. Add an IFS Process Enrichment in the Workflow

Hope this helps.

Regards

Abdul Rehman

​@Abdul its done, but when I create a new transport task line after creating a new transport task, I get an error:

IFS Web Version: 24.1.12.20250501071452.0
Date: 2025-05-27T08:59:48.776Z

---------------------------------------------------------------------------

TransportTask/Form (server error)
Error while serializing contents.

This error happens when the server cannot serialize the data to be sent to the client.
A common cause is that one attribute's length exceeds the defined maxlength in the projection.
To find more info, open Log Window or Debug Console, refresh and then check Network Tab in DevTools. In the response there can be more detailed information about the exception.
Error details: N/A

Request Id: b23dc9ad-a861-4423-8203-dbb22cf8796e
Url: https://ifs.uat.pol.no/main/ifsapplications/projection/v1/TransportTaskHandling.svc/TransportTaskLineDetailSet/IfsApp.TransportTaskHandling.TransportTaskLineDetail_Default()

---------------------------------------------------------------------------

​@henros, it seems like a general error to me. Discuss with technical support. Disable the workflow action, and then check whether the error has been resolved.

​@Abdul that’s not why, it’s because the Json item Destination is already prepopulated, and therefore you don’t need to Register it as a variable for it to be returned to the client handler :)

If you attempt to register it, it’ll try to register the same field twice which causes a serialization issue, see this thread.

​@henros 

 Just set your BPA workflow as such :

If you test troubleshoot, you’ll see that the following variables are already registered by the time the workflow triggers, so any change to those doesnt require the variable be registered again.

​@Abdul that’s not why, it’s because the Json item Destination is already prepopulated, and therefore you don’t need to Register it as a variable for it to be returned to the client handler :)

 

If you attempt to register it, it’ll try to register the same field twice which causes a serialization issue, see this thread.

 

 

​@henros 

 Just set your BPA workflow as such :

 

 

If you test troubleshoot, you’ll see that the following variables are already registered by the time the workflow triggers, so any change to those doesnt require the variable be registered again.

 

 

This resolved it - thank you very much!