Invocable processes can be used to modularize logic sections of our operations. The invocable process starts when invoked by another process, where the normal process passes the record into the invocable process. These processes are handy for implementing actions across multiple groups or for nesting logic. An example highlighted involved automating updates based on changes in support levels and regions. To invoke an invocable process, create multiple ones with different criteria in the process builder.
The summer '19 release brings a much-needed feature, the 'Notification Builder'. Unlike previous methods which used workarounds such as chatter group, users can now create and trigger custom in-app notifications using the process builder. The feature allows customization of notification messages and merging fields. Additionally, notifications can be specific to changes to records like 'Opportunity'.
The custom object's record should be set as "Public Read Only" for visibility to all users but editable only by the owner. In case of picklist field edits, the record will auto-assign to the editing user's groups through Process Builder, allowing them edit access while restricting the previous assignee. A profile giving 'Read' and 'Edit' permissions and user-assigned queues are also needed in this setup.