LEAF PWS Attachment A - Backlog Examples.docx

Attachment A - LEAF Backlog Examples

Digital 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.

· The export interface will need to be augmented to:

· Intake the DB/username/password for the destination database

· The password must never be displayed on screen, and must not be retrievable via any API.

· Provide an option that signifies whether automatic nightly exports are enabled.

· Show when the last export was completed

LEAF Connect Tool – Minor Enhancement (LEAF-5950)

· As a LEAF team member or coach with appropriate access: I want to input a user and retrieve all LEAF sites they are associated with (either through records, group membership, or active directory information), And see the primary admins for each of those sites, So that I can quickly identify local contacts and support connections for that user.

· User Input: A field to input or select a user (e.g., by name, email, or ID).

· Site Association Logic: The tool identifies all LEAF sites where the user: Has records, or Is a member of a group tied to the site.

· Fallback Logic: If no records or group associations are found, the tool uses Active Directory information (e.g., office location, department) to suggest likely LEAF site affiliations.

· Primary Admin Retrieval: For each associated or inferred site, the tool displays the primary admin(s) with name and contact info.

· Testable Output: Results are presented in a clear, testable format for validation before integration.

· Post-Testing: After successful testing, determine the best location for integrating this tool.

Inbox: Reduce Spacing Above On Hold Section – Minor Enhancement (LEAF-6408)

· As a user, I noticed the "On Hold" section is placed far down the page, separated from my Inbox by a large gap of empty space (caused by the "No more items in your inbox. Have a good day!" message sitting between them). Because of this, I almost missed that the On Hold section existed, and didn't realize that records placed On Hold no longer show up in my normal Inbox.

Mass Actions: Suppress Email notifications for submit and restore (LEAF-6342)

· As a LEAF user I want the ability to turn off email notifications for submit and restore so that I can limit unnecessary notification

De-prioritize list of LEAF team members in the User Access Group (LEAF-4774)

· As an admin, I want to view my admin list in a way that prioritizes my local administrators, instead of interleaving LEAF team members in the list.