#Ensemble

How to get rid of " 413 Request Entity Too Large" error?

I can see below where its defined, but cant find how its used. Where is the config defined, that I can change to get rid of this error.

Class: HS.API.REST.AbstractRESTAPI
Parameter HTTP413REQUESTENTITYTOOLARGE As %String = "413 Request Entity Too Large";

(Originally posted on InterSystems CODE by blaise Zarka, 10/27/14) The following code snippet includes methods for Ensemble that migrate the item settings for the given production to default. The class method "test" runs the process, and it takes the name of a production class as a string:

Class blaisezarka.MigrateSettingsToDefault [ Abstract ]
{
/// Migrate all items settings from production productionClassName to system default settings
ClassMethod test(productionClassName As %String) As %Status
{
set production = ##class(Ens.Config.Production).

Hi - If you want to embed Ensemble's Workflow Inbox, (that offers workflow task items to workflow users) inside of your application - you can access the URL directly without necessarily giving users access to the Management Portal - but more importantly, you can strip away the Titlebar, Worklists borders etc.

You do this by using the same URL parameters you would use, if embedding a regular DeepSee dashboard into your application.

For example, using &EMBED=1

removes all titles, borders and worklists.

Hey guys,

I'm working with an EnsLib.XML.X12.Document object which consists of a parent object along with multiple children.

When using the following code, my sent object is losing all references to its children.  I've played with the deep parameter and nothing is working to automatically clone the objects children(group docs ref)along with itself.  (Even though the documentation states that it should..)

objectClone = object.%ConstructClone()

d ..sendRequestAsync("Destination",objectClone)

Any insight would be really helpful.

Thanks!

Mitch

I tried to restore a backfile(.cbk) from ENSEMBLE 2010 version to ENSEMBLE 2009 version studio, it shows me "Class dictionary out of date, please run upgrade utility error $SYSTEM.OBJ.Upgrade()" message. I tried it but it doesn't work. Is there any other way to overcome this problem?

Thanks

Hi Team,

I have thought to write code,

To get Remote Ensemble(same network) Production details of ##class(Ens.Director).IsProductionRunning  

How can we get the 

While R&D,

Set rc=##class(%Net.RemoteConnection).%New()
 Set Status=rc.Connect("localhost","SAMPLES",1973,"_SYSTEM","SYS")

In Ensemble Management Portal > Security Management > Roles >Edit Roles... From Where the SQL tables and SQL Procedures shown in the above path of an ensemble management portal is displayed??

Thanks.

PL/SQL stands for Procedural Language extensions to the established question Language (square). square is a powerful language for both query integratedg and updat built-ing built-information integrated relational databases.

Oracle created PL/SQL that extends a few barriers of square to provide a extra comprehensive solution for built-ing undertakbuiltintegrated-crucial applications built-in on Oracle database.

PL/SQL is a built-ination of sq. together with the procedural capabilities of programm integratedg languages.

Hello Greetings-

I am exploring on converting HL7 to FHIR.

1. I saw there are built in DTLs “FHIR.FromSDA” and “FHIR.ToSDA” to convert SDA -> FHIR and FHIR -> SDA. Similarly Do Intersystems have DTLs for HL7 -> FHIR and FHIR -> HL7?

2. The reason why I am asking is, I see in HSLIB namespace HS->GateWay->HL7->HL7toSDA3 and HS->GateWay->SDA3->SDA3toHL7 DTLs. Like-wise I am trying to locate HL7 -> FHIR and FHIR -> HL7. Please help me to locate them

3. If there are no built-in DTLs for converting HL7 -> FHIR and FHIR -> HL7, what is the process to achieve this?

Thanks much in-advance.

Thanks,

Surya

hi, i find it very intersting topic, i'm working actually on a project based on intersystems plateform, my question is:

- when i develop a BPL and its corresponding rules, where can i go to extract defined rules code on (xdata) in the routine data base