Skip to main content
Gathering Interest

Infield Checklist : Version management of templates

Related products:InField
  • August 16, 2023
  • 3 replies
  • 56 views

Abram Ziegelaar
Seasoned ⭐️⭐️

Use Case

  • Checklists are part of a formal process / Standard Operating Procedure
  • Checklist Templates are created & formally approved, requiring restriction of access to create & edit checklist templates
  • Checklist Templates are version controlled
  • Approval Status & person responsible are identified;
    • Created by
    • Approved by
  • Status
    • Draft
    • Approved

 

Why is this important?

  • In regulated industries, checklists form part of the Validated records of production
  • Without formal version management Checklists cannot be used as formal records

3 replies

Abram Ziegelaar
Seasoned ⭐️⭐️
  • Author
  • Seasoned ⭐️⭐️
  • August 24, 2023

@Tor Erik Kvisle  this is related to a discussion you had with Gary Goh recently


Anita Hæhre
Expert ⭐️⭐️⭐️⭐️
Forum|alt.badge.img+1
  • Head of Community
  • November 10, 2023
NewGathering Interest

Shun Takase
MVP ⭐️⭐️⭐️⭐️⭐️
Forum|alt.badge.img
  • MVP ⭐️⭐️⭐️⭐️⭐️
  • April 27, 2026

This is definitely a feature we would also very much like to have. Is there any update or progress on this topic?

Currently, InField templates do not allow users to undo previous edits. As a result, if a task is accidentally deleted or an incorrect change is made, there is no way to restore it. Because of this limitation, at our company we recommend that end users take their own precautions when updating templates, such as keeping duplicated backup templates.

Similarly, when users want to review older versions of a template, they need to manually create and maintain separate backup templates each time. However, this approach inevitably leads to a continuously growing number of backup templates, which becomes difficult to manage.

Ideally, we would like to see change history managed within a single template, with the ability to restore previous versions directly from that history. The version history functionality in Canvas is a good reference. That said, in Canvas, versions are created automatically by the system at certain points, so it would be even more ideal if users could explicitly save versions at a timing of their own choosing.