I would like to confirm the OOTB behavior of FSM regarding the below situation:
If we create a time_commit (during the get appointments functionality for example), the plan start of the task is updated with the start of the time commit and all of this is sent to PSO. However, if we change the start of an existing time commit, this information is sent to PSO. The SLA of the task in PSO is updated but the plan start of the task isn't updated.
Could you please explain/ confirm why the behavior is different between insert and update?
Best answer by Aaron.Sleight
Yes, the plan start dttm is set initially and then not updated in the scenario that you describe unless it is manually updated or if PSO commits the job (i.e. locks the assigned resource and scheduled dttm).
Previously, we allowed the DSE broadcasts to update the plan start dttm, but the volume and frequency of those updates is too much and when dynamic scheduling is being used, then each of those updates really has very little value until the assignment is actually committed and will not undergo any further changes.
Yes, the plan start dttm is set initially and then not updated in the scenario that you describe unless it is manually updated or if PSO commits the job (i.e. locks the assigned resource and scheduled dttm).
Previously, we allowed the DSE broadcasts to update the plan start dttm, but the volume and frequency of those updates is too much and when dynamic scheduling is being used, then each of those updates really has very little value until the assignment is actually committed and will not undergo any further changes.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
