Echoing Chad's comments and adding screen shot of the "button somewhere in the new rules editor for switching back to the old one" :

Take a look at the WorkQueue Manager which also allows for coordination. 

workQueue =iris.cls("%SYSTEM.WorkMgr")._New()

status = workQueue.Queue("..PythonClassMethodToBeJobbed")

[Note routines require function [parentheses] not just a plain label - so for Alex's example below will need Test()]

Hope resolved by now but : One needs to double the quotes within the pattern since it needs to be a single string:

Matches(tAlias, "1(.E1""SITE A"",.E1""SITE B"")")

Matches(tAlias, "1(.E1""SITE A"",.E1""SITE B"")")

James

Hi Murillo

While no UI exists to create a deployment file to specify host items to remove it is possible to use the APIs to create such a deployment file  - see the last example in the top section of the class documentation for Ens.Deployment.Utils. This is the same removal mechanism used when creating the rollback mechanism.

HTH

James

link at https://irisdocs.intersystems.com/irislatest/csp/documatic/%25CSP.Documa...

Hi Grace

I defer to those with experience in the field to offer comparative advice but concerning the Production Export functionality:

For existing environments it is possible to use the Export for deployment from the Production configuration page for one or more items and not the whole production. This allows changing existing items or adding items to a production when deploying the export file. When changing an item the deployment code will disable the item first if it is enabled and then re-enable the item as necessary after the deployment has finished.

It is possible to remove items using the deployment functionality but for this one needs to use Ens.Deployment.Util APIs and not the GUI to create the removal deployment package. 

Concerning settings - if you haven't seen perhaps System Default Settings might be appropriate  (https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY...).

An alternative use of System Default Settings by some sites is to use for the same values without having to enter per item - hence the option in the Export for deployment dialog  to export deployable System Default Settings.

The Export from the Production configuration page attempts to identify what are linked items/code but might not be complete. This is the reason for being able to add Studio project contents to the export.  In version 2017.2.0 we added detection of RecordMap classes to be included in the export. 

Best wishes

James
 

Hi Amir

This issue is addressed in 2016.1.0

W x.GetValueAt("MSH.MSH~12.VID~1")
2.5

Best wishes

James

Thanks Scott,

Our EnsLib.HL7.Service.FTPService uses the FilePath setting in the Source information which does not account for the sub directory searching option:

OnProcessInput() line:

Set tIOStream.Name=pFTPStream.Attributes("Filename")_$C(13,10)_"via FTP "_..Adapter.FTPServer_":"_..Adapter.FTPPort_" path '"_..Adapter.FilePath_"'"
 

But the adapter is passing the actual path where the file was retrieved from in pFTPStream.Attributes("FTPDir") . I will make the change in EnsLib.HL7.Service.FTPService to use  pFTPStream.Attributes("FTPDir") instead of ..Adapter.FilePath but I am afraid I cannot advise on which release this will be in.

To verify from terminal using  write  ##class(EnsLib.HL7.Message).%OpenId(<id>).Source

returns before the code change:

somefile.hl7
via FTP 192.168.224.100:2121 path '/hl7'

to

somefile.hl7
via FTP 192.168.224.100:2121 path '/hl7/1/yellow/'

Would this be sufficient for your needs or since you state the reasons are more complicated  a more elegant solution in the Ensemble service is needed.

Kind regards

James