Workflows, Rules, Questions and Actions
ExecuteWorkflow-Operation
Workflows are a very powerful part of the application. They permit us to automate our business logic to some extent making it possible to standardize process and have the application do some of the repetitive tasks our business requires. When you want to trigger a workflow, only from outside of the coreBOS,ie. from the portal or anywhere else and you don't have access to activate it from the corebos system, then it should be set to System Mass Actions.
GET URL Format :
http://144.91.100.102:8880/corebos/webservice.php?operation=ExecuteWorkflow&sessionName={{sessionName}}&workflow=46&entities=["module_rest_idx77"]Query parameters
| Key | Value | Description |
|---|---|---|
| operation | ExecuteWorkflow | The operation you need to execute a workflow. |
| sessionName | {{sessionName}} | The value of a hashing value that you need to connect to coreBOS. |
| workflow | The workflow_id e.g. 46 | The workflow id that you want to trigger |
| entities | [module_id x record_id] e.g. [11x77] | The id of the module and the record that you want the workflow to be triggered |
Response
{
"success": true,
"result": true
}If the response is “success:true” then the workflow has been triggered e.g if you trigger a update field workflow task the result will be :
The wf update field tasks :
The account before the wf trigger:
The account after the wf trigger:
ExecuteWorkflowWithContext-Operation
Basically you can execute a workflow from outside corebos using the ExecuteWorkflowWithContext operation, which allows you to include a new parameter named context. The value of the parameter context can be any set of workflow context variables that your workflow supports. So, if you are sending an email, it can be an id of a Message Template(MsgTemplate) record you need to send. What does that mean? Typically you will create a workflow with a Send Mail task, but you don't want to hardcode the mail template. You create the send mail task only to define the recepients, and cc of the mail, while the template is decided on the webservice request itself. Saying that, the send mail task will serve only as a placeholder for the real template defined in the ws request. There is an extensive (and undocumented) list of context variables that permit tweaking the functionality of each workflow task. The other parameters remain the same, you have to define the id of the workflow that you need to execute, the id of the record that you need that workflow to be executed towards, and as always the sessionName in order to authenticate.
GET URL Format :
http://144.91.100.102:8880/corebos/webservice.php?operation=ExecuteWorkflowWithContext&sessionName={{sessionName}}&workflow=43&entities=["module_rest_idx244623"]&context={"SendThisMsgTemplate":44127}Query parameters
| Key | Value | Description |
|---|---|---|
| operation | ExecuteWorkflowWithContext | The operation you need to execute a workflow. |
| sessionName | {{sessionName}} | The value of a hashing value that you need to connect to coreBOS. |
| workflow | The workflow_id e.g. 43 | The workflow id that you want to trigger |
| entities | [module_id x record_id] e.g. ["module_rest_idx244623"] | The id of the module and the record that you want the workflow to be triggered |
| context | {"SendThisMsgTemplate":44127} | The context (message template) of the email that you want to send |
Response
{
"success": true,
"result": true
}If the response is “success:true” then the workflow has been triggered e.g if you trigger a send mail workflow the result will be :
The send mail tasks :
A message template that you want to send :
The email that has been sent have to be same with the context and no with th workflow send mail task:
