go to post Luis Angel Pére... · Jan 31, 2024 I was checking the official documentation and I found out that you can rename that tag: https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI... https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI... You can modify the name, but not remove it.
go to post Luis Angel Pére... · Jan 31, 2024 Thank you @Jeffrey Drumm and @Hao Ma ! I'll try to find out the exact version of Red Hat 8
go to post Luis Angel Pére... · Jan 30, 2024 Take a look to this article, maybe it's helpful: https://community.intersystems.com/post/retrieving-base64-files-post-cal...
go to post Luis Angel Pére... · Jan 30, 2024 I'm not sure, but I think that it's a default behaviour of SOAP responses, it returns always the response wrapped in a tag with the name of the method that was invoked. Can't you manage it from the application who sent the request?
go to post Luis Angel Pére... · Jan 30, 2024 You are wellcome @Sylvain Guilbaud ! Thank you for the reference to the official documentation.
go to post Luis Angel Pére... · Jan 26, 2024 This is the only information related with logging in the documentation: https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI...
go to post Luis Angel Pére... · Jan 26, 2024 You can see a similar example here. In your case you can set in pResponse the name of the file created and read it from the business process.
go to post Luis Angel Pére... · Jan 26, 2024 The API call is async? Maybe you are comparing both variable before to the end of the API call.
go to post Luis Angel Pére... · Jan 26, 2024 Maybe is there whitespaces in context.Prov? Have you tried to remove it? if $ZSTRIP(context.Prov,"<>W") = $ZSTRIP(context.ProvName,"<>W")
go to post Luis Angel Pére... · Jan 23, 2024 Try killing from the operating system the process, check the process id that is being executed and kill it. Check this answer: https://community.intersystems.com/post/stop-running-sql-query-quickly#c...
go to post Luis Angel Pére... · Jan 23, 2024 You can check a similar question here: https://community.intersystems.com/post/stop-running-sql-query-quickly#c...
go to post Luis Angel Pére... · Jan 23, 2024 You can identify the id of the process and kill it from the operating system.
go to post Luis Angel Pére... · Jan 22, 2024 There is no problem to use Apache on Windows, even more, the former private web server was Apache.
go to post Luis Angel Pére... · Jan 21, 2024 Hi @Andreas Dieckow ! I wrote an article about the Apache Server installation, if any is interested here is it (with screenshots included!).
go to post Luis Angel Pére... · Jan 21, 2024 Your web application is configured to accept just Unauthenticated requests, if you want to use password authentication check it on the configuration. I think that your application is ignoring the user that you are using and that's the reason because you don't have the proper permissions.
go to post Luis Angel Pére... · Jan 20, 2024 Have the response messages between the business operation and the business process any relevant data? Any info about errors? Are you catching and logging the errors from the business operation?
go to post Luis Angel Pére... · Jan 19, 2024 Thank you guys!! It's a great satisfaction to be part of this wonderful community!
