I want to highlight the fact that the account expiration was several months long (so the connection being up for many months with no reconnecting) resulted in the account expiring.
The other question (besides workarounds) is whether this is expected / desired behavior at the product level, or perhaps the account inactivity logic should take into account ongoing activity?
Another option (my preferred one) - ensure that source control is used for all namespaces in your instance and simply do the search in your source repository. Then you not only find the strings you are looking for but also you can easily find the history related to each of those parts of code.
thank you for making us aware. I have escalated this internally and I hope it can be corrected quickly.
We are using this to implement a reusable comprehensive email templating module to prevent our having to hand-craft HTML emails out of many different IRIS applications. So far the approach looks very promising! (and members of the community will eventually be able to directly see the results as we're first using this to implement a Welcome Email framework which can be used by any of our externally facing applications which use InterSystems Login accounts - https://community.intersystems.com/post/leveraging-your-intersystems-lo…)
My pleasure @Dean Andrews - I couldn't do any of it were it not for the awesome team you have supporting the D.C. :)
@Evgeny Shvarov - I feel the same way about you and your contribution! It's great striving together to make this place better for everyone learning our technologies :)
Umm ... that sounds a little scary, but thanks all the same ;)
thanks Raj!
Thank you - I agree it was great to connect at GS :)
much appreciated @Muhammad Waseem - it's a real pleasure :)
Thank you @Robert Cemper! Working with you on the Hermes application was a great joy to me as well, and I am very thankful that we have been able to stay in touch via the D.C. after your retirement :) I continue to learn from your deep technical expertise!!
@John Murray - thank you for the great investment that you and George James makes into tooling for our community! I am always very impressed with what you come up with :)
thank you for taking the time to write all of this out :)
very clear answer - thank you @Pravin Barton!
Calling @Stefan Wittmann, @Timothy Leavitt and @Pravin Barton
If you can move to isc.rest, I know it takes care of OpenAPI (aka Swagger) spec generation automatically.
I second this - using Do LOG^%ETN is very useful for grabbing the full stack and in memory values for later debugging ... this is where I usually start
@Evgeny Shvarov - I recommend you start a new thread with these questions
great summary, thanks Tim!!
I think that is a really good idea. IPM should definitely play a role in the future with %Zen
very well articulated! there was absolutely some great Rapid Application Development value inherit in Zen which is hard to replicate with a 3rd party library providing UI to an IRIS backend
nice summary Dan - thank you!
@Benjamin De Boe - thank you for weighing in!
if the folder includes files referenced by the running instance (xslt or js) then it's absence would have an impact on those functions which try to use the files at runtime
Yes - this will work in that case above case (see my example which preserves all of them in the middle)
If you know that it begins and ends with CRLF then it is as simple as:
USER>Set string = "[line feed](carriage return) str [line feed](carriage return) ing [line feed](carriage return)" USER>Write $piece(string,"[line feed](carriage return)",2,*-1) str [line feed](carriage return) ing
Could you please provide an example with screenshots?
Could you please describe the situations where it does something "bad" or where you see things as not working correctly?
We use nightly IRIS backups which are moved to a network share, so Test can restore the backups to an alternate application data DB via a script. We always have 2 application DBs defined, so we can script a restore on a weekly basis so the data is readily available if a developer needs it - they simply swap from the active data DB to the alternate (the alternate is always the target of the automated restore so as not to interrupt any data depending testing which may be actively going on at the time of restore).
We have found this to be very effective for our needs for multiple internal applications.
Thank you for all of your hard work!!
I recommend reaching out to the WRC to help you dig into this specific error.