[
https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi...
]
Stetson Robinson edited comment on DROOLS-3452 at 1/31/19 12:29 PM:
--------------------------------------------------------------------
If that's the DMN syntax requirement, then I guess we need to keep it. If it's not
and it's up to us, then definitely natural language, in the format "31 Jan 2019,
14:00:00+02:00:00" or whatever. If having spaces and punctuation is a problem, then
the compromised style recommendation is "31Jan2019T14:00:00+02:00:00", assuming
seconds are used.
was (Author: stetson.robinson):
If that's the DMN syntax requirement, then I guess we need to keep it. If it's not
and it's up to us, then definitely natural language, in the format "31 Jan 2019,
14:00:00+02:00:00" or whatever. If having spaces and punctuation is a problem, then
the style recommendation is "31Jan2019T14:00:00+02:00:00", assuming seconds are
used.
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
Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen
Shot 2019-01-15 at 11.49.58 AM.png, enumeration-question.png, enumerationB.png,
revised-range2.png
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)