Time_worked field on Workspace

[Marek Blachowsk]

Hi. I have the following problem with the time_worked field on workspace.
When I save a record on the backend, the time_worked timer field starts counting down from zero. In addition, a record is created on the task_time_worked table. This is how it should also work on CSM Workspace.
Unfortunately, on CSM Workspace after clicking the Save button, the time_worked timer does not reset to zero, while a record on the task_time_worked table is created only after the first save from entering the record. Each subsequent click on the Save button, although the other data on the form is updated, a new record on the task_time_worked table is not created.

I would appreciate your help in solving the problem.

[Dan Sundquist]

We also have this issue in CSM/FSM Configurable workspace. 

If you manually manipulate the field in Configurable (Edit timer or pause/unpause), the next save will create a task time worked. However, if you do not, the form does not see that 'current.time_worked' has changed after the initial save, and therefore never triggers the business rule that would create a Task Time Worked record.

In Legacy workspace, we do not have issues with timer fields. A Save of the record will reset the in-form timer to 00:00:00 and any subsequent saves will recognize that the timer on the form has changed values, therefore creating the task time worked record on each save.

We've escalated to HI Support, and they've created a Problem: PRB1635771.

[Marek Blachowsk]

We also reported the problem and according to HISupport it is currently being fixed 🙂

Thank you for your answer 🙂