LEAF Performance Work Statement Attachment A - Backlog Examples

Attachment A - LEAF Backlog ExamplesDigital Signature Implementation (LEAF-3613) – Major Enhancement Integrate digital signature signing and validation, requiring a VA Personal Identity Verification (PIV) Card to provide cryptographically secure signatures associated with LEAF Workflow Actions Workflow Editor v2 – Major Enhancement
Analyze customer pain points and friction within the existing editor to implement a revised version, incorporating modern Human Centered Design patterns and alignment with Section 508 requirements Access via Public Networks – Major Enhancement
Provide secure access to LEAF sites via Public Internet endpoints ServiceNow Integration – Moderate Enhancement (LEAF-5967) Create a LEAF Agent Instruction that enables automatic creation of ServiceNow Incidents and Tasks. Example instruction implementation: https://github.com/department-of-veterans-affairs/LEAF/blob/master/pkg/agent/payloadHoldForDuration.go MSSQL Export Part 1 – Moderate Enhancement (LEAF-4292)
This will provide Portal Admins a method to export their data into a SQL file compatible with MSSQL. The generated file must only be downloadable by Portal Admins. The Portal Admin should be able to navigate to Admin Panel -> Toolbox -> MSSQL Export, where they can see: Button: Generate SQL file
Link to previously generated SQL file
The exported schema should be simplified to make it easier for people to write queries. Use MSSQL conventions where possible. Export minimum two tables: record
Columns should include (from records): recordID, date, serviceID, userID, title, priority, lastStatus, submitted, deleted Active indicators that include a short label must also be made available as columns, replacing spaces with underscores. Duplicate names should include the indicatorID at the end of the name. Example: Total_Cost_12345 history
Columns should include (from action_history + workflow_steps): actionID, recordID, userID, stepID, stepName, actionType, time, comment grid_{fieldName} (each grid input format field should have a separate table. Duplicate names should include the indicator at the end of the name as in #1.2) Columns should include: recordID, and all columns in the grid Columns that include a UNIX timestamp should be transformed into the standard MSSQL date type (or whichever type is most common). MSSQL Export Part 2 – Moderate Enhancement (LEAF-4293)
This provides a mechanism to automatically write exports on a nightly basis from LEAF-4292 to a MSSQL database that the admin identifies.