HTTPRequestHandler

This actionhandler is not supported anymore.

Description

This handler sends an HTTP message with the passed parameters. If the parameter ADDBLOGARTICLE=true is set, then the result is attached to the instance as a note.

Class

com.dooris.bpm.actionhandler.HTTPRequestHandler

Parameter

Parameter	Default value	Description	Valid examples

Parameter	Default value	Description
`HTTP_HOSTNAME`		This parameter contains the URL, to which the parameters should be sent.
`POST_PARAMETER`		Parameters that are to be sent. The various parameters are separated by the entry NEXTPARAMETER.
`GET_PARAMETER`		Parameters that are to be sent. The various parameters are separated by the entry NEXTPARAMETER. Only one of the two methods is to be used. The preferred method is dependent on the type of data transfer. Sensitive data should preferably be set using POST_PARAMETER.
`HTTPRESPONSESTART`		Here, the transaction results are stored.
`LOGRESPONSE`	`true`	Tells if the reply to the request should be logged out.
`LOGREQUEST`	`true`	Tells if the request should be logged.
`ADDBLOGARTICLE`	`false`	Tells if the reply should be attached to the process as a note.

Example:

In this example, a request to create a new user is sent. The POST_PARAMETER is used to pass the user data, such as the user ID, the name, and the email.

The content of the POST_PARAMETER also contains HTML code (<br/> tags). To avoid a transaction error, the method content must be embedded in the addition <![CDATA[...]].

The result of the data transfer is then stored in HTTPRESPONSEART.

HTTP_HOSTNAME=http://examplehost.com/loom-portal/custom/test/user-data.html
POST_PARAMETER=<![CDATA[userId=${userId}NEXTPARAMETERuserName=${userName}NEXTPARAMETERmessage=Please create the requested user according to the following information<br />Email: ${userEmail}<br />Department:${department}<br />superior:${supervisor}]]
HTTPRESPONSESTART=sapTicketNr