go to post Mark OReilly · Aug 27, 2024 Closing- this went to a WRC- even making a helper class wouldn't make it work like we would expect it to work. There is a JIRA for message bank to be improved- as realisitally is should be more like a standard Async member where you could have a different message purging cycle on it i.e. maintain on it for 1 year while only 30 days on main ect.
go to post 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.
go to post Mark OReilly · May 18, 2023 set streamContainer=..CreatePythonPDFStream() set streamContainer.OriginalFilename="test2.pdf" issue did not happen whenever finished this with python (more complex) and it coming from a classmethod so unsure what the problem was
go to post Mark OReilly · May 12, 2023 DBs not required. could either be removed or just made non read only
go to post Mark OReilly · Jul 27, 2022 Solved by WRC. By pressing enter first on the Search bar then this issue disappeared. Issue presumed browser Caching issue
