Auto-created Work Orders via Groovy script bypassing Fusion Field Service (FFS) activity creation

Summary:

We are using a Groovy script to automatically create Service Work Orders from Service Requests. While the Work Order records are successfully created in Fusion, they fail to trigger the out-of-the-box integration to create the corresponding Fusion Field Service (FFS) activities.

Process & Testing:

1. When a Service Request triggers the Groovy script, the Work Order is created, but no FFS activity is generated or linked.
2. However, when we create a Work Order manually through the UI, the FFS activity is created automatically.
3. Crucial Test:We used the UI to copy the exact Work Order that was created by the Groovy script. The manually copied Work Order successfully generated an FFS activity.