Hello,

Unfortunately, the SOAP-Header settings functionality is not yet implemented.

 

As a workaround, we can suggest configuring the request body and passing it as a parameter

- If you are using a web service in the process, the "Call web service" element has a "Request body" parameter. It can be found in advanced settings mode.

 

Hello Federico,

Yes, it is possible to add XML attributes in SOAP integration web services. In SOAP, XML attributes can be added to the SOAP message header and body elements. The SOAP message header contains optional attributes that provide additional information about the message, while the SOAP message body can have attributes that describe the data being transmitted.

To add XML attributes to a SOAP message, you need to define the attribute in the WSDL file and then include the attribute in the SOAP message. The WSDL file specifies the XML schema that defines the structure of the SOAP message, including any attributes that are allowed.

You can add XML attributes to the SOAP message using various programming languages and tools, such as Java, .NET, and PHP. For example, in Java, you can use the JAX-WS API to add attributes to the SOAP message header and body elements.

It is important to note that adding XML attributes to a SOAP message can impact the interoperability of the web service, as different systems may interpret the attributes differently. Therefore, it is recommended to follow the XML schema standards and best practices when adding attributes to SOAP messages.



Best regards,

Bogdan S.

Bogdan Spasibov,

Can you give me a example how to add this in the parameters?

I need to add MessageId="getAccountMsg" and 

  <DeviceInformation DeviceType="CREATIO" DeviceNumber="0000"/> I can't make it works using the webservice integration.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:acc="http://www.symxchange.generated.symitar.com/account" xmlns:tns="http://www.symxchange.generated.symitar.com/common/dto/common">
   <soapenv:Header/>
   <soapenv:Body>
      <acc:getAccount>
         <Request MessageId="getAccountMsg">
            <AccountNumber>1234</AccountNumber>
               <UserNumberCredentials>
                  <!--Optional:-->
                  <UserNumber</UserNumber>
                  <Password></Password>
               </UserNumberCredentials>
            </Credentials>
            <DeviceInformation DeviceType="CREATIO" DeviceNumber="000000"/>
         </Request>
      </acc:getAccount>
   </soapenv:Body>
</soapenv:Envelope>

To add the MessageId="getAccountMsg" and <DeviceInformation DeviceType="CREATIO" DeviceNumber="0000"/> parameters to the SOAP request, you would need to modify the XML code as follows:



<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:acc="http://www.symxchange.generated.symitar.com/account" xmlns:tns="http://www.symxchange.generated.symitar.com/common/dto/common">

   <soapenv:Header/>

   <soapenv:Body>

      <acc:getAccount>

         <Request MessageId="getAccountMsg">

            <AccountNumber>1234</AccountNumber>

            <UserNumberCredentials>

               <!--Optional:-->

               <UserNumber></UserNumber>

               <Password></Password>

            </UserNumberCredentials>

            <DeviceInformation DeviceType="CREATIO" DeviceNumber="0000"/>

         </Request>

      </acc:getAccount>

   </soapenv:Body>

</soapenv:Envelope>

 

Anton Starikov,

Hi Anton I need to know how to add that in the UI since from the wdsl is not taking that value like is in the xml. I need a example to see how to add the parameter in the UI for the attribute MessageId.

Hello,

You can create this service manually.

Because this is an OOTB behavior with the value "is array".

Hi Kalymbet Anastasia,

Sorry, but I didn't understand your answer. The property "Is array" is true by default.

Do I need to create the soap request using a script task? 

Best Regards,

Pedro Pinheiro

Pedro Pinheiro,

Yes, you're right. When the request parameter is of type object the collection is considered a typed array and the checkbox is checked by default and not editable.



In this case, using a script task for the SOAP service would solve the case.



BR,

Bhoobalan Palanivelu.

Hi Pedro,

Maybe it's better to call the https://<instance>/0/rest/FileService/GetFile/7B332DB9-3993-4136-AC32-09353333CC7A/fileId for all the files and receive a response from the third party service? You need to call this link for each record from the DocumentFile table (filed should be modified for each time with an actual Id of a record from the DocumentFile table). Previously we didn't have such requests and we have no practical example of the logic deployment. The link above is a base link used to download attachments when clicking them on the "Attachments" detail so you can try calling it in the webservice.

Best regards,

Oscar

Hello Pedro,

You need to develop a configuration service (either regular or anonymous) using SOAP. Here is the article that describes how to configure web-services and integrate them into the Creatio app.

For example:

1) Create a source code for the service contract SPMSUBPServiceContract:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Runtime.Serialization;
using System.ServiceModel;
using System.ServiceModel.Web;
using System.Text;
 
