Bug 1020955

Summary: [guided rule editor] date options defaults not in source
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: manstis
Status: CLOSED CURRENTRELEASE QA Contact: Zuzana Krejčová <zkrejcov>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: lpetrovi
Target Milestone: ER5   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:15:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Zuzana Krejčová 2013-10-18 15:18:46 UTC 
Description of problem:
If you and a date-effective/-expires to a guided rule, it is pre-set with a default date. This date doesn't show up in the source until you click the dates input field or switch it to another date.

If you try to validate such rule, you get no validation results and after you save, you get 
ERROR [org.guvnor.common.services.builder.BuildChangeListener] Invalid date input format: [] it should follow: [dd-MMM-yyyy]: org.guvnor.common.services.shared.exceptions.GenericPortableException: Invalid date input format: [] it should follow: [dd-MMM-yyyy]
	...
in the server log. Rule is still saved successfully according to notification.


Version-Release number of selected component (if applicable):
BPMS 6.0 ER4


Steps to Reproduce:
1. Add a date-effective attribute to a guided rule.
2. Without changing the default date, switch to source.
3. Try to validate the rule.
4. Save the rule and look into the server log.
Comment 2 Zuzana Krejčová 2013-12-09 10:10:50 UTC 
Verified on ER5.