Salesforce Plat-Admn-301 Dumps

Debug logs capture database operations, system processes, and errors that occur when executing a transaction or running unit tests. Debug logs can help identify the cause of Apex CPU time limit exceeded errors by showing the execution time of each Apex statement and trigger. References:

A validation rule and a stage guidance in Path are two features that can help ensure that users input a use case before moving the opportunity stage to qualified.

A validation rule is a formula that validates the data entered by users and prevents records from being saved if they do not meet certain criteria. In this case, a validation rule can be used to check if the Use Case field is blank when the Stage field is changed to Qualified, and display an error message if so.

A stage guidance in Path is a feature that displays helpful information or tips for each stage of a sales process on an opportunity record page. In this case, adding the Use Case field to the stage guidance in Path can remind users to fill out this field before moving to the next stage.

The change can be made through the desktop site by using the Edit All button on the related list of products on the opportunity page. This button allows you to edit multiple products at once and change their price book entries. You cannot use this button on the mobile app, as it is not supported. You also cannot change the price book on the opportunity once it has products added to it, unless you remove all the products first. References: &type=5 &type=5

To help the finance team use Opportunity data to keep an eye on their pipeline without manually calculating anticipated income for the quarter, the administrator should set up collaborative forecasting. Collaborative forecasting allows users to view quota against open pipeline and make adjustments based on changing business conditions. References: &type=5

A Text Area (Rich) field allows users to format the text with fonts, colors, images, and hyperlinks. It also supports mapping to an opportunity when converting a lead. References: &type=5

When deploying profiles using change sets, the field-level security settings are not included unless the fields themselves are also part of the change set. Therefore, the administrator should consider adding the new custom fields to change set 2 along with the profiles, or manually adjust the field-level security after deployment. References: &type=5

Debugging a flow allows administrators to test how a flow behaves before activating it or making changes to it. Debugging a flow runs it in real time using test data provided by the administrator or default values from the flow. However, debugging a flow also performs any actions defined in the flow, such as creating, updating, or deleting records. Therefore, if a flow has a delete element that deletes a record based on certain criteria, debugging the flow will delete the test record even if the flow is inactive. References: &type=5

A lookup relationship with Read/Write sharing setting is the recommended option to use when adding a field to Case Outcome custom object. A lookup relationship is a type of relationship that links two objects together and allows users to associate one record with another. A lookup relationship does not affect the security or deletion of either record and can be optional or required. In this case, you can create a lookup relationship field on Case Outcome object that references Case object and allows users to link multiple Case records to multiple Case Outcome records. You can also set the sharing setting for the lookup field to Read/Write, which means that users who have access to the parent record can also access and edit the child record. References: &type=5 &type=5

Two reasons why the user cannot find the Location object while using Data Loader are:

The label of Location may have been changed. The label of an object is the name that is displayed in the user interface and can be different from the API name that is used by Data Loader and other tools. If the label of Location has been changed to something else, such as Site or Venue, then the user may not be able to find it by searching for Location in Data Loader. The user should check the API name of the object in Object Manager or use the Describe Global operation in Data Loader to see all available objects and their labels.

The user’s profile needs create access to Location. The user’s profile determines what objects and fields they can access and what actions they can perform on them, such as creating, reading, updating, or deleting records. If the user’s profile does not have create access to Location, then they will not be able to load records into that object using Data Loader. The user should check their profile permissions in Setup or ask their administrator to grant them create access to Location.

The other two options are incorrect because:

Data Loader should only be used with standard objects is not a reason because Data Loader can be used with both standard and custom objects, as long as they are accessible and queryable via the API.

Location has a master-detail field to Account is not a reason because having a master-detail field does not prevent an object from being available in Data Loader, as long as it meets the other requirements such as accessibility and queryability.

An object-specific quick action is a type of action that allows users to do something in the context of a specific object, such as creating or updating a record, logging a call, sending an email, or launching a custom action. In this case, the administrator can create an object-specific quick action on the opportunity object that pre-populates certain fields with predefined values and allows users to quickly close an opportunity from the Salesforce mobile app. References: &type=5 &type=5

Person Account cannot be disabled is something that the administrator should consider before enabling Person Accounts. Person Accounts are a special type of accounts that allow storing information about individual people who are not associated with an organization or business account. Once Person Accounts are enabled, they cannot be disabled or removed from the org without contacting Salesforce support