namespace SPMSUBPService
{
    [ServiceContract]
    public interface IService
    {
        [OperationContract]
        SPMClientInfoResponse SPMClientInfo(string Login);
    }
 
    [DataContract]
    public class SPMClientInfoResponse
    {
        bool success = true;
        string errorText = "";
 
        [DataMember]
        public bool Success
        {
            get { return success; }
            set { success = value; }
        }
 
        [DataMember]
        public string ErrorText
        {
            get { return errorText; }
            set { errorText = value; }
        }
    }
}

and the source code of the SPMSUBPService service directly:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Runtime.Serialization;
using System.ServiceModel;
using System.ServiceModel.Web;
using System.Text;
 
namespace SPMSUBPService
{
    public class SPMSUBPService : IService
    {
        public SPMClientInfoResponse SPMClientInfo(string Login)
        {
            return new SPMClientInfoResponse();
        }
    }
}

2) Create a file with SPMSUBPService.svc name in the Terrasoft.WebApp\ServiceModel folder with the following text:

<%@ ServiceHost Language="C#" Debug="true" Service="SPMSUBPService.SPMSUBPService" Factory="System.ServiceModel.Activation.ServiceHostFactory" %>

3) Add the description of the service to the Terrasoft.WebApp\ServiceModel\http\services.config file:

<services>
    ...
    <service behaviorConfiguration="BaseServiceBehavior" name="SPMSUBPService.SPMSUBPService">
        <endpoint name="SPMSUBPServiceEndPoint"
            binding="webHttpBinding"
            behaviorConfiguration="RestServiceBehavior"
            bindingNamespace="http://Terrasoft.WebApp.ServiceModel"
            contract="SPMSUBPService.IService" />
        <endpoint address="soap" binding="basicHttpBinding" contract="SPMSUBPService.IService"/>
        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
    </service>
    ...
</services>

4) Modify the Terrasoft.WebApp\Web.config file:

...
<location path="ServiceModel/SPMSUBPService.svc">
    <system.web>
      <authorization>
        <allow users="*" />
      </authorization>
    </system.web>
</location>
...

And everything is ready, the service is accessible via /0/ServiceModel/SPMSUBPService.svc and the WSDL as well /0/ServiceModel/SPMSUBPService.svc?singleWsdl

Best regards,

Oscar

Oscar Dylan,

Thank you for your response.

I've tried to implement the solution you provided above and I'm getting this error when sending a request through both Postman and SoapUI.

Can you please tell me what this error means and how can I fix it?

Thanks in Advance.

Best Regards,

Pedro Pinheiro

Hi Pedro Pinheiro,

Did you got the WSDL file. For me it is showing 404 not found error if I try to access that url.

Also how can we know the what input format to pass parameters to method. Can you share those details here.

Thanks in advance.

Regards,

Manideep.

Hi Korni Manideep Reddy,

We manage to make this service working, but since it was a long time ago we don't have the specific steps to fix the error.

However,  we have the updated steps that we use in order to make the service available. Maybe if you go through these following steps  you could fix your problem.

Note: These steps only work for .Net Framework instances.

1. Create a new file called “DemoServiceName.svc" in ..\Terrasoft.WebApp\ServiceModel folder, and add this line:

<%@ ServiceHost Language="C#" Debug="true" Service="Terrasoft.Configuration.DemoServiceNameSpace.DemoServiceName” Factory="System.ServiceModel.Activation.ServiceHostFactory" %>

2. Add the following configuration to the ..\Terrasoft.WebApp\web.config file:

<configuration>

  ...

  <location path="ServiceModel/DemoServiceName.svc">

    <system.web>

      <authorization>

        <allow users="*" />

      </authorization>

    </system.web>

  </location>

  ...

  <appSettings>

    ...

    <add key="AllowedLocations" value="https://yourwebsitedomain.creatio.com/0/;ServiceModel/DemoServiceName.s…"  />

    ...

  </appSettings>

  ...

</configuration>

3. Add the following service to the ..\Terrasoft.WebApp\ServiceModel\https\services.config file:

    <service behaviorConfiguration="BaseServiceBehavior" name="Terrasoft.Configuration.DemoServiceNameSpace.DemoServiceName">

        <endpoint name=“DemoServiceNameEndpoint" address="" binding="webHttpBinding" behaviorConfiguration="RestServiceBehavior" bindingNamespace="http://Terrasoft.WebApp.ServiceModel" contract="Terrasoft.Configuration.DemoServiceNameSpace.IDemoServiceNameRest" />

        <endpoint address="soap/demoservicename” binding="basicHttpBinding" contract="Terrasoft.Configuration.DemoServiceNameSpace.IDemoServiceNameSoap"/>

    </service>

