Manifest Web Application | 2.8 Release Notes

Release Notes / Manifest Web / Manifest Web Application | 2.8 Release Notes

About this release

Below you will find the latest updates introduced on the Manifest Web Application on July 23, 2023. Version 2.8 focuses mainly a new Job UI and also the faults management system getting a major upgrade. 

Support notes

For additional information on each new feature or improvement, visit Manifest User Guides for updated documentation.

Overview of what’s new

General Feature Enhancements

  • A new Fault system has been designed so that Faults can be added, tracked and managed independently from Jobs and procedures.

    Now you’ll be able to do more than just simply flag a Fault – you can add a Fault and follow its path to resolution and review Fault history for any Asset. Here are some of the new features which will support the “Inspection Story” with the full cycle from Fault creation to Fault resolution accounted for.
    • Now you’ll be able to do more than just simply flag a Fault – you can add a Fault and follow its path to resolution and review Fault history for any Asset. Here are some of the new features which will support the “Inspection Story” with the full cycle from Fault creation to Fault resolution accounted for.
    • Add a Fault during a Job from a specific Job Step (Job ID and Step will be recorded on the Fault), or directly from the Asset.
    • Add a Job or Task to the Fault to require additional work and then keep track of the Open Work Items for Faults.
    • Easily and quickly view the Faults for any Asset. Find the desired Asset and from the Asset Details, view a list of any Faults (Open and Resolved). If working on the 3D application, users can view AR Fault Markers directly over the Asset along with the any leader lines pointing to the issue, or 3D Pen Notes.  This also includes a historical record of Faults associated with a specific Asset.
    • Resolve Faults after issues have been addressed. When The Fault is marked as “Resolved”, the date/time and user who resolved the Fault are both recorded.
  • Configure Fault Notes: Administrators can define what note types should be available and/or required when a user creates a Fault. 
    • i.e., if an Admin determines that Fault Note options should include only Photo and Pen, this can be configured for the domain. If the Admin would like to always require a Photo Note, this note can be marked ‘required’. This all happens in the new Faults page and will be applied for all cases where a Fault is added, on any platform.
  • View Fault Reporting on the Web Application
    • A new Fault page will display a list of all Faults in the Manifest domain, along with associated Notes and Work. This provides a single view directly from the users’ desktop to view all Faults across any Location and for all Assets in a domain.
    • Asset listings in the Web will now also include a tab to view any associated Faults
  • Create a Job or a Task: From the Web application’s Work page, users can add either a Job or a Task. Creating a Task requires only a Description and Location. (Note that 3D only supports adding a Task from a Fault and is automatically associated to that Fault and Asset
  • View, Assign, Share, Complete a Task: Tasks display a simple description and ‘done’ button to complete. They can be self-assigned, or assigned to another user. There is also a Share button to Share via Connect Chat.
  • It’s not just Jobs anymore, it’s “Work”: with the addition of Tasks, we now have 2 work types users can utilize to create and track their work. As a result, you’ll find that menus and various labels throughout the applications have been changed from Jobs TO Work. 
  • We have added the ability to “Unassign” a Job, even if it’s In Progress. This is ideal for those scenarios where a worker may need to unassign a Job they have not completed, but don’t know who will pick it up on the next shift. 

Client Considerations

Given this new 2.8 version introduces the NEW and IMPROVED Faults system, it’s important for all clients to understand the following:

What happens to old Fault Data?
Old fault data will NOT be available on version 2.8. New fault fata will NOT be available on version priori to version 2.8.

Which applications will still be using the ‘old’ Fault flagging feature?
Application versions using the ‘old fault system’ include:

  • 3D versions between 2.3 – 2.7.4
  • iPadOS versions between 2.3 – 2.5.3
  • Docker versions up to version 2.7

Note: If clients do not wish to update to the new Fault feature release yet, they would be able to continue adding and viewing ‘old fault data’ if they are operating on any of the above releases. Unfortunately, Web 2.8 will NOT display old fault data (unless we migrate old fault data – and even this is only a temporary measure.)

What if some users in the same domain are operating on different versions, or some platforms that so not yet support 2.8?
Clients should ensure all users are operating on the same version if they are using the Fault System and want it to be available across users + platforms. Docker users may benefit from waiting to update to 2.8 until the docker release is available.

Bug Fixes

  • Bug fix with importing a template via ZIP file


Point release update for 2.8


2.8.1 was pushed to Production on August 7, 2023

  • Fixed issue with onboarding templates
  • Fixed issues with creating faults from the Faults page
  • Updates to actions section for tsks on the Work History Page
  • Fixed issue with certain model types not uploading and converting properly
  • Fixed issue with archived chats not showing up on Connect
  • Fixed issue with Choice Notes duplicating when reordering them on the templates page
  • Query optimization


2.8.2 was pushed to Production on September 26, 2023

  • Extending the UI in Jobs that have Sub-Jobs
  • Displaying filtered faults when navigating to the Faults Page
  • Update the character count when adding a Fault from the Asset to be 100 characters
  • Bugfix when uploading models with a space in the name
  • Fixed an error with permissions error appear when users restart the page
  • Optimized faults query

Table of Contents
    Add a header to begin generating the table of contents