Is Process builder a complete alternate for the triggers

Question

I need to do some analysis on process builder for taking a decision on config vs coding.

Saying that process builder is the alternate for the Triggers for updating the child records.

After creating some processes I noticed the following.

1) It can update the child records after meeting a condition on the parent record.

--> Here my observation is what if we need to update only specific child records, that means we are running out of options in this case we can not exert conditions at child record level.

--> So far I came across the couple of posts on bulk update or inserts issues with the process builder. for reference

https://success.salesforce.com/ideaView?id=08730000000DhBlAAK.

Process Builder Error with Bulk API

So here I would like to submit my analysis as process builder is not the complete alternate for the triggers since it has limitations on updating or inserting child records and also in doing the bulk updates/inserts. My question is I am I analysing the right way or missing some thing and if there is any thing more can i add to it.

Answer 1

Process builder is not meant to be the complete alternative for triggers but it can eliminate some. I see it more as an eventual replacement for workflow. As far as the child records, in Summer 15 there is an update that deals with that, from the release notes here:

Define Additional Conditions When Updating Records

When you update records in your process, you can now filter the records you’re updating using conditions.

To add conditions in an Update Records action:

Select the Updated records meet all conditions option.

Set the conditions that you want to use to filter the updated records.

Example

Let’s say your process updates the status of a parent case when the status of the child case is changed. You can now specify conditions (2) so that, for example, you won’t update the parent case (1) if its status is set to On Hold (3).

Answer 2

One other thing to consider:

If you use triggers, you are forced to write testmethods and if you do a good job of this (lots of asserts, positive and negative tests, ...), you'll end up with a comprehensive set of regression tests

If you use Process Builder, this testing requirement has to be met in other ways:

• A browser automated testing tool (Selenium)
• Your own (possibly haphazard) UI testing before release
• Wait for users to complain something isn't working
• Apex testmethods that simulate the CRUD event and then assert expected results

Answer 3

Trouble I had with process builder was:

1. Max 200 records per batch.
2. If you also have a trigger on the same object, this trigger would run per record basis. So if you had SOQL query there, effectively, the batch limit is 100.