[
https://issues.jboss.org/browse/DROOLS-3482?page=com.atlassian.jira.plugi...
]
Stetson Robinson commented on DROOLS-3482:
------------------------------------------
[~tirelli], [~uxdlc], I see. Would we cover our bases better if we said *Included DMN
artifacts* or *Included artifacts*?
* Tab and page header: *Included DMN artifacts* / *Included artifacts*
* Description: *Included DMN artifacts are externally defined DMN models or other
DMN-related artifacts that have been added to this DMN file so that its decision
requirements diagram or graph components are available to this DMN file.*
Still not in love with the description wording, but would that general idea work? Would
*assets* be better than *artifacts*? I hesitate to say "assets" because
that's what we use in the general project import screen.
Terminology for DMN import
--------------------------
Key: DROOLS-3482
URL:
https://issues.jboss.org/browse/DROOLS-3482
Project: Drools
Issue Type: Task
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Stetson Robinson
Priority: Minor
Labels: drools-tools
Define best term to use for importing a DMN file, from the project directory. Importing a
.dmn file will include file nodes, data types, etc. The term will be used for a tab label,
button labels, and the like.
UX mockups currently use "import" but other terms such as "include"
have been discussed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)