We can understand process builder as a point-and-click apparatus that lets you effortlessly mechanize if/then trade forms and see a graphical representation of your handle as you construct. Each prepare comprises a trigger, at slightest one criteria node, and at slightest one activity. You'll be able to arrange prompt activities or plan activities to be executed at a particular time.
The Handle Builder can combine different workflows into a single preparation and can have a chain of criteria (if-then statements). It can relate to different activities for each criterion. It can have child records updated. The builder can get to pinnacle code and basic errands can be supplanted with a prepared builder. Notifications can be connected to both chatter gather and mail alarms.
Criteria are if-else based and will not move to downstream criteria on the off chance that best criteria aren't met (subsequent criteria), be that as it may, there's a later alter permitting for the method to re-evaluate. The activity cannot be reused (with the special case of email caution) and must be redefined for each criterion. Editing a handle (after creation) involves cloning and altering, you'll be able not to alter a prepare once it’s saved. Some standard areas (action due date) for the occasion are still not able to be overhauled in case they cannot be upgraded through the standard workflow.
Discussing the fact of deployment of process builder or flows in Salesforce from sandbox to production org, here let me share my view over deployment through change set.
Coming to change set first let's go through this, Utilize alter sets to send customizations from one Salesforce org to another. For case, you'll be able to make and test an unused question in a sandbox org, at that point send it to your generation org employing an alter set. Alter sets can contain as it were adjustments you'll make through the Setup menu. Once you need to send customizations from your current org to another org, make an outbound alter set. Once you send the altar set, the getting org sees it as an inbound change set.
Step 1: For creating an outbound change set:
- Go to setup
- Enter outbound change set in the quick find box
- Click new
- You will be redirected to the Change set edit page
- Provide Name and Description and click on Save button
Step 2: For adding process builder or flows to this change set:
- Select the add button on the Change set components section, you will be redirected to add to the change set page.
- Select flow definitions from the Component type.
- Then select the process that you want to migrate.
- Click on the Add to change set button.
- For uploading this change set, click upload and select the target org where you want to migrate the process builder.
Step 3: From target production org:
- After logging in to the production org, go to the inbound change set where you can see the deployed change set.
- Click deploy.
- Once the deployment is completed successfully, all changes are committed.
Step 4: For activating the process builder in the production org:
- Go to process builder and select the process builder that was deployed and
- Click on activate.