Bug 1179057
Summary: | Some of UserTask attributs require an input validation for checking max length | ||
---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Hisao Furuichi <hfuruich> |
Component: | Eclipse Tooling | Assignee: | Kris Verlaenen <kverlaen> |
Status: | CLOSED EOL | QA Contact: | Jozef Marko <jomarko> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0.3 | CC: | ksuzumur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-27 20:02:41 UTC | Type: | Feature Request |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Hisao Furuichi
2015-01-06 04:48:47 UTC
Isn't this a database configuration issue? What happens if/when the underlying database implementation is changed? Does the jbpm plugin need to be changed again? Added a User Preference that allows the user to set a limit on the length of text fields. This defaults to 255. Fixed with Luna build 1.1.1.201501262023 User Preference added to Window->Preferences->BPMN2->Editor->Behavior Verified on BPMN2 Modeler 1.1.1.201501282123 Not included in jbds-8.0.2.GA_jbdsis-8.0.0.CR2 Test concerning this issue: https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/master/tests/org.jboss.tools.bpmn2.ui.bot.test/src/org/jboss/tools/bpmn2/ui/bot/complex/test/testcase/ComplexSpecialCharactersAndLenghtsTest.java Verified on jbds-8.1.0.CR1_jbdsis-8.0.1.CR1 - BPMN2 Modeler 1.1.2.Final |