Delegated administrators in Salesforce are designated users who are given limited administrative privileges to assist system administrators without having full access to all administrative functions. The two functions they can typically perform, which align with the permissions available to delegated admins, are:

Set up users and password management:

Delegated administrators can create and manage user accounts, which includes setting up new users, resetting passwords, and updating user details.

This is particularly useful for helping with user management tasks without providing full system administrator access.

Configure updates to sharing rules:

Delegated administrators can manage sharing rules within their specific groups or roles, which helps control access to records based on criteria set within the organization.

This level of access allows them to modify sharing rules to ensure appropriate data access without requiring full administrative control over all settings.

The other options listed are not within the scope of delegated administrator capabilities:

Manage custom objects and customize nearly every aspect: Delegated administrators do not have the ability to manage custom objects or perform extensive customization. These functions are reserved for system administrators with broader privileges.

Make updates to permission set configurations: Delegated administrators cannot create or modify permission sets. This is also restricted to full administrators, as it involves controlling access at a granular level across the org.

By utilizing delegated administrators for user and sharing rule management, organizations can maintain security and control while also sharing some administrative workload.

A flow is an automation tool that allows you to create processes that perform actions based on user input or record changes. A flow can be triggered by a user who launches it from a button, link, or Lightning page, or by the system when a record is created or updated. A flow has different versions that can be active or inactive. An active version is the one that runs when the flow is triggered, while an inactive version is the one that is saved but not running. When you deploy a flow to production with a change set, the flow version is deployed as inactive by default. This means that you need to activate the flow manually after deployment if you want it to run in production. References: &type=5 &type=5

Use Field-Level Security to control data access is how the administrator should deliver this solution. Field-Level Security is a way to restrict users’ access to view or edit specific fields on an object based on their profile or permission set. Field-Level Security can be used to make fields visible or hidden, and editable or read-only for different users. By using Field-Level Security, the administrator can ensure that only Marketing users can see all data on the Membership Details object, while Support users can only see the Support preference fields.

A custom summary formula is a formula that calculates values from summary fields in reports such as sums, averages, counts, etc. Custom summary formulas can use functions such as PREVGROUPVAL which returns the value of a field from the previous row at the same grouping level. By using a custom summary formula with the PREVGROUPVAL function, an administrator can create a report to calculate the year-over-year change in the dollar amount of a company’s opportunities by subtracting the amount from the previous year from the amount from the current year and dividing by the amount from the previous year. References: &type=5 &type=5

Bucket field is a feature that allows administrators to group report values into categories without changing the data in Salesforce. Bucket field can help simplify reports and charts by reducing the number of values displayed and summarizing data based on criteria such as ranges or groups. Bucket field can be used to group specific picklist values together into one of two lists

Change sets are tools that allow administrators to move customizations such as fields, page layouts, profiles, permission sets, etc. from one Salesforce org to another. To use change sets, administrators need to establish a deployment connection between a source org (such as a sandbox) and a target org (such as production). Then, administrators can create an outbound change set in the source org that contains the components they want to deploy, and upload it to the target org. In the target org, administrators can view and validate the inbound change set before deploying it to their org. References: &type=5

A summary report with a cross-filter is a type of report that allows you to summarize data by grouping rows and columns and applying filters based on related objects and fields. A cross-filter is a filter that lets you include or exclude records in your report based on related objects and their fields. In this case, you can create a summary report that includes a cross-filter to the Account object with a sub-filter for credit card number equal to null. This will show you all B2C accounts that are missing the credit card number, regardless of whether it is encrypted or not. References: &type=5 &type=5

IP ranges are settings that restrict login access to Salesforce from specific IP addresses. Administrators can set IP ranges at the org level or at the profile level. If a user tries to log in from an IP address that is outside the allowed range for their profile or their org, they will not be able to access Salesforce. Therefore, if a user started to work remotely and is having an issue logging in, it could be because they are not in the IP range for their profile or their org. References: &type=5

Chat must be routed with Omni-Channel in Lightning Experience because Omni-Channel is the only way to route chats to agents in Lightning Experience1. Chat can only be added to Console navigation Lightning apps because Chat is a console app feature and requires a console app with a console navigation style2. & &type=5

