Hi @Shneor Cheshin,Thanks for your answer.The custom_input_xml can be seen in the view information of the fields presented in the mass update pop up. Actually, this cannot be found in the FSM Metadata and it is not created in Custom Metadata.Through a client script, it allows me to change the behavior of these fields, to be read only or not according to the business requirement. Best Regards,Cátia Oliveira
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?
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 + durationCan'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.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
