CoreBOSBB

Is there a way to test emails in workflows without waiting for the next workflow call? I would like to skip waiting up to 15 minutes to see what output I get.

Best regards
Henning

Have a look at evalwf.php helper script. It doesn't send the email but it shows it to you on screen:

http://blog.corebos.org:8080/en/blog/scheduledworkflows

(09-14-2017, 05:35 PM)joebordes Wrote: [ -> ]Have a look at evalwf.php helper script. It doesn't send the email but it shows it to you on screen:

http://blog.corebos.org:8080/en/blog/scheduledworkflows

I receive an error executing the evalwf.php script:




Looking at the crmid in table vtiger_crmentity I find 6 figure records. No records in the requested format 2digits x 2digits.

Where do I find the right IDs to test the workflows against?

use the latest version of evalwf, I add some changes to accept both application crmid and web service id

https://github.com/tsolucio/corebos/commit/85f767ef3c78ad49e0ed6693b37ea09dc3b83d14#diff-8b90b33df359c9f2cb3c4e5c57e74d60

Thank you, I applied the fixed file.

I call this address:




This is the output I get:



I looked up the crmid in the vtiger_crmentity table. The workflow is related to cbCalendar and the crmid is related to a cbCalendar item.
What do I miss?

---

OK, answering myself in case anybody did not see how to do this:

The URL parameters to be used with evalwf.php are three
$1 = workflowid (table ”com_vtiger_workflows”)
$2 = webservice entity id (table ”ws_entity”)
$3 = crmid (from table ”vtiger_crmentity”)

Now put together the three like this




This seems to be a strange way of doing it. Why not like this?

The explanation is that the workflow system works based on the web service interface. Even though it is totally embedded inside the application to all effects it could be a standalone application. Web service used the extended syntax to identify records (WSIDxCRMID). I modified the evalwf script to automatically convert the internal CRMID to the extended web service version, but the actual parameter that the workflow system needs is the Web Service ID. In short, that is how web services work, and that is how workflows work.

Thank you for the clarification.

Please forgive the lay people :-)

:-)