I use markdowntopdf, but there are many online and offline services with the similar capabilities. I have created a release with PDFs.

> Would you have three branches for the code or 3 repo's.
Please describe differences between your DEV, TEST, PROD code. Still, I'd probably recommend one repo and 3 branches.

>Would you have three projects in Atelier to communicate with the environments and GitHub?
No, there would be one Atelier project for DEV. All other code propagation should be done automatically by Continuous Integration/Continuous Delivery solution.

That may mean one of the several things:

• You're not specifying or specifyiong incorrectly one or several request header parameters. One of the most often encountered errors is not specifying ContentType as application/json.
• Request content is formed incorrectly

Anyway, to solve this problem you need to make a correct request to the target system, record it and compare to the Ensemble request. Here's an article on that.

Why don't you want to do it in the rule editor?

Your first link leads to class documentation root.

In any place (but preferably in the beginning) of your REST handler method add these lines:

set %response.ContentType = "text/html"
do ##class(%CSP.Utils).DisplayAllObjects()
quit $$$OK

and then open REST Url to see all current objects, including %request.

You can use %Dictionary package to modify classes.

For example you can open property which is an object of %Dictionary.PropertyDefinition, modify it and save. Recompile the class to see new class definition.

Here's an example of %Dictionary modification to create new method.

1. Source control
   • GitHub releases are exactly for that - a place for users to get "binaries" - xmls with everything in our case. Check out DeepSeeWeb releases for an example.
2. Code
   • Sure, I've done something similar. Here's the code.
   • Missed that, sorry.
3. Ensemble
   • Sure, Inside your production you have access to all BO properties, including retry-relevant:  ..RetryCount, ..%LastReportedError and many others. So first you determine if the current message is a retry (..RetryCount>0) or not and then you can decide what to do with your request based on that.

Code for the custom adapter that specifies Content type:

Class Production.Adapter.HTTPOutboundAdapter Extends EnsLib.HTTP.OutboundAdapter
{

Method Post(Output pHttpResponse As %Net.HttpResponse, pFormVarNames As %String, pData...) As %Status
{
    quit ..SendFormDataArray(.pHttpResponse, "POST", ..GetRequest(), .pFormVarNames, .pData)
}

ClassMethod GetRequest() As %Net.HttpRequest
{
    set request = ##class(%Net.HttpRequest).%New()
    set request.ContentType = "application/json"
    quit request
}

}

Note that this way only one-line method Post gets redefined (you'll also need to redefine Get method, but still - these are small one-line methods). ContentType may be further refactored as a setting.

Some comments

1. Source control
   • Each class should be in a separate file. There are many source control hooks available.
   • When redefining system methods like SendFormDataArray method in DLS.HTTP.OutboundAdapter class it's better to do it in two commits - in a first one you just copy method as is and in a second you modify it. It's easier to understand "what changed?" that way (via git blame).
2. Code
   • Do not subclass/modify system methods if it's possible. What was modified SendFormDataArray?
   • Add comments to the parts you change when you must subclass/modify system methods.
   • $CLASSNAME($THIS) is equal to $CLASSNAME()
3. Ensemble
   • Instead of manual error handling in DLS.REST.OperationV2 you can use error  handling available in Ensemble. Check out Reply Code Actions, Retry Interval and Failure Timeout.

Business Rule Definition is stored as XML in XData block named RuleDefinition inside rule class and can be (de)serialized as an object of Ens.Rule.Model.ruleDefinition class. Some utility methods are available there.

Here's an example of modifying Demo.ComplexMap.Rule.SemesterBatchRouting rule in ENSDEMO class. It modifies "when" condition from 1 to 0.

zn "ENSDEMO"
set ruleClass = "Demo.ComplexMap.Rule.SemesterBatchRouting"
set sc = ##class(Ens.Rule.Model.ruleDefinition).LoadFromClass(ruleClass, .rule)
set rule.ruleSets.GetAt(1).actions.GetAt(1).whens.GetAt(1).condition=0
w rule.SaveAs(ruleClass)
set sc=$system.OBJ.Compile(ruleClass,"k-d")

That said, I think the better approach would be to use (in order of
increasing implementation difficulty):

• Context Class
• Temporary Variables
• Rule Assist Class

So the rule by itself does not change but values supplied by Context Class/Temporary Variables/etc do.

You can decode JSON escaped characters:

set string = $zcvt(string, "I", "JSON")

and remove special symbols after that.

• Business Services receive or pull information from external systems
• Business Processes do application logic
• Business Operations send information into external systems

You can get output from %ToJSON() into a variable without any redirection:

set jsonString = dynamicObj.%ToJSON()

iKnow or iFind?

If iFind, then what index?

It depends on your corpus, and diversity of concepts encountered there.

I have 1:1 as corpus size:index size as a baseline, but it all depends on many factors.

Documentation.

w $zv

Also note, that $SYSTEM.Version class provides several utility methods to get some part of version and so on.