As explained in question 3, a price book is a list of products and their prices for a specific segment of customers or market. By creating a new price book for the U.K product pricing, Northern Trail Outfitters (NTO) can offer different prices for their products in the U.K market due to shipping and raw material cost differences. The price book can also specify which currency is used for the prices, such as pounds or euros. References: &type=5

An after save flow is a type of flow that runs in the background after a record is saved and performs actions based on the record data or changes. An after save flow does not require user input or interaction and can be triggered by a record-triggered flow element or by an Apex trigger. In this case, you can create an after save flow that runs when a case record is updated and delivers status update email to customers based on certain criteria or conditions. References: &type=5 &type=5

Configure one app per department and activate record pages for each app is how the administrator should ensure this is configured correctly. An app is a collection of items that work together to serve a particular function for a group of users. An app can include items such as tabs, objects, reports, dashboards, and record pages. A record page is a type of Lightning page that displays details about a specific record. A record page can be customized using Lightning App Builder and activated for different apps, profiles, or record types. By configuring one app per department and activating record pages for each app, the administrator can ensure that the backup team users can view records in a way that makes sense for each department depending on which app they are using.

When you have multiple record-triggered flows that are configured to run before the record is saved on the same object, the order of flow execution is unpredictable. This means that you cannot guarantee which flow will run first or last, or how they will affect each other’s field updates. Therefore, you should avoid creating multiple before-save flows on the same object and instead consolidate them into one flow if possible. References: &type=5

Case Source updates to ‘email’ before the record is saved because the Process Builder runs before the auto-response rule. Then, an email is sent out using Template2 because the auto-response rule evaluates the Case Source value after it is updated by the Process Builder and matches the criteria for Template2

A permission set is a collection of settings and permissions that give users access to various tools and functions in Salesforce. A permission set can be used to extend users’ functional access without changing their profiles. You can assign permission sets to individual users or groups of users based on their business needs. In this case, you can create a permission set with Read access to the Government ID field on the custom object and assign it to the Institutional Team users who need access to this field via reports. References: &type=5 &type=5

Manual sharing is a way of granting access to individual records by manually sharing them with other users, roles, or groups. Manual sharing can override the organization-wide default and role hierarchy settings and give additional access to specific records. In this case, manual sharing could be the reason why only one user can see the account record, even though they have the same profile and role as another user who cannot see it. References: &type=5

A managed package is a type of app that can be installed from the AppExchange. Managed packages are typically created by ISV partners or developers who want to distribute and sell applications that are upgradeable and have intellectual property protection. Before installing a managed package, an administrator should consider the following:

A) Custom objects and custom fields used by the app count against the org’s limits.

Managed packages may include custom objects and custom fields that are used by the app. These custom objects and custom fields count against the org’s limits and may affect the performance or functionality of the org. Administrators should review the components and requirements of the app before installing it and make sure they have enough space and resources for the app. References: &type=5

C) Apps may require certain Salesforce editions or features to be enabled.

Managed packages may require certain Salesforce editions or features to be enabled in order to work properly. For example, some apps may require Lightning Experience, API access, custom permissions, or specific user licenses. Administrators should check the app’s description and documentation before installing it and make sure they meet the prerequisites for the app. References: &type=5

D) Apps may require external, third-party web services to function properly.

Managed packages may require external, third-party web services to function properly. For example, some apps may integrate with other platforms or systems such as Google Maps, PayPal, or Twilio. Administrators should check the app’s description and documentation before installing it and make sure they understand the implications and costs of using external web services. References: &type=5

The field is being updated by a workflow field update is why records are being updated with data that violates the validation rule. A workflow field update is a way to automatically change the value of a field when a workflow rule evaluates to true. A workflow field update can bypass validation rules and other security controls when updating a field value, which can result in invalid data being stored in the record.

To ensure that sales reps’ managers can view records containing customer’s credit information but their colleagues cannot, NTO should grant access using hierarchies via the sharing settings. This option allows users above another user in the role hierarchy to have access to records owned by or shared with users below them in the hierarchy. References: &type=5

To review the performance of a Lightning record page, administrators can utilize two key tools:

Lightning Usage App:

The Lightning Usage App provides insights into user engagement and performance metrics for Lightning Experience.

Within this app, administrators can view specific metrics related to page load times and other performance factors.

This is a helpful resource for tracking usage and identifying potential issues with page speed or performance across the org.

