[
https://issues.jboss.org/browse/DROOLS-3481?page=com.atlassian.jira.plugi...
]
Liz Clayton updated DROOLS-3481:
--------------------------------
Description:
Background
Persona: Business analyst or Rules practitioner
Use Cases:
* From the DMN canvas view:
As a user, I want to be able to set data type constraints for an input value in a Decision
Table, so that this constraint is valid _*only*_ in the context of this specific input in
this Decision Table.
* Provide options for:
- one-off constraints
- apply constraints to data type.
- possibly "yoke" constraints to data type.
Functional considerations/ pre conditions:
* Consider interaction in light of Property panel and consistency.
* Underscore the notion of one-off constraints.
* Maintain "Manage" link.
Verification conditions:
* Scrum team and PO review.
was:
Background
Persona: Business analyst or Rules practitioner
Use Cases:
* From the DMN canvas view:
As a user, I want to be able to set data type constraints for an input value in a Decision
Table, so that this constraint is valid _*only*_ in the context of this specific input in
this Decision Table.
* From the Data Types tab:
As a user I want the ability to define constraints for data type definitions in use within
the DMN file.
Functional considerations/ pre conditions:
* Consider interaction in light of Property panel and consistency.
* Underscore the notion of one-off constraints.
Verification conditions:
* Scrum team and PO review.
Data type constraints: DMN canvas view workflow
-----------------------------------------------
Key: DROOLS-3481
URL:
https://issues.jboss.org/browse/DROOLS-3481
Project: Drools
Issue Type: Story
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Liz Clayton
Priority: Major
Labels: UX, UXTeam, drools-tools
Background
Persona: Business analyst or Rules practitioner
Use Cases:
* From the DMN canvas view:
As a user, I want to be able to set data type constraints for an input value in a
Decision Table, so that this constraint is valid _*only*_ in the context of this specific
input in this Decision Table.
* Provide options for:
- one-off constraints
- apply constraints to data type.
- possibly "yoke" constraints to data type.
Functional considerations/ pre conditions:
* Consider interaction in light of Property panel and consistency.
* Underscore the notion of one-off constraints.
* Maintain "Manage" link.
Verification conditions:
* Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)