Utilizing (Web) Request Data
Together with API data sources, Request Data makes FlexiForms very powerful. You can pass external data to the form via the HTTP (a.k.a Web) request to the form.
Last updated
Together with API data sources, Request Data makes FlexiForms very powerful. You can pass external data to the form via the HTTP (a.k.a Web) request to the form.
Last updated
When you request a page (or any resource) on the internet, your request includes information such as the URL of the page, cookies sent by your browser, and more. This is referred to as (Web/HTTP) Request Data.
Request data contains important information, such as special key-value pairs (e.g., user_id=1456921) in the URL, your IP address, the origin of the request (the website from which you requested the resource), the browser you're using, the server that sent your request, and more.
Once you specify which parts of the request data you're interested in, FlexiForms makes good use of the specified data, especially the information from the URLs, in the following ways:
It makes that data available for your jobs. For example, you can display the user ID (from the URL) in an email or store it in the database. Similarly, you can store other details such as the IP address, browser, origin, etc., in the database.
You can use a piece of request data in your verification specifications. For example, the encoded value in the URL should match the passport provided by the user on the verification screen.
You can also use some request data to feed the form. This is especially useful to run different jobs by relying on a rule that will check the value of the passed query parameter. For example, if the form link has the query parameter mode=update (as in ), and if the rule for the Database Process Job (that is designed to update an existing job) is defined as mode="update", then the update job (rather than insert or delete job) is run.
