https://www.youtube.com/embed/Fh0uyC9owyE [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
For a long time, we have been using a utility in production to export the result of a query to an Excel spreadsheet. Moreover, we have applied a modification of it, in which the explicit setting of column formats is a priority.
I'm able to log into my local instance of HealthShare through the Management Portal, but once I've done so, the screen is entirely blank. I'm still able to access Terminal and Studio without any issue, as well as a hosted instance's Management Portal. I've tried stopping and starting HealthShare, no luck. I've been working on this instance for the past several months and haven't experienced anything like this, and I don't know of anything that I was doing that would have broken the Management Portal. Anyone have a suggestion as to where to go from here?
Maybe someone has a logger for incoming CSP requests and willing to share? Debugging high traffic HTTPS application and wireshark just doesn't cut it sometimes. So I thought I'd ask here. I'm especially interested in getting raw stream of incoming request.
Accessing an Azure cloud storage to upload/download blobs is quite easy using the designated %Net.Cloud.Storage.Client class API methods, or using the EnsLib.CloudStorage.* inbound/outbound adaptors.
Note that you'll need to have the %JavaServer External Language Server up and running to use the cloud storage API or adaptors, since they both use the PEX framework using the Java Server.
I need to create a routing rule where I've got to check for the value of "-" in field 5 of a repeating RQD segment, if the "-" is found in any of the RQD-5 I want to send it to a transform, if the rule doesn't find a "-" in any of the RQD-5 I want to send it to another transform.
Unfortunately we are running an older version of Ensemble and the foreach function is not available.
The other thing to add is the transforms are writing the output to a flat file so my business process is using the EnsLib.MsgRouter.RoutingEngine class.
Hello all, I am creating a REST API with a spec-first approach. However, I am using the try-catch method to handle any exception if any occurs. But whenever any error related to syntax or something occurs, we get internal server error
We are looking for a 3rd party application that can scan our IRIS based Cache Object Script code for vulnerabilities or coding weaknesses. There are many, many applications/vendors out there that do code scanning but none seem to support Cache Object Script or scanning the IRIS environment. If anyone is aware of a company/product that can scan our code / IRIS environment, I would love to hear about it.
The fhir-react project defines a unique component which renders the interface based on FHIR resource type. There's no need for any configuration because the library uses the standard of defined by the resource type.
So, I decided to apply the same idea, but for charts. The basic idea is depicted below:
Can we use Functions and Methods with multiple parameters and refer objects by reference as parameters inside Routing rule ?
How do we handle DB related workflows in Business Rules ? How can we perform Response object based handling in Business Rules ? Can we try by extending methods with Ens.Util.FunctionSet and pass in the Context object from the rule as a parameter for certain functions ? Can we split the Business Operations into methods that can be used from the routing rules and create the message route request flow ?
I have some problem with getting data from external source (PostgreSQL) via JDBC and load it in DeepSee and I resolved some problems while writing this question :)
I have 3 classes defined to model the team/team-member/employee relationship, where each employee can belong to multiple teams, each team can have multiple employees, and one and only one team member is a team leader:
I am pleased to announce that Caché and Ensemble 2015.2.3 are now available as maintenance releases. For a complete list of the corrections in 2015.2.3, please review the release notes.
Caché and Ensemble 2015.2.3 are available now for the same platforms as 2015.2.2
The complete set of supported platforms, including specific point releases and/or patches, is detailed in the Supported Platforms document.