Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.
Hello; I am using a custom class extending CodeTableDetail (actually it extends CodeTableTranslated) for a MedicalClaimLine.Extension property for a Procedure Modifier value, in addition to the existing MedicalClaimLine.ProcedureModifierItems property (this is a list of %String). This works very well, stored AND translated correctly, until a valid ProcedureModifier value is used that is all punctuation: ##, **, or ++.
I am looking at a task which involves processing an XML file. Picking the file up from a folder (c:\test.xml) reading the data out of the XML and archiving the xml after it has been processed.
I was wondering what the best way of doing this would be?
I have got as far as creating a service in Ensemble. The Service I have created uses the class name EnsLib.XML.Object.Service.FileService.
Any advice or tutorials/guides would be much appreciated.
I am wondering if anyone would know where I can get a copy of the ASTM E1394 specification for an ASTM-XML file based instrument to LIS interface I am writing?
how can I check repeating XML fields in a rule? I want to search a repeating sub Element fields for one or more numbers. Subelement(*) returns the counter of the elements, but I expected by a () to search all fields.
I'm using %XML.Writer to write XML files from a database source, and I see that it is not encoding carriage return or line feed as 
 and 
 respectively, and is instead leaving them unencode.
Here FileContent field in json will contain converted base64 string of very large pdf(10pages). I need to submit this json as a payload to REST endpoint.
You might of seen or might of not seen my earlier post about Exporting a Production from 2018.1 to import it into 2021.1. I was able to get the export working, however I noticed in reviewing the data within the export, our previous Workday XML Schemas that we imported via XSD files were not in the export. When walking through the export process under Message Schema or vDoc Schema I could not find the missing XML Schema structures. Why aren't XML's part of the export process if they are used within the Production?
I'm trying to output a XML file, mapped from a ORU_R01 2.3 HL7 message, with a file name based of fields in the source HL7 message in the following format,
I'm new to ObjectScript and I've been experimenting the correlate method of %XML.Reader to convert an XML file I've loaded into its corresponding class. But, I have found that I am not getting all the child items of an element in a List contained within the converted class, only the last item.
A permanent job opportunity has arisen for a Caché/Ensemble /Iris developer with at least 2 years experience. My client is a specialist resource provisioner of developers for high profile clients in the finance, healthcare, retail, distribution and credit business that are mainly based in central London. My client is looking for a highly-motivated individual who thrives in an environment where problems are open-ended.
Once a week we are attempting to load an XML file from Workday into a MS SQL table using JDBC and Store Procedures. There is approx 102999 records in this XML file. We are struggling with processing the entire file within a reason amount of time. We feed the XML through a BPL to then populate values in a stored procedure then call the stored procedure through a Business Operation. I have tried splitting out the Business Operations to make two calls, but we still continue to see an issue loading the XML into MS SQL.
When I put a trace on a datastream that is a JSON object, I use the .%ToJSON(). Is there an equivalent to working with XML objects to view in the trace?
I have very recently started to work with Ensemble and have both the 2014 and the 2017 version.
To learn, I have created a small test flow that takes an xml file using EnsLib.EDI.XML.Service.FileService, sends it to a Process that transforms it with xslt into another format, and then passes it onwards to a EnsLib.EDI.XML.Operation.FileOperation Business Operation.
This is the code that I have before and when sending it onwards:
I've created a custom class that extends to the standard HS.Message.PatientSearchRequest. Inside the custom class i just want to pass the data as input only.
But i am getting ERROR #6277: Type attribute, s01:AcoPatientSearchRequest, does not specify valid type for XML input tag: pRequest (ending at line 5 character 171) </error>
I tried adding Parameter XMLIGNOREINVALIDTAG = 1; and
How do you determine what namespace to use for your custom SAML attributes? We want to receive patient context (first name, last name, dob, gender, etc.)
OASIS has resource-id but none of the other attributes. urn:oasis:names:tc:xacml:1.0:resource:resource-id
If I export a class definition to an XML file, is there a way to programmatically import it so that I could schedule a task to look in a given location for XML files once a day and import class definitions?
I have created a method than evaluates an XML expression using the EvaluateExpression method. I need to replace an element value by other string but I couldn't find the way of doing it.
By update