[
https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi...
]
Liz Clayton edited comment on DROOLS-3452 at 1/15/19 11:12 AM:
---------------------------------------------------------------
Note, per [~tirelli]: We must support timezones, but they are optional for date times and
explicitly defined. The editor must persist the date/time, if using timezone, exactly as
it was typed in/selected by the user. No conversions allowed.
was (Author: uxdlc):
Note: We must support timezones, but they are optional for date times and explicitly
defined. The editor must persist the date/time, if using timezone, exactly as it was typed
in/selected by the user. No conversions allowed.
Data type constraints: Date/Time
--------------------------------
Key: DROOLS-3452
URL:
https://issues.jboss.org/browse/DROOLS-3452
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 define data type restrictions (one-off
instances) from a decision table .
* From the Data Types tab - as a user I want the ability to define constraints for the
following types: Date (Expression, Enumeration, and Range.)
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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)