It is understandable that there may be cases wherein responded/closed Transmittal might still need to be recalled, but said recall must be agreed first by both the sender and the recipient.
This can be done by adding the process wherein the recipient will be notified and have to agree first on the recall before it will proceed.
Currently, the sender has the option to still recall a package that was already responded/closed which will only send a notification to the recipient that the package has been recalled. The recipient who might not have agreed on the recall, since it has a very crucial information on it and might be needed for future audit, can no longer do anything since the package has already been recalled and said recall is irreversible.
|
Practical use of functionality?
The sender will not be able to just recall a responded/closed transmittal, either intentional or not, without the knowledge of the recipient. There is this case in our project wherein the sender must have overlooked and recalled the wrong transmittal. This could have been avoided if this feature being suggested could have been available. |
|
|
What is the impact of not doing this?
Since the transmittal has already been responded, meaning the recipient already put their efforts on reviewing the documents and providing their comments and this transmittal has a very crucial information on it and might be needed for future audit, then the sender will just decide on their own and can just recall it. |
Hi,
May I know the status of this now?
Thank you for your feedback. We will investigate this request. At present, the sender should have the right to recall a package without the consent of the receiver. However, even when packages are recalled the information is not destroyed and is still available in PWDM.
I believe the best cause of action would be to look at being able to undo a recall if done by mistake. As creating a complex rule of sender and receiver agreeing on the recall could cause additional issues.
Recall is not recommended as it compromise the quality of your submission. It is Document Control task to ensure right information is uploaded in the system. Obtaining approval from recipients might prolong the process of delivery. I suggest, Bentley can set parameters when a transmittal can be recalled and only within a short period of time only e.g. less than 24 hrs. Responded or acknowledged transmittals should not be recalled at all. (If sender is unhappy with response, system has the unlock response function). Sender can select an acceptable reason for recall (criteria to be set as per best practice) If your reason for recall do not fall under the given criteria, then recall is not an option. Transmittal has to be responded or closed or you may resend a new version. For attachments being deleted once recalled, perhaps Bentley can park them to an archive folder for ease of retrieval if parties require information. (rare case but again once responded, it should not be recalled)