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

Steps to create a HTTP Event

1. On the Adeptia Suite homepage, click the Develop tab.

2. Go to Events > HTTP.

   The Manage HTTP Event screen is displayed (see Figure 713).

   

   Figure 713: Manage HTTP Trigger

3. Click the CreateNew link. The Create HTTP Event screen is displayed.

4. Enter the name and description of the new HTTP Trigger activity in the textboxes Name and Description respectively (see Figure 714).

   
   Figure 714: Create Http Trigger

   To learn about Advanced Properties refer to Changing Advanced Properties section. 
   
   If you want to learn about event misfire handling then, please refer to the Handling Misfire Event section. 
   
   To enable email error notification, please refer to the Creating Email Error Notification section.

5. Click the Save button.

   You can view details of a process flow associated with a HTTP event, by clicking the process flow displayed under Associated Process Flows on the Manage HTTP Event screen.

    

   
   Usage Recommendation

   To read the context variable, within a process flow following steps are required:

1. 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.
2. 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.
3. Change the value of the Property Event Context Enabled to yes.
4. Post the data using your HTTP client application to the following URL:

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

where
ServerName:          Name of the server where Adeptia Server is running.
ServerPort:            Port at which Adeptia 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 Adeptia Server
LoginPassword:   Password of the Adeptia Server
Group ID:            30 digit ID of the group, the user belongs to. To view Group ID of the group, click View in the Manage group page.