Confirmation Change Requests and numbering
Readers submitting a Change Request should receive a confirmation by e mail and all Change Requests should be numbered. Currently the Change Request disappears after submitting it, leaving the Reader unable to track progress or to remember the Request was submitted at all. Numbering of each change request enables Readers/Document Owners to track and process them effectively for the next Revision of the document.
3
Comments
I find this a very good idea since we are struggeling with the same issue. Maybe I can submit another request which is simular to yours Arthur. When submitting a Form, the Submitter is receiving an Email indeed but after that we are not able to keep the Submitter up to date (wheter his request in the Form is solved or was noticed). Right now we are writing an Email seperately after we finished the request given in the form. It wold there be great to also number the forms that will be received by the Admins and also be able to answer directely withing the form.
Hello Arthur and Natalie :)
I love your energy.
We have been discussing different ways to rework Change Requests and apply improvements to the functionality.
From your descriptions I was able to deduce the following improvements:
I would like to challenge the last point:
If Readers can always see the status of their Change Requests in say a side bar in the reader. Will it then be needed to also send an email to them informing them that they have submitted a Change Request?
Hi Stefan Baudoin Bundgaard thank you for keeping us up to date. In my opinion and for this topic I think it is not needed to send an extra email, when they can just look into the system to see their submitted change requests. But maybe it would make sense that an email will be sent, when the change request is solved or rejected, because some of our Users do not login on a daily basis or probably forget, that there is an open change request.
I agree with Natalie; Readers going through the effort to submit a change requested should be kept abreast on the progress. Its OK not to sent a confirmation after submitting BUT Readers should be able to -easily- find their submitted requests and be informed about a change in status. The system should advise the Reader about the procedure for Change Requests. So, after all it might be the easiest to sent a confirmation e mail after all?
Thank you very much both of you. This will feed into my improvement epic for reworking Change Request.
I might not send emails in the first version, I try to be a little careful with the amount of emails we send out, since the more we send, the less value they add.
MANUALS-7009
Just want to poke at this case as I find it very interesting. I've said it a few times before, but once again: I fully support ideas that push WM into being a productivity tool. A great document management system such as WM has the side effect of adding complexity to an editor's daily work, so ideas to make WM more task-management-oriented are, for me, always welcome.
My only concern here is the sending of emails. For me, an option to disable it via admin settings would be preferable. I agree with Stefan Baudoin Bundgaard on this point. Emails should be used sparingly. Otherwise, they lose their purpose and become spam-like to the target persons.
I fully support the numbering of the Change Requests as an improvement, in order to keep track of Change Requests which have been submitted over time, and how many. It would be good if the CRs can be compiled in one place or extracted somehow, maybe through a report?
When clicking on the link in the e mail notifying me of a change request, the system opens the Reader and shows the document. Why not directly to the editor function so the change can be done immediately? Saving time in case of simple editorial changes for example..
I agree that numbering Change Requests would be a great improvement and would fully support adding functionality which allows users to track the CRs they have submitted, as we had this functionality in the system we used before WM and users do seem to miss this. I agree that emails are not really necessary if users can view the CRs they have submitted in WM themselves. Editors can also manually prompt an email to be generated by adding a comment in the CR task, I believe.
Please sign in to leave a comment.