Analyze Button:

The Analyze button is available within the Lightning App Builder when editing a Lightning record page.

By clicking this button, administrators can run a performance analysis on the page layout, which provides specific recommendations for optimizing page load times and improving overall user experience.

The tool evaluates components, their configuration, and potential sources of delay, giving direct feedback on areas to improve.

These two options directly provide performance analysis capabilities for Lightning record pages. The other options listed do not offer direct access to page performance metrics:

Activation Button is used for setting page visibility rules and activating a page, not for performance analysis.

Pages Menu helps in navigating and managing pages but does not provide performance metrics.

Using both the Lightning Usage App and the Analyze button allows administrators to comprehensively review and optimize Lightning page performance for improved user experience.

Data Loader is a tool that allows administrators to import or export large amounts of data (more than 50,000 records) from or to Salesforce using CSV files. Data Loader can be used for inserting, updating, deleting, upserting, exporting, or extracting data. Bulk API is an API that allows administrators to process large batches of records asynchronously in the background. Bulk API can handle millions of records with high performance and minimal system resources. By using Data Loader with Bulk API enabled, an administrator can import a large amount of historical data (more than 100,000 records) from another system efficiently and securely. References: &type=5 &type=5 &type=5

The fields that display in the details of the record page are controlled by the page layout assigned to the user’s profile and record type. The administrator can edit the page layout to add, remove, or reorder fields on the record page. References: &type=5

The equivalent field is the field that matches the dashboard filter field on the source report object. For example, if the dashboard filter is on Account Owner, then the equivalent field on the Opportunity object is Opportunity Owner. Changing the equivalent field ensures that the dashboard filter applies correctly to the Opportunity components. References: &type=5

Territory management is a feature that allows you to grant access to accounts and opportunities based on criteria such as geography, industry, product line, or customer size. A territory is a grouping of accounts and users that represents a market segment or business unit. In this case, the administrator should utilize territory management to add the operations team to the East territory, which contains all the accounts and opportunities in the East region. This way, the operations team members can access all the records in their territory regardless of who owns them or what the organization-wide default is. References: &type=5 &type=5

The data masking tool is a tool that allows you to mask sensitive data in your full sandbox by replacing it with fictitious data. This can help you protect your data privacy and comply with regulations while testing in a realistic environment. You can use the data masking tool to mask data for standard and custom objects, including person accounts, and choose from different masking formats and options. References: &type=5

Run the standard Data Classification report is what the administrator should recommend to the compliance team. Data Classification is a feature that allows administrators to flag where sensitive information is stored in Salesforce by assigning sensitivity and classification levels to fields. Data Classification also provides a standard report that shows field level sensitivity and classification for all fields in an org. The administrator can run this report and share it with the compliance team to meet their requirement. 

A price book is a list of products and their prices that can be added to an opportunity. A product can have different prices for different markets or segments, and these prices are stored in different price books. In this case, the administrator should create a new price book for the new retail pricing and add the products that are sold to retail locations for resale. This way, the users can select the appropriate price book and products for their opportunities based on the type of customer they are selling to. References: &type=5 &type=5

record types allow administrators to offer different business processes, picklist values, and page layouts to different users based on their profiles. By using record types for accounts and contacts at AW Computing, administrators can track their accounts and competitors on different record types with different fields on their page layouts. For partner accounts, they can also use record types to specify different values in the Industry picklist field. References: &type=5

Force logout on session timeout is the recommended security setting to configure because it prevents users from resuming their sessions after they time out due to inactivity, which reduces the risk of unauthorized access to Salesforce data from unattended devices. References: &type=5

Changing the field type to a Lookup Relationship will allow deleting the Relationship field without deleting the Runners records. A lookup relationship creates a loose association between two objects, where the child records do not depend on the parent records for their existence. A lookup relationship can be deleted without affecting the child records, unlike a master-detail relationship that enforces cascading deletes. References: &type=5

Use an Insert operation to load data because the data is not already in Salesforce and does not need to be updated or deleted3. Map an External ID data value to the object because External IDs are used to create relationships between records that are being imported and records that already exist in Salesforce4. & &type=5

Two practices that the administrator should adhere to in order to ensure a successful deployment to production are:

