Red Hat Bugzilla – Bug 1020955
[guided rule editor] date options defaults not in source
Last modified: 2016-07-31 21:08:35 EDT
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.
Verified on ER5.