4. Add the following service to the ..\Terrasoft.WebApp\ServiceModel\http\services.config file:

    <service behaviorConfiguration="BaseServiceBehavior" name="Terrasoft.Configuration.DemoServiceNameSpace.DemoServiceName">

        <endpoint name="DemoServiceNameEndpoint" address="" binding="webHttpBinding" behaviorConfiguration="RestServiceBehavior" bindingNamespace="http://Terrasoft.WebApp.ServiceModel" contract="Terrasoft.Configuration.DemoServiceNameSpace.IDemoServiceNameRest" />

        <endpoint address="soap/demoservicename" binding="basicHttpBinding" contract="Terrasoft.Configuration.DemoServiceNameSpace.IDemoServiceNameSoap"/>

    </service>

5. In the ..\Terrasoft.WebApp\ServiceModel\https\bindings.config file we need to change the basicHttpBinding to:

<basicHttpBinding>

        <binding maxReceivedMessageSize="10485760">

            <readerQuotas maxDepth="32" maxStringContentLength="10485760" maxArrayLength="10485760" maxBytesPerRead="10485760"/>

            <security mode="Transport">

                <transport clientCredentialType="None" />

            </security>

        </binding>

        <binding name="ReportServiceBinding">

            <security mode="Transport">

                <transport clientCredentialType="None" />

            </security>

        </binding>

</basicHttpBinding>

6. In the ..\Terrasoft.WebApp\ServiceModel\http\bindings.config file we need to change the basicHttpBinding to:

<basicHttpBinding>

    <binding maxReceivedMessageSize="10485760">

        <readerQuotas maxDepth="32" maxStringContentLength="10485760" maxArrayLength="10485760" maxBytesPerRead="10485760"/>

        <security mode="Transport">

            <transport clientCredentialType="None" />

        </security>

    </binding>

    <binding name="ReportServiceBinding" />

</basicHttpBinding>

After all of this changes are made the application needs to be restarted.

About the input format of the method, we used a CustomObject and CustomResponse which we define using the DataContract attribute.

        public class DemoServiceName: IDemoServiceNameRest, IDemoServiceNameSoap {
             //This service needs to be anonymous.
             //Implement Methods here. you don't need to define WebInvoke here.
        }
 
        [ServiceContract]
		public interface IDemoServiceNameSoap
		{
           	[OperationContract]
		    CustomResponse MethodNameSoap(CustomObject cobject);  
		}
 
 
		[ServiceContract]
		public interface IDemoServiceNameRest
		{
          	[OperationContract]
			[WebInvoke(Method = "POST", RequestFormat = WebMessageFormat.Xml, ResponseFormat = WebMessageFormat.Xml, BodyStyle = WebMessageBodyStyle.Bare)]
		    CustomResponse MethodNameRest(CustomObject cobject);
		}

Hope this helps solving your issue.

Best Regards,

Pedro Pinheiro

Hi Pedro Pinheiro,

I have tried above configuration settings But I am still not able to set  soap service. I am getting 500 ServiceActivationException.

Rakshith Dheer Reddy,

What is the error description you receive when trying to access "http://localhost:83/0/ServiceModel/SoapTestService.svc" through a browser?

Best Regards,

Pedro Pinheiro

Pedro Pinheiro,

We are getting this error from the browser. 

Hi Pedro Pinheiro,

In Postman, I am getting 500 error with ActionNotSupported.

Hi Kumaran K,

Sorry, I forgot to mention that you need to add the service behavior for the metadata. This can be done with the following steps:

1. In the ..\Terrasoft.WebApp\ServiceModel\https\behaviors.config file we need to set the httpsGetEnabled to true on both behaviors:

<serviceBehaviors>
 
...
 
              <behavior name="BaseServiceBehavior">
 
                       ...
 
                       <serviceMetadata httpsGetEnabled="true" />
 
                       ...
 
              </behavior>
 
             <behavior name="RestServiceBehavior">
 
                       ...
 
                       <serviceMetadata httpsGetEnabled="true" />
 
                       ...
 
             </behavior>
 
...
 
</serviceBehaviors>

2. In the ..\Terrasoft.WebApp\ServiceModel\http\behaviors.config file we need to set the httpGetEnabled to true on both behaviors:

<serviceBehaviors>
 
...
 
              <behavior name="BaseServiceBehavior">
 
                       ...
 
                       <serviceMetadata httpGetEnabled="true" />
 
                       ...
 
              </behavior>
 
             <behavior name="RestServiceBehavior">
 
                       ...
 
                       <serviceMetadata httpGetEnabled="true" />
 
                       ...
 
             </behavior>
 
...</serviceBehaviors>

Hope this helps.

Best Regards,

Pedro Pinheiro

Pedro Pinheiro,

Thank you, Pedro.

The soap service is working.