If this code is being run in FileXmlTransLaboIn, you can get the name of the config item from %Ensemble("ConfigName") and then query based on that.

set configName=%Ensemble("ConfigName")
&sql(SELECT Category INTO :itemCat FROM Ens_Config.Item WHERE Name=:configName)

Your code looks good and works for me. Are you having troubles with it or what are you looking to add next?

Yep, RawContent is potentially truncated and isn't meant for accessing the full message.

You can use the OutputTo* methods to get the whole message. OutputToLibraryStream is going to be the best option because a stream object can be of unlimited size. OutputToString will work, but only for messages that are smaller than the maximum string size (around 3 megabytes, assuming you have long strings enabled in the Caché config. If not, then 32k).

This query will list changes to layouts:

SELECT UserDR->SSUSR_Initials,AuditDate, AuditTime, ReferencedClass FROM websys.log WHERE sourcetype='LAYOUT' AND type='Update'

This works in HealthShare 2021.1 -- it may also work in older versions but I haven't tested.

You can view the source for %syPidtab.inc in the System Management Portal using System Explorer >> Routines or by opening it in Studio.

You can use the %Dictionary classes to get details of the class and methods:

USER>do $System.SQL.Shell()
SQL Command Line Shell
----------------------------------------------------
 
The command prefix is currently set to: <<nothing>>.
Enter <command>, 'q' to quit, '?' for help.
[SQL]USER>>SELECT FormalSpec FROM %Dictionary.MethodDefinition WHERE parent='My.Test.Class' AND Name='TestMethod'
1.      SELECT FormalSpec FROM %Dictionary.MethodDefinition WHERE parent='My.Test.Class' AND Name='TestMethod'
 
FormalSpec
param1:%String,param2:%Numeric
 
1 Rows(s) Affected
statement prepare time(s)/globals/cmds/disk: 0.0033s/321/1482/0ms
          execute time(s)/globals/cmds/disk: 0.0006s/3/385/0ms
                          cached query class: %sqlcq.USER.cls14
---------------------------------------------------------------------------
[SQL]USER>>

Create a BS that sends messages to BO every X seconds - it makes production more complex and also queues might not guarantee that the method is executed on schedule.

You could try submitting the message to the head of the queue to be sure it gets processed right away.

I'll be interested to see others' thoughts on this as well, but one approach is:

• Create a new empty database for the globals
• Use GBLOCKCOPY or MERGE to copy each of the globals from the current DB to the new globals DB. I believe GBLOCKCOPY is faster than MERGE.
• After they are copied/merged to the new DB kill the globals in the currrent DB. This then becomes your routines DB.

Or you can do the opposite and export all of your routines from the current DB, import them into a new routines DB, then delete them from the current DB which becomes your globals DB. This would be faster than the first approach unless your globals are really small.

%System.OBJ.Load() imports and compiles classes and can be run from another routine or class.

You've written a pretty good description of the Production Generator included in IRIS for Health:
https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI...

This presentation may be of interest:
https://learning.intersystems.com/course/view.php?id=1192