--- schema_version: "1" id: d19b8c8693d622b5d4e85d2c7428181b4de896dee461add9dced959783aba5e0 title: Process Builder Advanced Option Considerations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_advanced_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_advanced_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 90e4570762f9b8e158fa7b0de1e889ebc79ad61b839d17a022f6d96ee8c92cb4 description: Keep these considerations in mind when choosing advanced options. products: - Flow Builder - Salesforce Platform release: "264" --- # Process Builder Advanced Option Considerations Keep these considerations in mind when choosing advanced options. ### Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions
![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png) Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US). After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your [switch to Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules."). - Avoid creating an infinite loop when allowing your process to reevaluate records. For example, if your process checks whether an account description changes and then updates an account description and creates a Chatter post every time an account record is created or edited, the process evaluates and triggers actions resulting in six Chatter posts. - If you choose to evaluate a record multiple times in a single save operation when you specify an object for your process, we recommend not setting any of your criteria to No criteria—simply execute the actions! - If your process uses ISCHANGED, ISNEW, or PRIORVALUE formula functions, we recommend that you don’t use the advanced options. If you do use advanced options, keep these considerations in mind. - When a record is first created, ISNEW evaluates to true. If your process uses the ISNEW formula function and reevaluates a record multiple times in a single save operation, the process executes actions multiple times. For example, your process checks whether an account is created or updated. Each time the criteria is evaluated, ISNEW evaluates to true. The result is six Chatter posts. This example is true only if the process is triggered because an account record is created. - When ISNEW evaluates to true, the process updates the account’s annual revenue and posts to Chatter. - When the process updates the account’s annual revenue, the process then reevaluates the record (up to five additional times) because the record was changed. - When a record is created, PRIORVALUE returns the current value as the prior value. When a record is updated, PRIORVALUE returns the field value that was set immediately before the save operation started. If your process uses the PRIORVALUE formula function and reevaluates a record multiple times in a single operation, the process executes actions multiple times. If your process reevaluates a record multiple times in a single save operation and executes actions only when specified criteria changes, the prior value returns the values that existed before the record was saved. For example, your process checks whether an account is created or updated. Each time the record is reevaluated, the prior value of the account’s type is Prospect. The result is six Chatter posts. - Wen PRIORVALUE(\[Account\].Type) = 'Prospect' evaluates to true, the process updates the account’s annual revenue and posts to Chatter. - When an account is created with Prospect as the account type, the criteria is always true until the end of the process transaction. - If the process is changed to update the account type to Other when the criteria is true, then for an account created with Prospect as the account type, the formula PRIORVALUE(\[Account\].Type) = 'Prospect' is true until the end of the process transaction. - ISCHANGED always evaluates to false when a record is first created. For example, your process checks whether an account description changes—ISCHANGED(\[Account\].Description)—and the process also reevaluates records multiple times in a single save operation. If an account is first created with a blank description value and another process updates the account description in the same save operation, ISCHANGED evaluates to true every time the record is reevaluated because it compares the account description value when the record was first created (a blank value) with whatever is set for the current value. Let’s say this same process creates a Chatter post every time ISCHANGED(\[Account\].Description) evaluates to true. This process would create a recursive loop resulting in six Chatter posts because ISCHANGED evaluates to true throughout the save operation.