The ability to rollover, or supersede a form would be advantageous in any situation where there is a probability of the form being reset to an earlier status. Or the form is formally issued (to a client, customer, contractor) and will be reused.
For example – an inspection is required on an asset each month, the checklist is completed and issued to the client. The following month the checklist is moved back in status to draft, the inspection undertaken and the form content added to. Then issued again. In FieldView the original record is lost. However if there was a function to supersede the form then the original record can remain unchanged and a new record would developed, with easy traceability to the previous record etc…
Example 2 – an Non-conformity notice is issued, this is actioned by the contractor and the designer, however the designer disagrees with the contractors proposal. The status is moved back, the content edited and the form moves forward. However again the original record is not retained (within FieldView)
Dear Viewpoint Suggestion Box contributor;
We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs.
Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.