Nova postagem

Encontrar

Artigo
· Abr. 21, 2024 1min de leitura

Dynamic <call> target in BPL

Hi all,

When making a Business Process reusable, I needed to make the target of a <call> configurable as a business host setting. This can be done through indirection. Here's how:

Property TargetConfigName As Ens.DataType.ConfigName;

Parameter SETTINGS = "TargetConfigName:Basic";

/// BPL Definition
XData BPL [ XMLNamespace = "http://www.intersystems.com/bpl]
{
<process language='objectscript' request='Ens.Request' response='Ens.Response' height='2000' width='2000' >
<sequence xend='200' yend='450' >
<call name='Call configurable target' target='@process.TargetConfigName' async='1' xpos='200' ypos='250' >
<request type='Ens.Request>
<assign property="callrequestvalue="requestaction="set" />
</request>
<response type='Ens.Response>
<assign property="responsevalue="callresponseaction="set" />
</response>
</call>
<sync name='Wait' calls='Call configurable target' type='all' xpos='200' ypos='350' />
</sequence>
</process>
}
5 Comments
Discussão (5)3
Entre ou crie uma conta para continuar
Pergunta
· Abr. 20, 2024

There's any way to edit a SOAP header?

Hello everyone, I need some help. 

I have to send some events for a government WebService that I already imported the WSDL and XSD's and It worked fine and I'm able to build the message and connect into the service, but It has been rejected with the message that the XML is wrong and the only diference between the Caché SOAP message to all the examples that the government gave us is the header:

   

This is how the Government is expecting the message:

<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
	<soap12:Body>
		<cteDadosMsg
			xmlns="http://www.portalfiscal.inf.br/cte/wsdl/CTeStatusServicoV4">
			-----------------Dynamic XML Body------------------
		</cteDadosMsg>
	</soap12:Body>
</soap12:Envelope>

 

And this is how It's generate in Cache:

  <  ?xml version="1.0" encoding="UTF-8" ?>
<SOAP-ENV:Envelope
           xmlns:SOAP-ENV='http://www.w3.org/2003/05/soap-envelope'
            xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
          xmlns:s='http://www.w3.org/2001/XMLSchema'>
          <SOAP-ENV:Body>
                     <cteDadosMsg
                              xmlns="http://www.portalfiscal.inf.br/cte/wsdl/CTeRecepcaoEventoV4">
                              -----------------Dynamic XML Body------------------ 
                     </cteDadosMsg>
         </SOAP-ENV:Body>
</SOAP-ENV:Envelope>  

 

 

So, there's any way to edit It before invoke the webMethod or any configuration that made it during the process?

Thank you so much!!

10 Comments
Discussão (10)2
Entre ou crie uma conta para continuar
Artigo
· Abr. 20, 2024 1min de leitura

Utilisation des paramètres de procédure avec ODBC/JDBC

Bonjour,
Je me débattais avec une procédure qui devait recevoir une chaîne de caractères et l'utiliser comme filtre, j'ai découvert que puisque je voulais que la procédure fasse une transformation de données et retourne un ensemble de données, j'avais besoin d'utiliser le langage objectScript.
J'ai créé la procédure en utilisant l'interface graphique SQL dans le portail, et tout fonctionne correctement lorsque j'appelle la procédure à partir de l'interface graphique SQL, mais pas à travers une connexion JDBC - voici l'appel "call spPatientOS('2024-04-07T12:35:32Z')".
Le résultat est que la procédure a été créée avec le paramètre défini comme STRING(MAXLEN=1), ce qui signifie que mon paramètre provenant de la connexion JDBC a été tronqué à "call spPatientOS('2')"
La modification du MAXLEN a résolu le problème.
HTH,
Eyal

Traduit avec DeepL.com (version gratuite)

Discussão (0)1
Entre ou crie uma conta para continuar
Pergunta
· Abr. 20, 2024

OpenAPI property mismatch in Spec First approach IRIS documentation

Hello Community,

I just go through the IRIS latest documentation and I found the openAPI property is  "x-ISC_DispatchParent" was mentioned in sample swagger and its the actual property used in spec-first approach. However in some place the property was mentioned like "x-ISC_DispParent"  and bit discrepant
/confused. So, Just want to ensure Is this is an issue in documentation?

Thanks.

Ashok.

2 Comments
Discussão (2)2
Entre ou crie uma conta para continuar
Anúncio
· Abr. 19, 2024

[Video] Organizing HL7 FHIR Resources

Hi Developers,

Watch the latest video on InterSystems Developers YouTube:

⏯ Organizing HL7 FHIR Resources

See how HL7 FHIR resources can be organized and connected to help create a complete patient record. With FHIR resources, you can group information from outside sources or from other FHIR resources to make relevant information easy to find and share.

Stay tuned for more videos! 👍

Discussão (0)1
Entre ou crie uma conta para continuar