Settings and activity
25 results found
-
4 votes
An error occurred while saving the comment 
Harsh Khanna
shared this idea
·
-
3 votesHarsh Khanna
shared this idea
·
-
3 votesHarsh Khanna
shared this idea
·
-
3 votesHarsh Khanna
shared this idea
·
-
4 votesHarsh Khanna
shared this idea
·
-
3 votesHarsh Khanna
shared this idea
·
-
4 votes
An error occurred while saving the comment Harsh Khanna
commented
When an incorrect document is attached and the ticket is approved and closed, we can replace the document from the Work Request Search screen if we are the responsible person.
However, there is no record or trace of the replacement within the system.
While there is a comment field available during the replacement process, the inputted comments are not displayed anywhere on the ticket.Need for Traceability:
Our on-site team has expressed the need to confirm the history of document replacements within WebCentral for evidence and compliance purposes.similar functionality like, Document Version Screen has the similar function (System --> Archibus Administrators Applicatoin Configuration --> Revisions by Document)
Can we also get the same functionality in the WR screen.
Harsh Khanna
shared this idea
·
-
5 votesHarsh Khanna
shared this idea
·
-
3 votesHarsh Khanna
shared this idea
·
-
5 votesHarsh Khanna
shared this idea
·
-
20 votesHarsh Khanna
supported this idea
·
-
5 votesHarsh Khanna
shared this idea
·
-
5 votesHarsh Khanna
shared this idea
·
-
7 votesHarsh Khanna
shared this idea
·
-
6 votesHarsh Khanna
shared this idea
·
-
6 votesHarsh Khanna
shared this idea
·
-
5 votesHarsh Khanna
shared this idea
·
-
5 votesHarsh Khanna
shared this idea
·
-
17 votesHarsh Khanna
shared this idea
·
-
5 votesHarsh Khanna
shared this idea
·
Currently, when users fill out a checklist in the Onsite or Webcentral app, each data entry (e.g., temperature, pressure, pass/fail result) is saved without a visible timestamp indicating when that specific item was recorded. While the overall checklist may capture a submission time, individual field inputs—especially those filled out over time during inspections—do not reflect the actual moment of entry.
This limitation is particularly problematic in scenarios where:
Checklists are completed in multiple stages throughout the day.
Multiple users contribute to the same checklist, such as in handover situations.
Regulated environments (e.g., manufacturing, healthcare, facilities with ISO/QMS audits) require detailed logs of who did what and when.
Impact
Traceability Gaps: In audits or incident investigations, it becomes difficult to verify when an item was inspected, making compliance validation incomplete.
Compliance Risk: Fails to meet documentation standards for industries requiring timestamped logs (e.g., GMP, ISO 9001, FDA 21 CFR Part 11).
Accountability Issues: Without per-field timestamps, it's hard to detect delays or irregularities in inspection routines.
Requested Action
Display an automatic timestamp next to each checklist entry field—ideally with both time and date—and optionally include this metadata in exported reports.