Hide Forgot
Guided Rule Editor, after adding a consequence that uses DSL enum values, they dissapear after save. Only way to fix is to delete the DSL and recreate it in order for them to show back up.
Although annoying, I will nack this for 6.0.0 and propose it for 6.0.1, given that there is a work around. If we have time, we will of course fix it for 6.0.0 and change the nack->ack. If you think this must be fixed for 6.0.0, please ping us and we will re-consider.
Toni.. another one :( When writing the unit test could you please also try an enum in the Condition? I suspect this is something that could be common across both Conditions and Actions (and not even necessarily specific to DSLs).
I created the following DSL:- [then]Set applicants credit rating to {rating:ENUM:Applicant.creditRating} = applicant.setCreditRating("{rating}"); This correctly showed an enumeration drop-down in the RHS of the rule. I selected a value in the guided rule, saved it, closed the editor and re-opened. It was correctly re-opened and the RHS enumeration could still be edited. It is possible this has been fixed under another BZ relating to issues re-opening guided rules. Setting to MODIFIED for QE testing to confirm this is no longer an issue.
This does happen on Condition side of the DSL as well in 6.0.0GA. See attached screenshot for an example - corrsponding DSL [conditions] are: [condition] If there is a Holding = $holding : Holding( ) [condition] and the Country of Exchange is "{countryOfExchange:ENUM:holding.countryOfExchange}" = ... [condition] and the Capital threshold is greater than "{capitalThreshold} %" = ...
Created attachment 866162 [details] DSL losing editability after save screenshot
Created attachment 875590 [details] Holding DSL I have reproduced exactly as the screenshot illustrates with this DSL on 6.0.0.GA. This is in fact the same issue as bug 1067923.
> This is in fact the same issue as bug 1067923. I mean comment #6 is duplicate of 1067923.
Consequences input fields are now editable after reopen, too.