Add permissions and access settings to outbound change sets in addition to the dependent component list. This can help avoid deployment errors or access issues caused by missing permissions or settings for the components in the change set. For example, if the change set includes a new custom object, the administrator should also include the object permissions, field-level security, page layouts, and record types for that object.

Run deployment validations on the change set in the sandbox prior to uploading to production. This can help test the change set for any errors or conflicts before deploying it to production. Deployment validations simulate the deployment without actually making any changes and report any issues or warnings.

The other two options are incorrect because:

Cloning a change set does not add forgotten dependent components to an uploaded change set. It only creates a copy of the existing change set that can be modified before uploading.

When deploying a new record type, it is not necessary to have it as the only component in the change set. It can be deployed along with other components as long as they are compatible and have the required dependencies.

Data Import Wizard is a tool that allows administrators to import data for standard and custom objects in Salesforce using CSV files. Data Import Wizard can handle up to 50,000 records at a time and supports simple data transformations and validations. Data Import Wizard can be used to upload records for a custom object when the number of records is small and the import frequency is low.

Flows are tools that automate business processes by collecting data and performing actions in your org or an external system. Flows can be triggered by various events such as record creation, updates, or invocations from other processes or flows. Flows can also send email alerts as part of their actions. To send a notification when a record is deleted and by whom, and to maintain their own discovery information, an administrator can use a flow that runs when a record is deleted, queries the record owner’s email address and discovery information from another object or variable, and sends an email alert with those details. References: &type=5

A validation rule can enforce data quality by preventing users from saving records that do not meet certain criteria. In this case, the validation rule can check if both the Sales Engineer and the Account Executive lookup fields are blank, and display an error message if so. This way, the director of sales can ensure that every opportunity has either a sales engineer or an account executive assigned to the deal. References: &type=5

A matching rule is a rule that defines how records are compared for duplication based on certain fields or fuzzy logic. By including more fields or changing the matching method, you can make the matching rule more or less strict and reduce false positives or negatives. In this case, including the email field to the existing matching rule for contacts can help avoid duplicate messages for common names by checking if the email addresses are also identical. References: &type=5 &type=5

The Setup Audit Trail is a tool that allows you to view and download a log of changes made in your org’s Setup area. The log shows up to 20 fields of information for each change, such as who made it, when it was made, what type of change it was, and what values were changed. You can use the Setup Audit Trail to track configuration changes directly in production and identify any unauthorized or problematic changes. One of the changes that the Setup Audit Trail tracks is when a user’s profile is changed and who changed it. This means that you can use the Setup Audit Trail to see when a user’s profile has been changed and who changed the data. References: &type=5

A cross-filter lets you filter records based on related objects and their fields. For example, you can filter accounts that have at least one opportunity from this year and at least one completed activity in the last 30 days. References: &type=5

The Delete permission is missing on the user for Accounts is what is preventing the user from completing the merge. Merging accounts is a way to combine up to three duplicate accounts into one master record and update the related records accordingly. Merging accounts requires the Delete permission on accounts because merging accounts involves deleting the duplicate records and keeping only the master record.

Displaying the related contacts related list and adding the direct field will allow users to distinguish between contacts and related contacts. The related contacts related list shows all contacts that are related to an account, either directly or indirectly. The direct field indicates whether a contact is directly associated with an account or not. By adding this field to the related list, users can easily see which contacts are direct and which are not. References: &type=5 &type=5

Contacts to Multiple Accounts is a feature that allows administrators to relate a contact to multiple accounts without creating duplicate contacts for each account. This feature is useful for scenarios where a contact has business relationships with more than one account, such as consultants, brokers, or loan advisors. By setting up Contacts to Multiple Accounts for loan advisors at DreamHouse Realty, administrators can track which loan advisors work with which customers and which accounts without creating duplicate contacts for each account. References: &type=5

To help ensure that users who are viewing reports and dashboards are who they say they are, DR should require a high assurance session when exporting or printing reports and dashboards. A high assurance session requires users to verify their identity using multi-factor authentication before accessing sensitive data or functionality in Salesforce. References: &type=5

 Omni-Channel is a feature that allows service reps to receive work assignments based on their availability, capacity, and skills. It also allows administrators to define routing rules and priorities for different types of work items, such as cases, chats, or leads. Omni-Channel can help reduce the wait time for customers and improve the efficiency of service reps.

