
Message Start Event (form)
Issues a Web form (its URL) for awaiting entry. Starts a new process automatically by receiving entry. The form can be embedded on any website using “iframe” HTML tag.
Capture

Notes
- User-type/Organization-type Data Items do not appear in web forms
- If [Page URL on Submit] has been set, it will be redirected to the specified URL after form submission
- It is possible to set an IP address filter by each URL of the form
- The URL of webforms to be published will be it the following syntax format
- {Your domain}/System/Event/MessageStartForm/{App ID}/{Node number}/{key}/view
- You can check the URL of web form in the property screen
- [API key] tab is where to specify the API key value that will be inserted to {key}
- Even though you can specify any character string for the API key, it is recommended to use a random character string that is automatically generated for security reason
- The API key can be set with single-byte alphanumeric characters, at most 100 in length
- You can specify the language of the published form by adding a query parameter to the URL
locale=enfor English,locale=jafor Japanese- Button names and input error messages will be displayed in the specified language
- Some button displays follow the language settings of your OS or browser
- You can specify initial values for input fields when the form is displayed by adding query parameters to the URL
- e.g.:
title=test&q_var1=foobar(specify the [title] or the field name of the Data Items as the parameter name) - URL encoding is needed
- The details of parameter names and value format are the same as [Message Start Event (HTTP)]
- e.g.:
- There is a possibility that Process not to be started automatically due to the limit of the number of startups of the entire Workflow platform
- There is a possibility that Process not to be started automatically due to the size limit of the data that can be received
Pingback: System Settings – IP Address Filtering – Questetra Support
Pingback: System Settings – App External Connectivity – Questetra Support
Pingback: Catalogue Request Correspondence Flow – Questetra Support
Pingback: Inquiry Handling Process – Questetra Support
Pingback: SLA Credits Issuance Flow – Questetra Support
Pingback: Product Demo Flow – Questetra Support
Pingback: Answer Drafting Flow – Questetra Support
Pingback: Event Participation Acceptance flow – Questetra Support
Pingback: Catalogue Request Correspondence Flow (Add-on) – Questetra Support
Pingback: Inquiry Response Flow – Questetra Support
Pingback: Seminar Registration 1 – Questetra Support
Pingback: Seminar Registration 4 – Questetra Support
Pingback: Seminar Registration 3 – Questetra Support
Pingback: Delete Seminar Application Information – Questetra Support