Share
ReportHi Everyone,
Most complex plugin.
Thanks in advance
Happy CRM'ing
*This post is locked for comments
You’re offline. This is a read only version of the page.
594
Hi Everyone,
Most complex plugin.
Thanks in advance
Happy CRM'ing
*This post is locked for comments
Fong,
Thanks for replying to my post. By complex i meant which one plugin that you implemented was tough,complex and took lot of time to work on it. I need your real time work experience example.
I appreciate if u could share it with me.
For me, When i was new I experienced recursive behaviour from pre-update plugins when updating the same record.
We need to make use of images and check the depth of the loop to overcome the issues of recursive behaviour.
Hi,
I disagree that a complex workflow is inherently bad - workflows are a tool to let you extend CRM and to say a complex working = bad design is like saying a complex plugin = bad design. I'm a developer at heart and put out a tool to let people build really copmlex workflows that used to require custom code (it's Workflow Elements at KaskelaSolutions.com). Here are two specific examples I've used this in the last few weeks:
Only with the native workflow activities and out of the box stuff (receipt email)
When an order is complete:
- Query for the products on the order (Workflow Elements)
- Check for some condition in the results
- Send an email and include the products as content
Here's a second one a little more difficult. It's to generate an invoice, generate a Word doc receipt and email to the customer:
When a case is resolved
- Query if there's already an invoice (Workflow Elements)
- If not, create a new invoice and add the line item
- Query for the Case Resolution record (to get billing details)
- Add a product to the invoice for billable time spend (Workflow Elements)
- Kick off a child workflow on the invoice
(on demand child workflow on the invoice)
- Generate a word doc from a template (out of the box)
- Rename the document to include the invoice number (Workflow Elements)
- Create an email message to the customer (CREATE, NOT SEND)
- Attach the document to the email (Workflow Elements)
- Send the email to the customer (Workflow Elements)
- // the last 3 steps repeated but email to a sales manager
// We're even looking into using PowerCharge from Power Objects to automatically charge their card on file in they have one and sending out a Receipt instead of an Invoice.
You might look at that and say it's too complex, but I say that it lets the user have a fully customized billing and receipt system without having to write a line of code. They're able to change any part of it when they want to, without the cost and time of having their partner do it.
Hope this helps! I'd appreciate if you'd mark this as Answering your question.
Thanks,
Aiden
This is very subjective :)
When the plugins is too complicated means the architecture is wrong.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (