Projects can now contain up to one hundred vitals (they were formerly limited to fifteen) and users can now personalize their own views and order of vitals for each project type.
User-specific personalization means, for example, that a project type could include 54 vitals, and the attorney could view the 13 most important vitals for them, whereas the accountant could view the 10 vitals they most need.
Note: Vital view is customizable based on user and on browser, so a user can configure different settings for different browsers or different devices.
Set Up in the Customs Editor
Just as before, vitals can be added and ordered in the Customs Editor Advanced tool. In the Vitals tab, click Add Vital to add a new vital, and click and drag the dots next to a vital to reorder it.
Note: First Primary is currently supported. However, other Protect Team vitals are not yet supported in this beta. If you have Project Team vitals set up, those vitals can be viewed using the Legacy Vitals toggle in the project.
Suggestions
Given the expanded number of vitals, and the personalization available for each user, you may consider adding additional vitals, even if they will only be useful for some members of the team. Then, other team members can choose to make those vitals not visible in their own vital views.
Once you’ve set up your vitals, ensure that your team knows they can personalize their own views of vitals!
View in the Project
Vital views can now be customized for each user for each project type. Configuring the vitals in a project will affect how the vitals are configured in all other projects of that type.
In the project, open vitals and click Configure at the bottom of the flyout.
In the configuration flyout, you can select the order and the visibility for each vital. Click on the dots next to a vital and drag it to the desired placement to change the order.
For any vitals you do not want to view, click on the eye icon to hide them. Hidden vitals can be found in the configuration flyout under Hidden.
If you’d like to reset the vitals to the order chosen for the project type, with all vitals visible, click Reset to Defaults.
Troubleshooting
Read below for some common questions regarding expanded vitals. To review errors that take place when you turn on the beta, read the subsequent section.
Rerouted Vitals
If you click on a vital and are rerouted to the project’s first section (usually the Activity feed), it may be because:
- you do not have access to the section the vital is in
- the vital is a legacy incident date field and the section it refers to has been deprecated
Project Team Vitals
The vitals beta does not support project team vitals at this time. We are actively working on supporting this, and hope to support Project Team vitals by the end of Q1 2025.
New Fields Appearing as Vitals
If you created a field, but it is not available to be added as a vital, take the following steps:
- Check if the field is in a collection section: Both legacy and expanded vitals support summaries of collection sections—for example, Count of Items or Sum of Currency Fields across all items. However, vitals does not support item field-specific data in collection sections.
- Check if the vital is already created: Double-check to ensure the vital you are trying to add is not already in use.
- Update the field: Update the new field by adjusting it (for instance, adding a space, or altering the text, saving, and then altering it back and resaving).
Fields Data Not Showing in Vitals
If you entered data in the field in-project, but the vital in the panel still shows as empty, take the following steps:
- Double-check the field: Ensure the vital you create references the field you expect it to reference. If you have identical fields across multiple sections, you may have selected the field name for a field from a different section.
- Update the field: Update the field in the Customs Editor by adjusting it (for instance, adding a space, or altering the text, saving, and then altering it back and resaving).
Turn on the Beta
To turn on expanded vitals for their Org, a user must be an Org Admin and must have access to the Customs Editor (granted in the Advanced Access tab).
Click the Main Menu and select Advanced from the dropdown. Click Customs Editor in the left side menu.
If prompted, select your Org, and then select any existing project template. Click the Vitals Beta button.
Clicking this button opens a modal where you can review important information about the beta. If you aren’t ready to turn it on, you can close the modal without changes.
Note: You are able to disable the beta once it’s been turned on. However, if you disable and then re-enable it, any changes you made to vitals during the first enablement will be lost.
Once you’ve reviewed the information, select Enable Beta.
Once you’ve selected to enable the beta, migration will run to set up your legacy vitals in the beta vitals version. This setup can take 10-60 seconds.
Enablement Troubleshooting
If the data is not migrated successfully, you’ll be able to review the errors in the modal. You can also click the copy icon next to "Migration Results" to send it in a support ticket if needed.
Read below for explanations of the most common migration issues.
- Invalid Field: In legacy vitals, you may have encountered vitals that had the prefix "Invalid!". These were vitals that had an invalid field. These vitals’ definitions will not migrate and will return as errors.
- No legacy vital definition fields found for project type: This response means that no vital definitions were ever created for the project type. This message typically returns when an Org has a test project type with no vitals set up.
Comments
0 comments
Article is closed for comments.