Hide Forgot
securitylevel_name: Public Open a blank package, switch to Advanced view and declare a simple fact: declare Fact field1: String field2: String end When you try to switch back to Basic view, you get a message "There are errors in this view. Can not switch to guided mode until the errors are resolved" which doesn't exactly describe the problem ,if there's any (I don't think so). However, the declared fact is imported to the fact model of the package and can be used to build rules in Guided editor.
Attachment: Added: PackageConfigError.png
Link: Added: This issue depends GUVNOR-1095
You are really only supposed to be able to declare imports and globals in the advanced view. Currently you can also declare facts, rules, functions which is not supposed to :) The fact that you created actually is declared and visible, but the code shows the error window which is not descriptive at all. Added more descriptive error messages that tell users that they should not be declaring functions/rules/declared types here but should use the corresponding guided editor features for it.
Done, more appropriate error messages are now shown to user.
Now I understand it is deprecated declaring facts through the Advanced view. The error message looks OK. But, now it *is* possible to switch back to Basic view (even if there is a fact declared in the Advanced view). Hitting 'Save and validate configuration' instead of 'Basic view' button will do the task. Please include removing this inconsistency to resolve the issue.
This is not a blocker for BRMS 5.1.0, moving to future.
Jiri, I thought that was the plan just to warn users that they should not declare facts/rules/etc in that view and should use the appropriate guided editor features. From the description it was not clear what was requested to implement, but I believe a warning is better than a hard "no" because of users who may already be doing this and depend on it in their packages.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Will document in release notes as a known issue, or resolved issue depending on resolution.
Tiho, I agree with your explanation. The alert messages do describe the problem well now. I think there is noting more to be done on this issue.
Deleted Technical Notes Contents. Old Contents: Will document in release notes as a known issue, or resolved issue depending on resolution.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When using the advanced view of the BRMS web user interface if the user declares a Fact and attempts to switch back to the basic view, the following error message was displayed, "There are errors in this view. Can not switch to guided mode until the errors are resolved". The error message has been updated to provide more information and now reads, "Defining declared types in this view is not allowed. Please remove all declared types from the view."
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -When using the advanced view of the BRMS web user interface if the user declares a Fact and attempts to switch back to the basic view, the following error message was displayed, "There are errors in this view. Can not switch to guided mode until the errors are resolved". The error message has been updated to provide more information and now reads, "Defining declared types in this view is not allowed. Please remove all declared types from the view."+When using the advanced view of the BRMS web user interface if the user declared a fact and attempted to switch back to the basic view, the following error message was displayed, "There are errors in this view. Can not switch to guided mode until the errors are resolved". The error message has been updated to provide more information and now reads, "Defining declared types in this view is not allowed. Please remove all declared types from the view."
I removed the needs release note flag as this was documented as a resolved issue in the 5.2 release notes.