go to post Sebastian Thiele · Mar 7, 2019 Hi Eduard,already did this. the role %Developer should already include the %EnsRole ressources. Even assigning them to the created role manually gives me that error when logging in. Somehow as part of the login procedure, the cachelib db is accessed. Even if granting the ressources of cachelib the error remains.kind regards,sebastian
go to post Sebastian Thiele · Feb 22, 2019 If you are running Ensemble or HealthShare you may have a look at Ens.Util.Time or Ens.DataType.UTC. They provide an API to work with different time formats and also theire conversions. In Ens.DataType.UTC there is a method timeLocaltoUTC pass in you value and you don´t have to worry about.
go to post Sebastian Thiele · Jan 8, 2019 Thank you Eduard for the fast response on my questions. This totaly meets my usecase.Best regards,Sebastian
go to post Sebastian Thiele · Aug 17, 2018 Hi,as my advisor told me. This is a bug in Ensemble/Caché release 2017.2.2 since the intended behaviour to set sqltablename on serverside is sufficient and this specific security consideration reported a "false positive" - if I got it right a correction for this is available with ensemle 2018.1 and is identified as SAM524. The current workaround is to use both approaches setting tablename on the server and use permitclientsql = "true".Anyway I´ll mark this issue here as solved/answered.Best regards,Sebastian
go to post Sebastian Thiele · Aug 4, 2018 Hi,after talking to WRC and some testing. The approach altering the ZEN tablePane, tableName on the server as depicted above works until 2017.1.2. From 2017.2.1 it seems to be reqiured to have an additional property for the tablePane to be set. This property is calles ´permitClientSQL´ (set to true). This isn´t well documented in my opinion and the behaviour is to weaken the security. But even when set to true this property still requires to have the tableName property on the server despite documentation says something different.They´ll have a look at it, since my advior himself wasn´t quite sure what that change between 2017.1 and 2017.2 is about. Keep you update when I´ve got some new details.best regards,sebastian
go to post Sebastian Thiele · Mar 7, 2018 Digging the intersystems learning facility the course can also be found through the learning catalogue on learning.intersystems.com.best regards,Sebastian
go to post Sebastian Thiele · Mar 6, 2018 Hi,the link seems to be broken. Any chance to get this article back up?best regards,sebastian
go to post Sebastian Thiele · Dec 5, 2017 Hi,after looking into the example and some local testing I found this is what I am looking for. Anyway one of the major points in my opinion is to deseriialize the email into a stream, write this one into a file an pass it to the oppenssl command and parse the result. Are there any suggestions for the step of deserialization the email with it´s entire contents to a stream? The api seams at least not the have a direct method(s) for this. Hof can this be achieved?Best regards,sebastian
go to post Sebastian Thiele · Dec 4, 2017 Hi Dimitry,thank you for the fast response. I will test the approach with a locally created certificate get back with my findings.best regards,sebastian
go to post Sebastian Thiele · Oct 24, 2017 Hi Jamie,thank you for the hint given. Unfortunately I was not able to find any sub tags for the given field PatientPrimaryLanguageCodeSequence. The NEMA DICOM docs only state this field as SQ (a structured type) which sub-tags are need to be used is not clear. Anyway as from my tests. Ensemble try to evaluate the path set when constructing an entry for the dicom document - and in my case for that specific field fails with<EnsDICOM>InvalidPropertyReference: The property reference 'PatientPrimaryLanguageCodeSequence[1].someTag'is invalid: Tag name not found in dictionary: 1 at offset 40 - parsing property referencebest regards,Sebastian
