Hello James,
Thank you for sharing your workflow, that's really helpful to see your complexity. For templates available across FormSpaces, this is a great feature request. We are always open to hearing feedback on how we can make your work go a little smoother, and although we can't guarantee a fix or timeline, I'll be sure to pass on your request to the team.
As you mention, that's true you can create templates to use within a form only. If it's one single form, I can see what you're saying, it will indeed take some time to build out that Conditional Logic. That said, many of our customers have really complex forms out there in the world accommodating what the fillable PDF would, and as you say you've contemplated it, it may be worth the upfront time investment making the switch.
Ruling that out, if you're sure you want to have separate forms, and you know that within those forms there will be repetition, save time by creating a 'boilerplate' version of the form. You could have a FormSpace just for your boilerplate forms, and as needed, you go in there and make a copy of a form into other FormSpaces to edit. We cover that over in the TrueContext University Level 2 training, exploring the differences between moving and copying across FormSpaces.
I hope that helps out in your next steps! Let us know how it goes and I will be sure to pass on your notes.
------------------------------
Erika Lapenat
Technical Content Developer
TrueContext University
------------------------------
Original Message:
Sent: 07-25-2024 17:55
From: James Leschinsky
Subject: Preventing accidental "discard changes"
Hi Erin,
Thanks for the reply.
Essentially our company makes electric heaters and different controllers for those heaters. We have to inspect and test the heater, but we also have to inspect and test the controller. There are many different kinds of heaters (each with their own form), and many different kinds of controllers (each with their own form). Sometimes one controller can control multiple heaters or multiple controllers for one heater is also possible.
The typical workflow is to first do de-energized inspections/tests of the heaters and controllers while documenting on two separate forms, then turn on the power and do energized tests on both.
Currently we use fillable PDFs where we can easily combine the two forms into one document and switching between them is as simple as sliding your finger across the screen to the next page.
I have contemplated combining the forms into one but it leads to a complicated "super form" with a massive amount of work creating conditional logic to cover all possible combinations of heaters/controllers.
I was also hoping "templates" would be my silver bullet, but then I realized it only lets you use the template within a form, not across forms.
Is there a feature I haven't found yet that lets me copy a form page/section from one form to another form?
------------------------------
James Leschinsky
Field Service Engineer
nVent
Original Message:
Sent: 07-25-2024 09:55
From: Erin Longhurst
Subject: Preventing accidental "discard changes"
Hi James,
There's currently no way to disable the "Discard Changes" option at the team or form level, unfortunately. I can understand the fears of data loss when people're working quickly and want to swap between forms -- it's definitely a matter of training and familiarity to prevent such.
Is it common to have two separate forms to do simultaneous processes, like the inspection you've mentioned? Are they always the same inspection(s) paired together, or does it vary by site/job?
Warmly,
------------------------------
Erin Longhurst
Product Manager
TrueContext
Original Message:
Sent: 07-24-2024 17:34
From: James Leschinsky
Subject: Preventing accidental "discard changes"
Is there a way to disable the "Discard Changes" button when closing a form and just default it to always save as a draft instead?
Right now our workflow requires users to flip between multiple forms while onsite (e.g. inspecting two different things simultaneously).
We're still in the implementation process, but I'm confident we are going to get techs complaining about accidental data loss all the time despite the "are you sure" prompt.
------------------------------
James Leschinsky
Field Service Engineer
nVent
------------------------------