{"id":6139,"date":"2018-01-02T22:41:05","date_gmt":"2018-01-02T22:41:05","guid":{"rendered":"https:\/\/alt2.minisoft.com\/support\/?p=6139"},"modified":"2020-07-02T10:02:32","modified_gmt":"2020-07-02T17:02:32","slug":"web-service-post-call-output","status":"publish","type":"post","link":"https:\/\/www.minisoft.com\/support\/web-service-post-call-output\/","title":{"rendered":"Web Service POST Call Output"},"content":{"rendered":"

To follow along with this guide, please download the following files: OutputGuide<\/a><\/p>\n

This guide will demonstrate how to output a eFORMz project using a web service call by two different forms. ProjectB.efz\u00a0calls eFORMz using a configuration file stored on the eFORMz Web Server. A single URL parameter of \u201cconfig\u201d with a relative file location of the configuration file is used. The data is POSTed as an XML file.<\/p>\n

ProjectC.efz calls eFORMz for \u201coutput\u201d using a ServiceConfiguration wrapper. The URL has no additional parameters. The XML data is wrapped in an <InputData> element within a <ServiceConfguration> root. The root contains the processing details. Parameters for a web service call may be found in this document: https:\/\/minisoft.com\/support\/index.php\/eformz-api-url-parameters\/<\/a><\/p>\n

What is the output parameter used for in a web service call? It is to output data from an eFORMz project immediately. In this guide we will create a .XML file output that is accessible from a web service call in the ProjectB.efz file.<\/p>\n

NOTE:<\/span><\/strong><\/p>\n

This is purely an example<\/strong> and eFORMz would not be used this way<\/span><\/strong> in a production environment. eFORMz can use a Rule “Output from Project” that doesn’t use a web service call to receive the output from another project in eFORMz.<\/p>\n

This is to show how applications can use the functionality of a web service call to eFORMz’s web service API. Any application that can call a web service will have to use the following URLs in this guide.<\/p>\n

Here is a reference to the guide.
\neFORMz API URL Parameters<\/a><\/p>\n

Output a eFORMz project using a web service call<\/h2>\n

Here we have the variables for the project. The Filename variable is used to determine where to place the output file.<\/p>\n

1. Set value to variable \u201cFull Data File Name\u201d. \u201cFull Data File Name\u201d is the full file path from where the eFORMz project input data is located and \u201cData File Name\u201d is the name of the file after the full file path. If you had an input data file called \u201cExampleXML.xml\u201d the \u201cFull Data File Name\u201d would be the path\u2026\\ExampleXML.xml and \u201cData File Name\u201d would be ExampleXML.xml.<\/p>\n

2. We will replace the Data File Name with variable Current Time (Timestamp). Current Time (Timestamp) returns the current time as the number of milliseconds since. An example of ProjectB\u2019s filename path could be \u201c1514917018286.xml\u201d<\/p>\n

\"\"<\/a><\/p>\n

The variable URL is used for the web service URL that is accepted by eFORMz:<\/p>\n

http:\/\/localhost:8001\/servlet\/com.minisoft.AppServer.AppServer?APP=com.minisoft.eformz.eFORMzApp&output&project=projectpath&format=.xml<\/code><\/p>\n

3. Set the value to the desired URL.<\/p>\n

\"\"<\/a><\/p>\n

4. Variable XMLData is the \u201cRequestData\u201d. This variable needs to have some sort of input data to be able to send the web service call. We are using Load from File, but you can also use Set value to send XML data as well.<\/p>\n

\"\"<\/a>\"\"<\/a><\/p>\n

5. The variable Response data is a variable that uses the Write To File function to write in the output data from the eFORMz project that the web service is calling, MIME Output Data from the web service call to the variable Filename.<\/p>\n

\"\"<\/a><\/p>\n

6. The variable response Code is used to display the web service call status codes. 500 is an error and 200 is successful.<\/p>\n

\"\"<\/a><\/p>\n

The Post-condition procedure is used to start the Web Service call action.<\/p>\n

8. Create the web service action.<\/p>\n

\"\"<\/a><\/p>\n

9.\u00a0The Web Service Procedure uses the RequestData variable. Create an action inside of the Web Service.<\/p>\n

\"\"<\/a><\/p>\n

10.\u00a0Right click on the web service call action and open the properties window.<\/p>\n

\"\"<\/a><\/p>\n

11. Select the Request verb POST. Select this action to use the variable that was assigned the Web Service call URL. In our example it is URL. Set the input data and output data to MIME. In our example we are passing through XML, so the content type is set to XML. The MIME Output Data is set to the variable ResponseData.<\/p>\n

12.\u00a0Set the variable ResponseCode. This will return error codes from the Web Service to better monitor if the service was successful.<\/p>\n

\"\"<\/a><\/p>\n

13.\u00a0Display Forms and Data will refresh the eFORMz project, which will create another Web Service call.<\/p>\n

\"\"<\/a><\/p>\n

14.\u00a0The ResponseCode will be set to 200 and the ResponseData will have the output information from the eFORMz project you are calling if it was successfully. The XML file has been created.<\/p>\n

\"\"<\/a><\/p>\n

15.\u00a0The eFORMz project that you are calling must be returning data. In this example we can see that MapPackSlipData() is being used to return XML data.<\/p>\n

\"\"<\/a> \"\"<\/a><\/p>\n

References<\/h2>\n

For more details on the eFORMz API, consult the following posts:<\/p>\n

eFORMz API (Called as a Web Service)<\/a>
\neFORMz API .NET Web Service Call<\/a>
\neFORMz API URL Parameters<\/a>
\nWeb Service POST call to \u201cWake Up\u201d a \u201cSleeping\u201d Queue: Part 1<\/a>
\nWeb Service POST call to \u201cWake Up\u201d a \u201cSleeping\u201d Queue: Part 2<\/a>
\nWeb Service POST call to \u201cWake Up\u201d a \u201cSleeping\u201d Queue: Part 3<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

To follow along with this guide, please download the following files: OutputGuide This guide will demonstrate how to output a eFORMz project using a web service call by two different forms. ProjectB.efz\u00a0calls eFORMz using a configuration file stored on the eFORMz Web Server. A single URL parameter of \u201cconfig\u201d with a relative file location of […]<\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[346,342,340,25],"_links":{"self":[{"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/6139"}],"collection":[{"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/comments?post=6139"}],"version-history":[{"count":7,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/6139\/revisions"}],"predecessor-version":[{"id":8187,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/6139\/revisions\/8187"}],"wp:attachment":[{"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/media?parent=6139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/categories?post=6139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/tags?post=6139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}