Terms and Conditions

Compare Designer to default Workflow Module

Here I want to compare the feature of my Workflow Designer Module with the possibilities of the internal Workflow vtigerCRM Module.

The workflow trigger

internal module

  • Only on the first save
  • Until the first time the condition is true
  • Every time the record is saved
  • Every time a record is modified
  • Schedule (since vtigerCRM 6.1)
Workflow Designer

  • Equal:
    • Only on the first save
    • Every time the record is saved
    • Schedule
  • Additional
    • manually
    • when email is stored to the record
    • when new comment is created

Additionally the Workflow could guarantee
a workflow will executed only one time for every record

The missing trigger “until the first time the condition is true” is not implementable, because I allow multiple conditions in one workflow and you need to implement this trigger for yourself, which is possible. Also the “every time a record is modified” could be implemented in conditions, which could check if a field was modified.
The Conditions
internal module Workflow Designer
  • Limited to one AND group and one OR group
  • These groups could not nested within
  • Multiple OR and AND groups mixed together
  • These Groups could be unlimited nested within to build complex conditions
  • There could be multiple individual conditions within one workflow
The Actions

internal moduleWorkflow Designer

internal module Workflow Designer
 Send Mail

  • no attachments
    • pdf attachments needs PDFMaker extension, which had a complete different more usable standalone Action
  • no possibility to use mail templates
 Send Mail

  • multiple(unlimited) attachments could be loaded from Documents, PDFmaker and SQLReports
  • you could select a mail template which you like to use
 Invoke Custom Function

  • you could make use of plain php source code you implement externally
  • this action need access to the fileserver
 Invoke Custom Function

  • per default some basic PHP function could be used in the so called “custom expressions” in every textfield in every action. This allow to implement complex php scripts
  • no fileserver access is required
  • you could make use of only some basic PHP features
  • also you could create functions externally in plain php files if you need more advanced features, too. This requires access to the fileserver, too.
 Create Event/Create ToDo

  • only internal fields could be set
  • values could not loaded from record
 Create Event/Create ToDo

  • allmost equal but you also could set custom fields
  • configuration use multi-featured textfield with access to every fieldvalue
 Update field

  • set only fields from current record
  • load values only from current record
  • only simple expressions are possible
  Update field

  • set also fields in related modules
  • load values from the current AND related records
  • makes heavily use of the multi-featured textfield to build complex conditions
  Create field

  • I’m not sure, If I’m doing something wrong,
    but I could only create records from modules which are related to the current module
  • Completely not usefull!
  • No possible to create Invoices/Quotes …
   Create field

  • You could create records in every existing entity module
  • load values from the current AND related records
  • makes heavily use of the multi-featured textfield to build complex conditions
  • Within an extra Action you could create Invoice/Quote/…
 send SMS

  • basic sms functions
  • here you could access related fields values!
  send SMS

  • equal functions like internal one
  • additionally you could use custom expressions, like in every task
…  lots of additional features.
See here for a simple task comparison