Comments
Users across our business have been complaining that this feature was available in BC14 but has been removed from BC23. They need this so that they can identify where an approval request is stalled and chase the appropriate person for action.
Another backwards step between the on-premise BC and Cloud versions.
This functionality is critical to our business processes for querying Invoices and other documents before processing. Being able to Notify another user of a question and maintaining a record in the document of the questions and responses builds an important audit trail, which is just not possible using Teams or eMails.
Once a batch has been approved you cannot make any changes to the amounts on the line anyway without gaining re-approval, which is what you would expect as it prevents a users from adjusting values and exporting the BACS file with amounts that were not approved.
However, since the protection above is in place, there seems no benefit in then adding another approval requirement after the BACS file has been created, this is just adding delays and inefficiency into the process. This is just not required and provides no additional financial control protection whilst frustrating users!!
Our organization needs the ability to template everything on the Task Templates
Task checklists
Creating and using Buckets
Templating the columns on the Tasks Lists in this order:
Name | Quick Look (so we can see the checklist items) | Bucket (for Status of the Work) } Assigned to | Start | Finish | Duration | Effort | Priority (have the ability to change the options) | Depends on