All,
Am trying to close out audit checklists and am hitting a small hitch - where entries in the 'Completed By' and 'Completed On' fields, disappear when the record is saved.
Has anyone else found this, and is there something being done to remedy it?
KB
?
Hi Ken,
This isn't an issue we have experienced before. Can you drop support an email at support@gaelquality.com with some additional details of the steps you are going through?
Alan BlairSupport Engineer, Gael LtdE: support@gaelquality.com || T: +44 1355 593400
Why not visit our new online knowledgebase for all your Q-Pulse 5 problems and usability queries?
This has happened to me too. I don't know why and found that it does not happen every time. In my case as the "Lead Auditor" I was completing several audit records at the same time and found most audits would save the name with the checklist and one would not. I have just retried in V5.5 by reopening and trying it again and that one audit record does not save the checklist completed by and date.
Things that I originally thought and have ruled out are:
The audit was performed by another person and I am entering it for them. I have done this for other auditors and found that the checklist does save properly.
The checklist completion date does not match the audit date. I have tried to change the date to match the audit date and that one record still does not save correctly.
I have no idea why it happened and have not been able to redo this with another audit record yet. We have just completed our next internal audit and are in process of entering the details to save and close it out. I will reply with results.
Update: I just closed two new audits, one audit record another person filled in their checklist and the system saved their name and date.
With the second audit, I had to fill in the checklist, but it did not save the name or date. I tried my name, the other auditors name and it didn't work. The differences I have noted are: the second audit was done two months ago and I am trying to backdate the checklist completion to coincide with the actual dates, with the first audit the checklist was entered prior to acceptance of the findings summary, I accepted the findings summary on the second audit prior to completing the checklist. I am not sure any of these are really reasons that the checklist would not save a name and date, it doesn't seem to make any sense.
Folks,
Feedback that I have had from Gael points to a problem with the 'Refresh' function within the record.
Since this has been noticed, the same issue has appeared in a number of other records (not just within the Audit module). While the informatin does ultimately save, it is often quite unnerving, if you have just completed a large note, to see it disappear.
This would seem to be a system-wide defect. Can Gael please confirm that it will be rectified in the next release?
Ken
I was about to register this very finding tonight ... only to see it already here. The "completed by" isn't stored no matter what I try. This is an audit that was "overdue" just in case that matters.
A similar issue is when it does register the "completed by" and "completed on" I can't seem to print this even although it is on screen.
I'm on v5.2
Bubonic,
That's exactly my point. Feedback that I am getting from Gael suggests that we need V5.5 before the refresh issue would be resolved. It seems to me to be a poor show for such a basic function of the system to be defective so late in its development.
Version level really shouldn't matter here. Hopefully we will hear more at the user groups.
I don't think that V5.5 fixes the issue either. I have found that it still happened to me even after the version upgrade.
This is an issue that has already been passed to our development team. The refresh issue is present in 5.51, however please note that with this issue no data has actually been lost but rather is simply not being displayed. If you close out of the record (returning to the list view) and push the F5 key to refresh the data displayed, then re-enter the record the correct results will be displayed.
After consulting with our testing department, this issue is already being investigated and will be resolved in out next release. Whenever an issue is raised, a solution will be identified and implemented at the earliest opportunity. Ken you mention that version level shouldn't matter, however any updates, patches etc applied to the software require to be version controlled. Any changes made will go through our development process then test cycles before release and with each release whether its internal or external will require a change to the version level. Therefore if you report an issue which has been resolved, you will be required to upgrade (and thus changing the version number).
If anyone would like to track this defect, the reference number for it is BC-5964, and if you contact support via email we can append this to your account and notify you when the solution has been released. Ken, you also mentioned that you have seen this issue in other areas of Q-Pulse (not just the Audit module). Would you be able to email support with some additional details of this so we can investigate further?
Alan,
Thanks for your response.
What I meant about the version level was that such a basic function of the system should not still be defective so late in the system development. To be honest, it does question the level of testing that is done.
With regard to the other areas, where this refresh problem exists, I have noticed it when entering and saving notes within the Asset module. When the note is typed, you 'OK' it and it all disappears. Not until you close and re-enter the record does it appear.
Hi Ken,Thanks for the post.
I would just like to reinforce Alan's response that the issue referred to is related to timing and refresh; the integrity of the underlying Q-Pulse data is preserved. With regard to your comment on the level of testing, as you know, Q-Pulse has many facets to its operation and when functions are combined with other functional and non functional requirements (e.g. Add new Non-conformance, with/without security, with/without audit logging, with/without messaging, label customisation, XP client, Vista client etc. etc.), you begin to understand the permutations that exist and the challenges that it brings to Test.
These are challenges that we don't shirk from and our Test Strategy, delivered through a balance of manual and automated tests, does provide a comprehensive coverage throughout the development lifecycle from unit testing through to functional, performance and process testing; however we do recognise that we will not "catch" everything all of the time, but our underlying principle of continuous improvement does ensure that when issues are found we develop our supporting processes to move forward positively with Q-Pulse.
Regards,
Paul
Paul Callaghan Products Director Gael Ltd t: +44 (0)1355 593 400 f: +44 (0)1355 579 191 w: www.gaelquality.com
Gael LtdOrion House, S. E. Technology Park, East Kilbride, Scotland, UK. G75 0RD T: +44 1355 593400 F: +44 1355 579191 E: info@gaelquality.com
Registered Office: 1 Cambuslang Court, Cambuslang, Glasgow, Scotland G32 8FH. Registered in Scotland. Company No. 208191. VAT Registration No. 886 6848 45.
Copyright © Gael Limited.