AllAccepted answers
Mark OReilly · Jul 10, 2024

Hi Josh:

It's interesting you find it is an intermittent issue. We had some very large rules and when we turned on the new rule editor no matter what would get an :( face. 

If we deleted a few rules up to a certain amount this would load up correctly. 

If you look in your devtools when this happens it is a timeout issue where the connection is being closed prior to the rule having loaded. 

With asking WRC and pointing out the issue the :( issue was replicated in 2023.1 but did not happen in 2024.x. 

What I think it is is the gateway timeout time is too small and if you update the timeout to a bit longer it might allow the web application to load. 

Alternatively go to web application /ui/interop/rule-editor and disable the application to go back to the old rule editor. This issue and No crtl+f find functionality has caused many people to divert from the new editor until it is optimised, as well as i believe in 2023 too much whitespace. 

Mark OReilly · Feb 20, 2024

Thanks:

Over the weekend a viable solution has been found for this. A decision was made that actually the code being ran was probably too complex to be a computed field. This code was originally written in a Business process. The solution was to amend the custom method of the process and call a classmethod for this which could be run in a dtl or when setting up the class. 

The scenario was we had a property that is a long string of all the other values 

Decided best just to add to any DTL 

I would prefer it generating the function when the dtl is complete ect in the class without having to call it externally but i doubt it is actually possible

Mark OReilly · Feb 17, 2024

To clarify my question this is the library property helper class Library property helper when you look at the documentation for computed from documentation here Computed documentation

ClassMethod FullNameComputation(cols As %Library.PropertyHelper) As %String
{
    return cols.getfield("FirstName")_" "_cols.getfield("LastName")
}
// ...

But you can't seem to throw a parameter i.e.par= "Firstname" cols.getfield(par) in the code without it throwing errors

Mark OReilly · Jan 10, 2024

Hi: 

We agree we loaded up the page and Ctrl + F did not work in Google Chrome on Windows. Due to this really as a key workflow we are having to revert back to the old viewer. 

Mixed views on the new layout, some people are big fans that it is more separated out and with it saying "if and then" rather than when and an action that wasn't as clearly broken up. 

There is too much whitespace around the if and then boxes i would say. The rule box fits very neatly  but especially if you have an if expression 1 and only a simple send with a transform the boxes are just a little big with whitespace. 

One thing we discussed was the rule numbers. When you do a "test" or the rule logging it will at first return a rule number effected still but rule numbers are not on the rule editor. I understand i think the rationale as developers rule numbers themselves change so for internal development reference in notes they shouldn't be used but think in terms of UI the rule numbers should probably be included. 

How do you generally go about requesting bug fixes or just general improvements? In category on the production monitor a lower case a going below something starting with an upper case Z is still mildy frustating

Mark OReilly · Sep 13, 2023

Hi i'm not sure i understand what you are trying to achieve. Your current state of the mirror is Caught up in terms of journal restore. This means in the current environment your journals are currently up to date with the Primary server as per the documentation. What/Why are you trying to restore a journal as from the mirror monitoring and you are in a mirrored environment it does not look like you need to Journal restore at the moment?

Mark OReilly · Jul 21, 2023

In addition to Luis's documentation i would look here. 

Ensemble Orphaned Messages | InterSystems Developer Community | Best

Again following the other answers it will be for you to determine if the growth of your .dat file is as expected. Have a think if you should be keeping a full time history logs of all your data. 

From your post it does sound like you just aren't getting rid of the transactional data and if you have most things set up correctly and no funny %save operations on your code or embedded xml object messages within messages then if you just start a task to start getting rid of any transactional data over x amount of days you should be fine, NOTE though if you are mirroring be careful setting to short a number of days ago, i.e. if youve had the system 3 months and you decide to keep only 1 month this may be a huge amount of data to delete which would hit your journal files hard and potentially fill it up, try perhaps configure so you only delete 1 days worth of data first (or a week ect) at first and then gradually reduce that number down to your agreed retention period.