Related Posts
Hi , my base location is kolkata in ibm . And i just shifted to kolkata with my family. However i am tagged to a project Barclays client which is in pune and bangalore. Is there any chance of my base location getting changed any day in future in IBM.
Infosys Tata Consultancy IBM Accenture Cognizant Capgemini
Comments will help very much
More Posts
Hi fishes! The hiring manager has asked me for salary expectations of B6 Data Analyst and my experience is 3.5 yrs with a CTC of 6.65. Considering I have to move to Bangalore l'm thinking of asking 13 or 14.. is it a big ask? If so, what do you think is a good ask? Please help. Thanks in advance :)
Natwest group
Additional Posts in Salesforce Professionals
New to Fishbowl?
unlock all discussions on Fishbowl.


That’s where you as a consultant need to make the call of what the simplest path is. Just because a flow *can* be done, doesn’t mean it should.
If Apex can solve the problem more efficiently and with less overall tech burden, do it. Document the hell out of it, but do it.
Use invocable apex in a flow. Everyone wins.
Subject Expert
If it's so complex, why aren't you splitting it into smaller invokable subflows thst *are* manageable?
...I didn't say I wasn't? A flow with a bunch of sub flows is still a massive flow. Also, we're working with callouts, so we're still forced to use Apex (for parsing). So even if an admin can handle the flow itself, if anything ever changes on the API side (how the JSON is structured for example), they still need a dev 🙂
There's definitely some limitations and considerations:
1. Flow provides no way to either prevent DML operations from committing, or to throw custom errors; the addError() Apex method is not supported when executed from Flow via Apex invocable method.
2. It may take additional care and consideration to design your record-triggered automation, particularly if you require callouts to external systems or need to perpetuate state between processes.
3. Making your record-triggered automation performant is a multidimensional problem, and no design rule will encompass all the factors.
4. The Flow runtime automatically performs cross-batch bulkification on behalf of the user. However, it does not perform any functional bulkification.
5. Flow’s formula engine sporadically exhibits poor performance when resolving extremely complex formulas. This issue is exacerbated in batch use cases because formulas are currently both compiled and resolved serially during runtime.
https://architect.salesforce.com/decision-guides/trigger-automation
Do you have multiple flows on same object? I still prefer a trigger over flow specially for objects where I think flow would become a mess.
What other options would you design the automation?