Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Feature Story Description:
| Anchor | ||||
|---|---|---|---|---|
|
As an Admin I want to be able to assign the validation rules that are created to various users.
Define all the frontend backend validation rules that will be used.
The end-user only sees the result but they doesn’t see the validation rule.
i.e. check the facility address against DSR.
Business Rationale:
Client-side validation helps ensure the data that is submitted matches the requirements set forth in the various form controls (i.e., required fields, required formats, etc.). This is an important piece of user-friendly design/good user experience.The ability to assign these
Some data points require validation that can be too complex to build into CHEFS or might require validation against external systems (e.g. PHN check)
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
11 | Parent | |
2 | ||
3 |
|
|
4 |
|
|
Technical Details:
OOTB.
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
Prototype/Mockups
Provide high fidelity prototype or mockup
Out of Scope:
Contact(s):
Table of Contents
| Table of Contents |
|---|