Business Rule Editor Changes
Have a question about the new Rule Editor within 2024.1... How are you able to edit the Target, it shows greyed out and when I click on the field it does not allow me to edit the field.
.png)
I would like to understand before I give my team a presentation tomorrow about if we should upgrade or not. Thanks
Comments
We recently upgraded our environment to 2023.1 which included the new rule editor ui. We immediately disabled the new ui to revert to the version that our team was comfortable with.
https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.U…
Yeah, I think I am going to lean that way too, there is something security wise that is preventing me from editing the Target, but the documentation doesn't share any details about what it could be.
I left
.png)
per what the document says. I tried CompileAllNamespaces() and different options but still it is inconsistent on if I can edit it or not.
That part I am not sure of. I installed 2024.1 on my local computer and ran into the same issue with not being able to change the target. I have %ALL access so I wouldn't think it would be a permissions problem. I briefly demoed it to our developers. Everyone liked the old version better. I turned it off and haven't looked back.
Yup, same here. I have %ALL access, and still not being able to modify the Target of SEND. I tried all different options that I could think of changing in the Web Applications, but no luck. I opened a ticket with WRC.
While I like the IF, THEN look and it is better than WHEN.. if I have to disable for now, I will leave that up to the team tomorrow.
And here is the code if you are using a Installer manifest 😉 Helps us while working with containers.
...
Class HBT.Util.WebApp
{
ClassMethod DisableNewRuleEditor() As%Status
{
#Dim tSC As%Status#Dim tSE As%Exception.StatusExceptionTry {
Zn"%SYS"
&SQL(UPDATE Security.Applications SET Enabled = 0WHEREID = '/ui/interop/rule-editor')
Set tSC = $$$OK
} Catch tSE {
Set tSC = tSE.AsStatus()
Quit
}
Quit tSC
}
}💡 This question is considered a Key Question. More details here.
Other issues that we have noticed are..
- Textual Search through Ctrl-F (Browser) no longer works.
- Search within Rule Editor does not highlight or take you to the code you are searching for.
- It is very difficult to Add any Rules, Expressions, Code, etc.. within the Application
- In Expression boxes, can’t copy/paste from other rules.
- In Send Command, it is very difficult to add the target.
- Not allowed to type, paste, and type ahead search does not work.
- Even highlighting the Target with your mouse does not automatically add it to the Target.
- Its automatically putting a “,” before the Target, even if you click the check box next to the Target.
- Can’t type ahead or paste translation within Translation Expression. You must scroll through the entire list; we have a lot of translations we have to now search through.
I have sent this feedback to InterSystems.
We just took an upgrade (to 2023.1.4) and are assembling our own issues with the Business Rule Editor to report to Intersystems before we revert back to the old version.
Some problems we have found so far in addition to what Scott has already reported:
- Another wrinkle with the "send" action: You cannot edit it manually. This is a problem when the GUI forces you to make choices that are incorrect for your logic - such as its forced ordering of "chained" transform names (multiple DTLs in one "send") in alphabetical order rather than the order they actually need to be in.
- Constraints are also no longer manually editable, which is inconvenient when you have a long list of message types (e.g. ADTs).
- Rules are no longer numbered, and there is a lot more whitespace. This, with the added problem of the commands appearing at the bottom (and Scott's already reported issue with not being able to Ctrl+F) makes it difficult to analyze, navigate and program the rule.
- Autocompletion of the HL7 fields no longer works. --> HL7.{
- There is no longer a "Save As" button . You can accomplish this by using Edit, but it's obfuscated.
- There is longer a "search" box in the "Open" dialog, forcing you to click through all the package levels. Additionally, there are no longer alternate (more efficient) "view" options.
- Pop-ups are no longer resizable
- Breadcrumbs (back to Interoperability etc) are no longer available at the top of the page.
- The URL still at times reflects a different namespace/rule than is shown on the page. It's thus difficult to be certain one is saving the rule in the expected location. (i.e. It seems it doesn't update the URL for the current component, if you have changed component from within the editor using the open/new buttons.)
.png)
Thanks for adding to the ongoing list. Make sure you open a WRC ticket to make InterSystems aware of the likes/dislikes..
We will, thanks Scott!
Could use a compact view. There is no disabled shading. Disabled shading was super helpful to quickly know which rules are enabled/disabled.
Good one!!!
it's interesting and very nice
Scott.. Can you confirm the 'issue free' version of IRIS that you previously on? I recently installed IRIS 2024.1 to my PC, just for the purpose of learning BPL/DTL, so, I wouldn't know a system flaw it if it bit me. Thanks
We are on HealthShare Health Connect 2024.1, no the free version.
Thank you Scott, but, I am inquiring about what version you were on prior to 2024.1 (aka. that was 'free' of issues).
2022.1.4
Perfect.. Thank you Scott!