FormIO how to update DCDs

Summary

This document serves as a guide to help you understand the process flow of FormIO features. By leveraging these features, you can effectively manage various forms/DCDs states and mitigate problems that may occur in current environments ( DTAP ). Whether you're an end user, this document provides the necessary information to streamline the workflow and improve productivity.

Introduction

We're excited to introduce you to a feature within our development process that enhances efficiency and ensures the smooth operation of our application: FormIO's "Save as Draft" feature. While this may sound technical, we'll explain it in a way that's easy to understand, highlighting its importance and how it benefits our team and projects.

Understanding FormIO

Our development team uses FormIO to create and edit dynamic web-based forms/DCDs. These forms/DCDs are essential for users to input data, submit requests, and interact with our systems seamlessly.

The Challenge

Our developers frequently require modifying or fixing these Forms/DCDs during the development stage. Nonetheless, applying these modifications directly to the live versions of the Forms/DCDs can pose potential risks. Any unintentional errors or incomplete changes may interrupt our applications' user experience or functionality.

The Solution: FormIO Feature

FormIO provides a convenient solution to this challenge through its "Save as Draft" feature. When developers edit or fix existing Forms/DCDs, they can save their progress as a draft rather than immediately deploying the changes to the live environment. They also must make the revision note.

How it Works

• Saving Progress: When a developer works on a form within FormIO, they can save their changes as a draft. This ensures that the modifications made are stored but not yet applied to the live version of the form.

• Revision Notes: Developers must also include notes or comments regarding the changes they've made. These notes are saved alongside the draft, providing valuable context for future reference.

• Preventing Unintended Deployment: By utilizing the "Save as Draft" feature, developers can continue refining the form without the fear of accidentally deploying incomplete or erroneous changes to the production environment.