...
- You can use only email alerts that are associated with the same object that the process is associated with. The record that started the process is used as the starting point for any merge fields that are used in the email alert
Activating
- You can't activate a process unless it has at least one action on EVERY node.
- You can NOT activate a process if there are more than 50 Active workflow rules on that object already. Note: you can keep creating workflows if there are more than 50 workflows, but you will get stopped if you try to deploy a workflow from Sandbox, or activate a process. (See https://help.salesforce.com/apex/HTViewSolution?id=000181391&language=en_US).
- If it has been activated, you can't save it even as a new Version of the process - you have to save it as a completely new process.
- It doesn't even prefill what you had previously saved it as - you have to look at the name on the process behind the save as dialog.
- You can't delete a process if it was used in the past 12 hours - this is a huge PITA for testing processes. Probably why it is better to do them in sandbox and push them over only after they are really ready.
...
I suggest you use Formulas instead - it is at least somewhat readable.
Nodes
- You can't set up one Node at the top of the process to be the general criteria that all nodes follow below. Eg, I wanted to set the top node to be - only do all of the things below, IF the Campaign is Active, and the start date is > today. But because I did not want to do any actions on that node, I could not activate the process.
- So, I have to put those criteria of Campaign = Active and Start Date > Today into each and every node - eg I want a Node that runs on Campaign Member Status = Enrolled, and another than runs on CM Status = Completed.
Updates
Fields
- Can't use formulas for creating field values. Options:
- Create the formulas in other fields
- Use Publisher Actions
- Use Flow Triggers.
...