To access a junction object record, a user needs to have at least read permission on one of its master records and on the junction object itself. If the user does not have access to either master record, they cannot access the junction object record. If the user has access to both master records, they can access the junction object record with the most permissive access level of either master record. References: &type=5 &type=5

A permission set is a collection of settings and permissions that can extend users’ functional access without changing their profiles. By creating a permission set with view All on Accounts and assigning it to the service and sales managers, an administrator can grant them access to all account records in their org without modifying their existing profiles. References: &type=5

Delegated Administration allows administrators to delegate certain user management tasks to non-administrators. For example, a delegated administrator can assign permissions sets to users in specified roles or public groups without having full access to modify permission sets. References: &type=5

Login Forensics is a Salesforce feature that allows you to monitor and analyze login behavior and trends in your org. It can help you identify and prevent brute-force password attacks by showing you the number of login attempts, successes, and failures per user, location, and device. You can also set up alerts to notify you when a user exceeds a certain number of login failures or when a login originates from an unusual location or device. References: &type=5 &type=5

The resume event is recalculated and the email goes out to the account owner immediately because the flow uses a scheduled path that evaluates the expiration date field every time it changes. When the expiration date is changed to yesterday, the flow resumes immediately and executes the action of sending the email

To grant access for the sales rep who broke their phone and needs multi-factor authentication using Salesforce Authenticator app, the administrator can generate a temporary identity verification code for them. This code allows users who don’t have their verification method available to log in securely without compromising their account security. References: &type=5

A record type allows administrators to offer different business processes, picklist values, and page layouts to different users based on their profiles. By creating a record type for the type of property (single-family home or condo), DreamHouse Realty can assign different page layouts to each record type that display only relevant fields for each property type. The record type can also determine which sales process and path are available for each opportunity. References: &type=5

Three reasons CK should utilize Data Categories when creating articles in Knowledge are:

Data Categories help organize the Knowledge base content displayed. Data categories are logical groupings of articles that reflect your business needs and processes. You can create a data category group and assign it to one or more article types, and then create data categories and subcategories within that group. Data categories help you organize your articles by topic or criteria and make them easier to find and browse by your users or customers.

Data Categories provide a way to secure access to the Knowledge base content. Data category visibility is a setting that determines which data categories users can access based on their profiles or permission sets. You can use data category visibility to control access to your articles based on their data categories and ensure that only relevant and appropriate content is displayed to different users or customers.

A Knowledge article can be tagged to more than one Data Category. A Knowledge article is a document that provides information or answers to common questions or issues. A Knowledge article can be tagged to one or more data categories within each data category group that is assigned to its article type. This allows you to classify your articles by multiple criteria and make them searchable and accessible by different users or customers.

Data Classification is the feature that the administrator should use to flag where sensitive information is stored in Salesforce. Data Classification is a feature that allows administrators to flag where sensitive information is stored in Salesforce by assigning sensitivity and classification levels to fields. Data Classification can help administrators comply with data privacy regulations and best practices by identifying and managing sensitive data in their orgs.

Three recommendations that the administrator can make to reduce the file size of full data exports are:

Reduce the amount of objects per export. By selecting only the objects that are necessary for the backup and excluding the ones that are not, you can reduce the number of files and records that are exported and decrease the file size.

Deselect ‘Include images, documents, and attachments’ in the export. By unchecking this option, you can exclude the files that are stored in Salesforce as images, documents, or attachments from the export. These files can take up a lot of space and increase the file size significantly.

Keep deleted record counts to a minimum. By emptying the recycle bin regularly or using hard delete options, you can reduce the number of deleted records that are included in the export. Deleted records are still counted as part of the export limit and can increase the file size.

The other two options are incorrect because:

Requesting a backup file every 5 days does not reduce the file size of each export. It only increases the frequency of exports and may cause more storage issues.

Unselecting the recycle bin in the object export option does not reduce the file size of full data exports. It only applies to individual object exports and not to weekly or monthly exports.

One possible reason for the changes to case routing is the difference in the order of execution between before save flow triggers and workflow rules. Before save flow triggers run before assignment rules, which means that any field updates made by the flow can affect how the assignment rules assign the case. Workflow rules run after assignment rules, which means that any field updates made by the workflow do not affect how the assignment rules assign the case. Therefore, replacing workflow rules with before save flow triggers can change the case routing logic. References: &type=5 &type=5