Epsilon3 Changelog #29: Field Input Conditionals, Date/Time Field Input, Redline Procedure Headers
This is a more succinct Changelog given our long holiday weekend, but we wanted to get the new features out to you as quickly as possible!
Quickly iterating on our conditional functionality, you can now use field inputs to determine the procedure flow. We have added a new date/time field input type to help you better capture your data. Finally, we’ve expanded our redlining capabilities to now include procedure headers.
Check out last week’s article in Breaking Defense about how Epsilon3 is partnering with the Space Force and other teams throughout aerospace and defense. Also, it was fun to be part of Lux Capital’s “Securities” podcast this week in an episode titled “Shoving the rocket into space with your bare hands.”
As always, please keep the feedback coming!
– Laura
P.S. A big thanks again to the AWS Space Accelerator. We had a great time meeting all the teams and appreciate all the support! If you’d like to join for Demo Day, sign up here.
New! Field Input Conditionals
We’ve extended the step conditional functionality to now support field inputs!
In addition to designing procedures with branching logic based on step success or failure, you can now configure branching logic based on field input values.
To get started, add a field input list or custom list to your step, then add conditional logic and select from either the step status or your field input. You can then easily configure the next step depending on what list value the user selects when running the procedure.
Because we now allow branching determined by either steps or field inputs, we’ve renamed “Step Conditionals” to simply “Conditionals.”
Improved! Redline Procedure Headers
We now allow you to suggest edits on procedure headers! Keep track of critical notes anywhere they may be.
Click the "Suggest Edits" button and the pencil icon next to the item you'd like to suggest edits on. Your suggestion will appear in the next draft of the procedure.
Suggest edits on text, note, caution, and warning blocks, or even the header name.
Need to require approvals for suggested edits? Head to the Settings page and toggle "Require approval for new suggested edits" on.
New! Import Procedures from PRL Format
To help simplify bringing new procedures into Epsilon3, you can import procedures directly from Procedure Representation Language (PRL) file format.
Includes support for procedure title, sections, steps, substeps, field inputs, notes, cautions, warnings, and tables
New! Date/Time Field Input
We’ve heard your feedback that the timestamp isn’t the only time you’re looking to see and have now added a new type of field input to let you insert any date/time.
Save when an event actually happened if working asynchronously, or tell another team when the next step/procedure should be started. Works great with field input references!
Supports date, time, and combined date and time input types.
Improvements
We've made extensive performance and infrastructure improvements, including reducing the query time for the master procedure list by 10x in some cases.
We now support importing procedures with step headers and a few additional formats. Please reach out if we can help you get your existing procedures into Epsilon3!
Fixes
Fixed an issue where data input in runs was being saved back to procedures in some scenarios when redlining steps requiring signoff by multiple operators.
Fixed an issue where users were not able to redline field input number types with a range.
Fixed an issue where users were able to accept suggested edits while not participating.
Interested in learning more? Click below to get started.
