Support Forum

[victor]

Hello,

We have a problem: When a user add an incorrect message he can delete but the handler dont return to the previous one.

I think that the system must allow only delete the last message and undo the changes over the task that this message has produced.

Maybe one could delete more than one message but always he must delete every message from most older that he want to delete to the last. And always recovering the right task situation.

Thanks

[admin]

Hello,

We have a problem: When a user add an incorrect message he can delete but the handler dont return to the previous one.

I think that the system must allow only delete the last message and undo the changes over the task that this message has produced.

Maybe one could delete more than one message but always he must delete every message from most older that he want to delete to the last. And always recovering the right task situation.

Thanks

Its quite difficult to implement and users (generally) should not delete messages (and tasks) at all - this is "last choice" for manager. Deleting messages can cause problems, such as
- somebody start task, but user delete message when somebody else assign their
- user enter message with hours, receive money and delete it, this problem is very actual for us.

I more like concept used in accounting - if some operation is invalid, you should create another one that rollback invalid. In TrackStudio should be useful to add special "rollback" message type that step back (move from resolved to processed, from processed to new, etc).

[willettsj]

I've implemented sucha workflow step (only available to managers) for this very reason, so if users move something on too far by accident, you can easily rollback.

[victor]

I've implemented sucha workflow step (only available to managers) for this very reason, so if users move something on too far by accident, you can easily rollback.

I see. I think that Maxim has a good point of view about this theme and willettsj has a good solution allowing only to the managers do this rollback procedure.

Thanks!

[victor]

I've implemented sucha workflow step (only available to managers) for this very reason, so if users move something on too far by accident, you can easily rollback.

I see. I think that Maxim has a good point of view about this theme and willettsj has a good solution allowing only to the managers do this rollback procedure.

Thanks!

Only one more question... final states... Is there any problem to add a rollback message from a final state to other state?

Thanks

[admin]

Only one more question... final states... Is there any problem to add a rollback message from a final state to other state?

"Rollback message" - what do you mean ? Its no problem to add message type from a final state, standard workflow use message type "reopen" (from "closed" to "processed")

[victor]

Only one more question... final states... Is there any problem to add a rollback message from a final state to other state?

"Rollback message" - what do you mean ? Its no problem to add message type from a final state, standard workflow use message type "reopen" (from "closed" to "processed")

Ok, thanks! :)