Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:extensions:workflowdesigner:httphandler [2014/01/05 14:02] swarnat |
en:extensions:workflowdesigner:httphandler [2016/11/14 01:18] (current) swarnat |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| <WRAP info> | <WRAP info> | ||
| === use cases === | === use cases === | ||
| - | * replacement of Webserive for Record Creation, like Forms on Webpage for Lead collection | + | * replacement of Webservice for Record Creation, like Forms on Webpage for Lead collection |
| * execute special processes from webpage (External Administrations) if the record ID of organization is known (generation of quotes, ...) | * execute special processes from webpage (External Administrations) if the record ID of organization is known (generation of quotes, ...) | ||
| </WRAP> | </WRAP> | ||
| Line 32: | Line 32: | ||
| To configure the Workflow/Trigger you want to execute, use the following GET Variables: | To configure the Workflow/Trigger you want to execute, use the following GET Variables: | ||
| - | * **workflow_trigger**\\ Which trigger should be triggered. Set by trigger key (CUSTOM_43) | ||
| * **record_id**\\ Which record from CRM should be used by Workflow Designer to append the Workflow\\ If you don't want to connect a record, set the record_id = 0 | * **record_id**\\ Which record from CRM should be used by Workflow Designer to append the Workflow\\ If you don't want to connect a record, set the record_id = 0 | ||
| * **workflow_id**\\ Which Workflow should be executed? You get the Workflow ID from the URL in administration | * **workflow_id**\\ Which Workflow should be executed? You get the Workflow ID from the URL in administration | ||
| Line 48: | Line 47: | ||
| The values could be used inside the executed workflows in the **$env** variable. | The values could be used inside the executed workflows in the **$env** variable. | ||
| - | For example if you submit a variable //lastname// to the workflow, you could access the variable in every task of this workflow by using ''$env["lastname"]''. | + | For example if you submit a variable //lastname// to the HTTP Handler URL, you could access the variable in every task of this workflow by using ''$env["lastname"]''. |
| - | ===== Technical implementation ===== | ||
| - | |||
| - | - Call ''<urlofvtigerCRM>/modules/Workflow2/HTTPHandler.php?<ExecutionConfiguration>'' | ||
| - | - Submit any Variable you want to use in Workflow via POST values. | ||
| - | - At the moment, there is no useful return value | ||
| ===== Examples ====== | ===== Examples ====== | ||
| Line 61: | Line 55: | ||
| <code php> | <code php> | ||
| - | $url = '<urlofvtigerCRM>/modules/Workflow2/HTTPHandler.php?<ExecutionConfiguration>'; | + | $url = '<urlofvtigerCRM>/<shorturl>&<ExecutionConfiguration>'; |
| $fields = array( | $fields = array( | ||
| Line 87: | Line 81: | ||
| <code php> | <code php> | ||
| - | $url = '<urlofvtigerCRM>/modules/Workflow2/HTTPHandler.php?record_id=852&workflow_id=77'; | + | $url = '<urlofvtigerCRM>/<shorturl>?record_id=852&workflow_id=77'; |
| $fields = array( | $fields = array( | ||