what is ExtentFunc?

For each persistent class there is an Extent class query that returns IDs.

For Sample.Employee class it is:

SELECT ID, Name, SSN, Home_City, Home_State FROM Sample.Employee

For each class query, <QueryName>Func  method gets generated.

You can see it in the class int code using  Show Other View (Open Sample.Employee and press Ctrl+Shift+V).

Here's the generated <QueryName>Func  method for the Extent query of the Sample.Employee class:

zExtentFunc() public {
    try {
        set tSchemaPath = ##class(%SQL.Statement).%ClassPath($classname())
            set tStatement = ##class(%SQL.Statement).%New(,tSchemaPath)
            do tStatement.prepare(" SELECT ID , Name , SSN , Home_City , Home_State FROM Sample . Employee")
        set tResult = tStatement.%Execute()
    }
    catch tException { if '$Isobject($Get(tResult)) { set tResult = ##class(%SQL.StatementResult).%New() } set tResult.%SQLCODE=tException.AsSQLCODE(),tResult.%Message=tException.AsSQLMessage() }
    Quit tResult }

It executes the query and returns result set. More on class queries.

class %sqlcq.SAMPLES.cls9

To see the code:

• Go to General SQL settings in SMP and set Cached Query - Save Source to Yes.
• Purge cached queries from sample namespace.
• Execute this query again.
• Check the new query class name- probably  %sqlcq.SAMPLES.cls1
• It now could be seen in studio

Ensemble runs under other user, so:

1. Compare environment variables from terminal and Ensemble (path is especially important):

do $zf(-1,"set > vars.txt")

2. Check that ensemble can access all required files.

3. Check working directory.

4. (Optional) Provide full paths to all files and binaries.

Sample.Company and Sample.Employee share one company/many employees relationship.

Do you want to iterate over employees and display a company name for each?

set rs = ##class(Sample.Employee).ExtentFunc()
while rs.%Next() { set emp = ##class(Sample.Employee).%OpenId(rs.ID) w emp.Company.Name,! }

You can even get company names even without opening objects:

set rs = ##class(Sample.Employee).ExtentFunc()
while rs.%Next() { w ##class(Sample.Company).NameGetStored(##class(Sample.Employee).CompanyGetStored(rs.ID)),! }

Fixed.

I mean pertaining to this article.

So far NodeJS is only used as a general dev environment and build pipeline manager.

Maybe front-end would communicate with Caché backend via REST API? Or websockets?

You can convert binary openssl output to base64 and write that to file:

s cmd=$$$FormatText("openssl dgst -sha256 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 -sign %1 %2 | base64 > %3",fileKey,fileMsg,file64)

base64 is available in most linux flavors, and on Windows in various GNU CoreUtils builds and in Git (usually under C:\Program Files\Git\usr\bin\).

Also in an a business operation filenames should be generated randomly (probably via ##clss(%File).TempFilename(ext)) to avoid conflicts.

I didn't know that

#include %occCPTJSgen

Redefines $$$TAB. Seems useful. Thanks.

Please note that $$$TAB macro is actually a whitespace:

ClassMethod GetTab() [ CodeMode = expression ]
{
$$$TAB
}

Call to GetTab returns:

USER>zzdump ##class(Utils.Persistent).GetTab()
0000: 20

I usually use either $c(9) or user-defined macro for tabulation.

You'll need a Business Service and a Business Operation.

Business service runs every X seconds (or you can configure a more complicated schedule) gets a list of hosts and calls Business Operation. Business Operation performs the request.

do ##class(%Compiler.UDL.TextServices).GetTextAsString(namespace, class, .text)
write text

You can write custom queries and create custom result sets that iterate over globals, etc. and expose them via ODBC.

There's no need to search for the /s1/s2/s3 in the second template, as the first template would send every node into the second template. So your XSLT should probably look like this:

<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:output method="xml" indent="yes"/>
     
    <xsl:template match="//@* | //node()">
        <xsl:copy>
            <xsl:apply-templates select="@*"/>
            <xsl:apply-templates select="node()"/>
        </xsl:copy>
    </xsl:template>
    
    <xsl:template match="//s3" >
        <xsl:copy>
            <xsl:apply-templates select="@*"/>
            Content Replaced
        </xsl:copy>
    </xsl:template>
    
</xsl:stylesheet>

As both Angular and Zen manage page state, combining them it does not seem particularly promising.

Here's the wrapper I usually use.