Epsilon3 Changelog #24: Table of Contents, Failed Steps, External Data Integration
It was great to meet so many of you in person at Space Symposium! Thanks for a great time and for all of your support!
We’re continuing to quickly build out our product vision – see our new product summary here.
This cycle, we added a new table of contents to help navigate your procedures, optional failed steps to help track your procedure performance, and have started to bring in external data to make your procedures more efficient and further reduce errors.
Comments, additional requests and feedback are always welcome on our product portal page or via email at support@epsilon3.io.
P.S. Laura was recently featured in Business Insider as one of the 15 of the most influential women in aerospace.
- Max
New! Table of Contents in Runs
One initiative to help you keep track of your procedure at a glance!
View all section names, step names, and step states in your procedure within the table of contents, located on the right side of the Run page.
To make best use of your screen real estate: On tablets, the ToC is hidden for vertical orientation and visible for horizontal orientation.
New! Failed Steps
Moving towards helping you better track your procedures, you can now mark a step as failed by navigating to the step’s three-dot menu > FAIL STEP.
The failed step will be highlighted in red with all inputs preserved in the step.
The Run Progress Bar now displays the failed step percentage. However, rest assured this will not change your ability to continue the procedure.
New! Connect To External Data
A powerful new tool to extend your Epsilon3 functionality and a first step towards deeper software integrations!
Connect to existing data such as parts & inventory, work orders, support tickets, requirements, and more.
Add references in your procedures to items in your external tools, reducing errors by allowing only known values (serial numbers, ticket numbers, etc.).
Item references can be added during procedure design time by using the new External Data content type and searching among the configured data types.
You can also link during a running procedure by using the new External Data field input type when adding and configuring field inputs in procedure steps.
Served dynamically through the Epsilon3 API. Let us know if you’d like a demonstration, a sample integration, or an API key to get started!
Improvements
The run history tab now loads at lightning speed!
More offline capabilities: you can now repeat sections offline.
Style update! Field inputs now have consistent style and spacing.
We updated the run progress bar to include new colors for completed, skipped, and failed steps.
Fixes
Fixed a crash when signing out from the procedure edit page
Fixed an issue where users could deactivate themselves
Fixed an issue where dragging and dropping content in a header was not being persisted on save
Fixed an issue where “step has changed” indicator was sometimes shown incorrectly in reviews
Fixed an issue where telemetry ranges with min or max of zero were not displayed
Fixed an issue where clicking the "include in summary" checkbox would not always work on Safari
Fixed misalignment of save button for variable inputs with errors
Interested in learning more? Click below to get started.
