Use case is a CSM will move out the date on a Task that is a part of the playbook and there is no way to track this change or see why the change was made. Would love to have a way for the user to identify why the date was pushed out.
Hi Dan, the CTA original due date does not appear on the CTA so maybe there is a configuration setting I am not aware of. However, the ability to have a reason (mandatory) as to why we are moving the date and reflecting this in the CTA would be ideal. We are currently using the process as you describe above.