Skip to main content

Hello,

In FSM, I'm having an issue with the fields plan_start_dttm, plan_end_dttm, plan_travel_start_dttm and plan_travel_start_dttm of table Task.

At the moment the implementation at the client is using only FSM BackOffice and not PSO. Hence all programming will be done manually by the dispatchers

Basically, my purpose is to avoid that these dates are calculated, so I deleted the FSM Client Script associated to the custom code in UI Designer (image below).

However, I have found that these dates are calculated despite the changes made in custom code.

To solve this issue, I created a client script that put the dates empty.

Does anybody have any suggestion? 

Does anybody is aware of any logic or process that are related with these two fields ? 

Hi @AccCatOli 

Plan Start is mandatory and AFAIK is calculation is hard coded. Plan End will take the Plan Start and add the task duration. I dont think you can avoid poulating these fields.

What is the purpose of your functionality? Why do you need these fields empty?

Cheers!

Hi @Shneor Cheshin 

Thank you very much for your feedback.

I also notice that the fields plan_start_dttm and plan_travel_start_dttm are automatically filled with the value of the task creation date. In addition, the fields plan_end_dttm and plan_travel_end_dttm are obtained by adding the plan_start_dttm and plan_travel_start_dttm plus the task duration, respectively. This means that the values are obtained by the following calculations:

  • plan_end_dttm = plan_start_dttm  + duration
  • plan_travel_end_dttm  = plan_travel_start_dttm  + duration

Can't it also be avoided that the travel fields get these values? The fields plan_travel_start_dttm and plan_travel_end_dttm are not mandatory.

Hi @AccCatOli ,

As @Shneor Cheshin has mentioned, it is not possible to override the setting of plan start and end, plan travel start and end dates with any configurations as everything has been written down in the task policy (baseline code) itself. Plan_Start_Dttm is considered as the base to calculate and insert the rest of the travel times based on the plan task duration which is applied through task level and if not, through the application parameter default_task_duration. Even though if you try to change the duration values as null, still the duration levels are set to 60 mins by default by the code as this is a necessary step to create a task. Hence, the only way to achieve this would be to write custom code to override the baseline behavior of the application which is not really recommended as this can severely affect the scheduling concepts in FSM / PSO. Only the user is allowed to change the time fields manually here.

Hi @SAMLK 

Thank you very much for your feedback.

Yes, I verified what you mentioned in the first part of the response.

So, if I understood what you mentioned in the last part, these four fields (plan_start_dttm, plan_end_dttm, plan_travel_start_dttm and plan_travel_end_dttm) are affected by communication between FSM and PSO. Do you know in which moment?

Reply


Terms & ConditionsCookie settings