HTTP Event

Owned by Akash Kumar Jaiswal (Unlicensed)
Last updated: Jan 24, 2023 by Rohan Dhanwade (Deactivated)
2 min read

The HTTP event enables you to schedule a process flow to be triggered when an HTTP request is made to Connect Server. It also allows the request to pass the data to the process flow. The trigger can be used by an HTTP client application to integrate with process flow, deployed on the Connect Server. 

Steps to create an HTTP event:

  1. Click Configure >EVENTS > HTTP.

  2. Click Create HTTP Event.

  3. On the Create HTTP Event screen, type the name and description of the new HTTP Event in the Name and Description fields respectively.



  4. Expand Advanced Properties to view the advanced properties of an HTTP Event.



  5. Type the email id in the Notification Receiver Email-ID(s) (comma separated) to receive error emails related to this HTTP event.

  6. Select Trigger in Sequence check box to trigger the associated process flow in a sequential manner. If you do not select the Trigger in Sequence check box then the associated process flow will trigger concurrently.

  7. Select the Project in the Project field. This option is visible only when GAC is enabled.

  8. Click Save.

Usage Recommendation

While creating the process flow, create a process flow variable. To know, how to create Process Flow Variable, refer to the section Creating Process Flow Variable.

Following steps are required to read the context variable within a process flow:

  1. Use this process flow variable as Context Source within process flow. To know, how to use a Process Flow Variable as Context Source, refer to the section Using Context Source and Context Target.
  2. Change the value of the Property Event Context Enabled to yes.
  3. Post the data using your HTTP client application to the following URL:

http://<servername>:<serverport>/rest/aisresources/receiveservlet?activityID=<entityid>&userID=<loginname>&password=<loginpassword>&group=IndigoGroup:<Group ID>

where,

ServerName:          Name of the server where Connect Server is running.
ServerPort:            Port at which Connect Server is running. By default, it is 8080.
EntityID:                30 digit ID of the HTTP Trigger activity. To view Entity ID of the HTTP Trigger, click View in the HTTP Trigger Page.
LoginName:         User ID of the Connect  Server
LoginPassword:   Password of the Connect Server
Group ID:            30 digit ID of the group, the user belongs to. 

You may be interested in...
What's new
Best practices
Training guides
Frequently asked questions
Adeptia Connect APIs
Adeptia security report