DATAMARK VEP v2024.4.1

Release Notes

 12/16/2024

Admin

Moved “Manage Schemas” to the Utilities Page (E, V, S)

The functionality to manage schemas has been relocated from the Admin Module to the Utilities Module.

Updated Approval Status in the Admin Widget (E)
 Once an upload or edit is approved in the Admin Widget, the approval status will display as “processing” instead of “pending” while the request is completed.

Downloads

NENA V2 Download Enhancements (E, V, A, S)
Updates have been made to the NENA V2 download to ensure the correct domain values are included.
 

Uploads

Bolded Select Option in Upload Field Mapping (E, V, S)
The “Select” dropdown is now bold during the upload process. This improvement will visually alert users to any missing fields during field mapping.
 

Dashboard and Reporting

All Single Jurisdiction Validations Displayed in Dashboard, Reports, and Downloaded Validation Metrics (E, V, A, S)
All validation results will now be displayed on the dashboard, available for download as validation metrics, and included in the custom validation report. If a validation has never been executed or lacks data for a specific check, it will show as “N/A.” If validations have been executed but resulted in zero anomalies, this will still be indicated as zero values. VEP currently has 131 single jurisdiction validations, all of which will be displayed.

Validations Grouped by Feature Class in the Downloaded Validation Results (E, V, A, S)

After completing a validation run, the exported results in the Excel table are organized by feature class.

Validations with 100% Marked Exceptions Displayed in Dashboard and Reporting (E, V, A, S)

When specific validations are marked with 100% exceptions, they will still be displayed in the dashboard, downloaded validation results, and validation custom report.
 

Single Entry Aggregator

All Uploads and Validation Runs Visible to Admins (S)

Single Entry Aggregator Admin users, will now have visibility into every upload and validation run in the system.

Jurisdiction Information Added to Uploads (S)

The jurisdiction chosen will be displayed in the upload table for Single Entry Aggregator users when a file is uploaded. Admins will now have visibility into which uploads occurred for specific jurisdictions.

Jurisdiction Information Added to Validations (S)

When a validation is run, the selected jurisdiction(s) will be displayed on the validation results page for Single Entry Aggregator users. Admins will now have visibility into validations that occurred for specific jurisdictions.

Jurisdiction Information Added to the CAMA Table (S)

A jurisdiction name field has been added to the CAMA table for Single Entry Aggregator users using parcel data. This field is now populated in the web map and the downloaded data.

Dashboard Optimization and Updates to Display All or Multiple Jurisdictions (S)

The dashboard for Single Entry Aggregator users who wish to display combined data across all jurisdictions has been enhanced.
 

Aggregations

Updates to Collaboration Portal Pages (E, V A)

Improvements have been made to the Data Aggregator user interface to enhance usability and make it easier to locate both executed and scheduled data ready to be aggregated. A new tab has been added for scheduled data aggregation flags, and the text throughout the page has been revised for better clarity.

Edit Scheduled Data Aggregations and Ready for Aggregation Scheduling (E, V, A)

Multi-jurisdictional collaborators can edit the occurrences of when their data is scheduled to be ready for aggregation. Additionally, Aggregators and Regional Aggregators can edit their scheduled or recurring data aggregations.

Text and Pop-Up Updates

Text and Pop-Up Updates Throughout VEP (E, V, A, S)

To enhance user experience and clarity, we have updated texts and pop-ups throughout VEP. Additionally, many pop-ups have been eliminated to decrease the clicks required to complete workflows.

External NGUID Configuration

Use Different Types of External NGUIDS in VEP (E, V, S)

VEP can now accept various types of external GUIDs. Previously, it only supported integer values saved as strings. Now, VEP can handle GUIDs, global IDs, text characters, integers, or a combination of these types of values. External GUIDs are unique to each record in VEP and are essential for tracking your data.

If you would like to reconfigure your external GUID values for one or more layers or have additional questions about this new functionality, please submit a ticket to the Support Center or contact your Client Success Manager.

Automated Uploads (Premium Feature)

Automated Uploads for Data Coming from a Versioned SDE (E, V, S)

Users uploading data from a versioned SDE will not encounter issues from open edit sessions or versioning conflicts.

Please navigate to the Automated Upload Tool's website to download the latest version of the tool. 

Parcel Validations (Premium Features)

Parcel Has Matching Geometry Validation Added (E, V, S)

A new validation feature has been added to parcel validations (premium feature). This check (PAR-3E) identifies parcels in each dataset with the same geometry.

Improvements to the Parcel Gap and Overlap Validations (E, V, S)

Logic improvements have been made to the checks for parcel overlaps and gaps. All overlaps and gaps will now be flagged, even if they occur in rights-of-way or bodies of water.

Updated Validation Name for CAMA and Parcel ID Mismatch (E, V, S)

The validation check for CAMA records without an associated Parcel record has been renamed “CAMA and Parcel ID Mismatch,” it is now associated with PAR-1B.

Validations

Speed Optimizations for All Validations (E, V, A, S)

All VEP validations have been optimized, significantly reducing the time required to run validations and receive anomalies.

Incorporated Municipality is Null Checks Removed from Address Point and Road Centerline Validations (E, V, S)

The null check has been removed from the address point (VAL80-04) and the road centerline incorporated municipality attribute checks (VAL81-05 and VAL81-06). While these validation checks will still identify blank or empty records, they will no longer flag cases where the incorporated municipality fields are null.

RCL Digitized Direction Logic Enhancements (E, V, S)

Enhancements have been made to the validation logic for VAL12-1, specifically for the road centerline directionality that does not match the corresponding order of the address points. If a road centerline has only one address point or only one address point on each side of the segment, this will no longer be flagged. Overall, the logic for this check has been enhanced to improve both consistency and accuracy.

Bug Fixes

Reorder Fields in the Layer Configuration Module (E)
 When a field order is changed in the display, this page no longer jumps to the top immediately. 

Page Arrows Working in the Manage Schema Module (E, V, S)
 The Manage Schema Module's page arrow functionality allows you to navigate to the next page of saved schemas.

Exceptions Removed When Anomalies are Resolved (E, V, A, S)
If all anomalies for a given validation are resolved, marked exceptions will be removed from the validation report, results, and dashboard.

Unmarked Exceptions Persist After Upload and Validation Run (E, V, A, S)
Exceptions that are unmarked and uploaded into VEP will continue to maintain their unmarked status after subsequent validation runs.

Blank Validation Fields Created from Manage Anomalies Page (E, V, A, S)
When anomalies are unmarked on the Manage Anomalies Page, the markup records will keep null values in the status, justification, and comments fields instead of having blank values inserted into those fields.

Dashboard Historical Anomaly Charts Displaying Accurate Results Over Time (E, V, A, S)

Clicking the red and green arrows on the dashboard will show accurate counts of anomalies over time, depending on the selected time period