Menu
Welcome, Guest
Username: Password: Remember me

TOPIC: Suitecrm custom workflow vs Mysql Store procedure

Suitecrm custom workflow vs Mysql Store procedure 3 months 1 week ago #86996

  • rigal
  • rigal's Avatar
  • Offline
  • New Member
  • Posts: 17
  • Karma: 0
Hello,

Which with a better way to manage automation (when a new user is added in Suite CRM make a new entry in two-three custom modules I am thinking to make suite CRM workflow. Custom workflow slow down response ? or store procedures better way.


Antone, please give your suggestions and feedback?

Thanks
The administrator has disabled public write access.

Suitecrm custom workflow vs Mysql Store procedure 3 months 1 week ago #86997

  • diligent
  • diligent's Avatar
  • Offline
  • Moderator
  • Posts: 99
  • Thank you received: 28
  • Karma: 3
My personal opinion: avoid database triggers whenever it is possible.

you'll find a lot of discussions like:
stackoverflow.com/questions/460316/are-database-triggers-evil

in the end, it's your decision.
The administrator has disabled public write access.

Suitecrm custom workflow vs Mysql Store procedure 3 months 1 week ago #86999

  • ashish@outrightcrm.com
  • ashish@outrightcrm.com's Avatar
  • Online
  • SuiteCRM Is My Life
  • CTO at outright Systems
  • Posts: 447
  • Thank you received: 53
  • Karma: 5
A database trigger/strored procedure is not good when you serious with managing CRM application.

a CRM application is huge growing nature, using triggers will kill whole application integrity. Here is main reasons.

1) The application doesn't know what happened end data and why it is changed.
2) The application doesn't know when it is going to changed.
3) The application will not log anything, logger really helps to debug the application.

So my personal opinion is to maintain everything on application level. Don't use trigger / stored proedures. Rest your choice!
The administrator has disabled public write access.
Time to create page: 0.064 seconds
Powered by Kunena Forum