The Event Notification callout allows clients to choose to be notified through web services when certain actions take place in their Concur company. If the client uses Concur Expense, the supported events are the Expense report entering the Post-Submit or Pre-Extract workflow steps. If the client uses Concur Travel Request, the supported events are the Travel Request entering the Post-Submit or Pre-Extract workflow steps. When the event happens, Concur generates a notification and places it into the notification system queue. When the notification reaches the front of the queue, Concur sends a request to the configured endpoint with event information.
This callout differs from the standard Concur web services in the following ways:
An example use of this callout is:
This is one use case for the Event Notification callout, however it can be used for a wide variety of requirements.
Concur products are highly configurable, and not all clients will have access to all features.
Partner developers must determine which configurations are required for their solution prior to the review process.
Existing clients can work with Concur Advantage Technical Services to create custom applications that work with their configuration.
The configuration process has the following steps:
Third-party developer, client or Concur downloads, installs, configures, and customizes the application connector. The application connector may make requests to the inbound web services.
The developer or the Concur clients registers the application connector.
Refer to Installation > Process for the detailed steps.
Once the configuration is complete, the callout uses the following process:
Concur will make calls to the application connector’s endpoint using SSL. During configuration, Concur will connect to the application connector to validate that its hostname and access credentials are valid.
In the code Concur provides for a sample application connector, credentials are stored in a web configuration file that varies by platform, such as web.xml or web.config. However, if you are hosting the connector, you can customize where and how the credentials are stored by customizing HTTPBasicAuth.java or Authentication.cs.
Expense or Travel Request will not be able to connect to the application connector until a certificate signed by a Certificate Authority (CA) is installed in the application connector. If you are hosting the application connector, you will need to install the signed certificate before Concur can access the connector.
Authentication between Concur and the application connector is performed using HTTP Basic Auth. By default, these credentials are stored in the appropriate web configuration file for your platform, such as web.xml or web.config. These credentials are entered in Concur on the Register Application Connector page in Web Services under Administration.
Refer to the Callouts and Application Connectors page for more information.
Post Event Notification Request
The installation process includes installing the application connector, and registering it with Concur.
| Field | Description |
|---|---|
| Name | Enter the name that should appear in the list of connectors. |
| Description | Enter the description of the function of the connector, such as what back-end system it might connect to. |
| Host Name | Enter the hostname for the connector. Example: https://{servername} |
| User Name | Enter the user name required to authenticate with the host. This must be the same as the user name specified in the configuration file for the application connector, using HTTP Basic Auth. |
| Password | Enter the password required to authenticate with the host. This must be the same as the password specified in the configuration file for the application connector, using HTTP Basic Auth. |
Refer to the HTTP Codes page for details of the common responses and errors.