These 2 fields are not sent from Cloud to PSO (check the application message or PSO Audit). If you need to fix the time, you can use the “Fixed Start” field.

Hi,

We are facing an issue with the task date sent to PSO and its allocation. Even though the planned date of the task is set for a future date, it is getting scheduled and allocated on the current date. While we can assign a fixed date at the task level, we are generating tasks through the recurrence service program. The same issue is occurring with the SLA, as it is also taking the current date and time.

For example, we want a task to be scheduled for 19-05-2025, and manually generated requests from the recurrence service program reflect the planned start and end dates as 19-05-2025. However, in PSO, it is getting assigned to a resource today. How can we restrict this? Is there a way to set a fixed start date while the task is generated using the recurrence service program?

We want to see the one-month allocation for the resource in PSO.

 

If you don’t have SLA commitments you can use the Earliest Start and Latest Finish Dates to control the primary SLA for PSO.

Hi ​@anmise / ​@Alexander Heinze 
Is there any way to include the datetime for the earliest start and latest finish for tasks created by the recurrence service program? Tasks created by the recurrence service program only have a planned start and planned end date.

You cannot set the dates on the Recurring Service, but you can use SLA templates on to the Service linked to the Recurring Service, which can control the dates sent to PSO. 

Hi ​@anmise / ​@Alexander Heinze  
Currently, we are using the 23R2 cloud version. The latest finish is not being sent to PSO. Additionally, we cannot see the SLA Latest Start and SLA Latest Finish in the SLA template. Is there a solution to restrict the task completion date and time?

Based on your screenshots it doesn’t look like you use SLA templates (it says “no commitments”), hence the PSO integration uses the defaults from the scheduling dataset.

Try adding SLA Commitments (you can use start-based or end-based) with work task applicability. These should constrain the start/end in PSO. Explained in NGSM and Scheduling Demystified.