Clarity around expected start field

[Nikita50]

 How Expected Start field on change_task form is populated.

[Community Alums]

Hi @Nikita50 ,

In the below Script Include 'WFCreateTaskActivityUtils', at line number 38 the Expected Start field value on the SC_TASK is being set.

https://ANY OOB INSTANCE.service-now.com/nav_to.do?uri=%2Fsys_script_include.do%3Fsys_id%3D5c8247410... 

To make this field value blank, Customer can set a NULL value to variable expected_start in the script include.

[Nikita50]

Thanks you Sandeep. I am trying to understand it for change task form not catalog task.

[Dr Atul G- LNG]

Hi @Nikita50 

This field has no use or relevance to the Change Task form because it is inherited from the Task table. While it’s available, the Change module uses its field to track the change date. So, there’s nothing to worry about. However, you can use this one if you're doing an integration and need a date-type field. Similarly, if you notice in the Incident table, there are two state fields: 'State' and 'Incident State.'

[Nikita50]

Thank you Atul, actually my client wants to know the behavior of this field. For some records, this field is empty, for some it is a random date and for some it is same as change task created date. 

is this handled by some code or not?