I'm planning to change the data type of Account.Annual_Revenue__c from Number to Currency. I already have the References list. Walk me through the risk for each of these three components: the flow Account_Tier_Calculator, the validation rule Require_Revenue_on_Enterprise, and the formula field Account.Revenue_Bucket__c. What would break and how should I mitigate it?

I'm planning to delete the custom object Legacy_Task__c. I see 12 references in the References table. Look at the three flows that reference it (Legacy_Migration_Sync, Task_Rollup_Calculator, Legacy_Status_Updater) and rate the deletion risk of each as Low, Medium, or High.

I'm planning to change the API name of Opportunity.Legacy_Amount__c. From the References list, the flow Pipeline_Forecast_Calculator and the formula field Opportunity.Total_Value_Formula__c both reference it. Walk me through what each one does with this field and rate the rename risk as Low, Medium, or High.

Here are the record-triggered flows on the Opportunity object from the Data Dictionary: Stage_Change_Notification, Forecast_Roll_Up, Pipeline_Audit_Sync. For each one, show the trigger event (create, update, or both) and the entry criteria. Flag any flows that might conflict with each other or have overlapping logic.

Analyze the flow Case_Escalation_Process for optimization opportunities. Look for: unnecessary record lookups, SOQL queries that could be consolidated, decision elements that could be simplified, and any patterns that might cause governor limit issues in bulk operations.

Review the Apex class AccountService for best practices. Check for: bulkification issues, hardcoded IDs, missing null checks, SOQL queries inside loops, and proper error handling. List any issues found with the specific line or method.

Walk me through the trigger CaseTrigger step by step. What events does it fire on? What does it do in each context (before insert, after update, etc.)? Are there any potential issues with the current implementation?

Show me all workflow rules on the Opportunity object. For each one, list the evaluation criteria, rule criteria, and all associated actions (field updates, email alerts, outbound messages, tasks). Flag any that reference fields that have been deprecated or renamed.

Users are getting the error 'Close Date is required when Stage is Closed Won' on the Opportunity object, but they've filled in the Close Date field. What validation rules on Opportunity could be causing this? Check if there's a mismatch between the field API name in the validation rule and the field on the page layout.

The email alert Case_Escalation_Notification is not sending when cases are escalated. Trace the full chain: what triggers this alert, what conditions must be met, and what fields need to be populated? Check if the email template is active and if the recipient addresses are valid.

We want to consolidate the record types Subsidiary_A_Account and Subsidiary_B_Account into a single record type called Partner_Account. Analyze the differences between the two: different page layouts, picklist value availability, and profile assignments. Create a consolidation plan that preserves all necessary configurations.

Audit these four profiles, Standard_User, Sales_User, Sales_Manager, and Marketing_User. For each one, list the key permissions: Modify All Data, View All Data, Author Apex, Manage Users, and Customize Application. Flag any non-admin profiles that have these permissions, they may be overly permissive.

We want to implement a least-privilege permission model. Currently all users are on the Standard_User profile with various permission sets. Analyze the current setup and recommend a framework using permission set groups. Group permissions by role: Sales, Service, Marketing, and Admin.

Identify technical debt in this org: inactive flows that are still referenced, deprecated API versions in Apex classes, workflow rules that should be migrated to flows, and custom fields with 'Legacy' or 'Old' in their names.

We want to consolidate Legacy_Order__c into the standard Opportunity object. Create a migration plan that includes: which fields map to existing Opportunity fields, which fields need to be created as new custom fields on Opportunity, which automations need to be updated, and what the recommended sequence of changes is.

For the custom object Legacy_Order__c, I see 18 references in the References table. Walk me through the three flows that reference it (Legacy_Migration_Sync, Order_Rollup_Calculator, Legacy_Status_Updater) and rate the deprecation risk of each as Low, Medium, or High.

Based on our analysis, create a phased cleanup plan for the Account object. Phase 1: fields with zero references (safe to delete). Phase 2: fields referenced only by inactive components. Phase 3: fields referenced by active components that need migration. Include a recommended sequence for each phase.

I want to delete the following custom fields from Account: Legacy_Source__c, Old_Phone__c, Temp_Flag__c. For each field, confirm whether it's referenced by any active component. If it is, list the components and rate the risk of deletion as Low, Medium, or High.

I've identified 14 components that reference former.admin@previous-employer.com. For each one, [paste the list], recommend whether to update the email address, deactivate the component, or reassign ownership. Prioritize by business impact.

Analyze this org for migration complexity. Flag any components that would be difficult to migrate: heavily customized Apex, complex flows with many decision branches, custom integrations, and managed package dependencies. Rate each area as Low, Medium, or High complexity.

Document the Lead-to-Opportunity conversion process in this org. Include all flows, validation rules, assignment rules, and Apex triggers that fire during lead conversion. Describe the process in both technical and business-friendly language.

Hubbl flagged the Apex class AccountTriggerHandler as using API version 38.0. Explain what risks this poses and what would need to change if I update it to the current API version. Are there any dependencies I should be aware of?

Hubbl flagged 15 workflow rules that should be converted to flows. List them and for each one, rate the conversion complexity as Simple, Moderate, or Complex based on the number of actions and criteria involved.

Convert this business request into user stories with acceptance criteria: 'The sales team wants to track competitor information on each deal, including competitor name, their product, pricing, and our win/loss reason against them.' Generate user stories for each capability and include acceptance criteria for each.

Here are my discovery notes from a client meeting: [paste notes]. Convert these into a structured Business Requirements Document with sections for: Business Objective, Scope, Functional Requirements, Non-Functional Requirements, Assumptions, and Out of Scope items.

Here's a Jira ticket: 'Add a new field Account.Renewal_Risk_Score__c (picklist: Low/Medium/High). It should be visible on the Customer Account page layout, required for the Customer Success profile, and included in the Renewal Dashboard report.' Generate the full technical design including field creation, page layout update, field-level security, validation rule, and report modification.

Generate a solution design for this user story: 'As a sales manager, I want to receive an email notification when any Opportunity in my team's pipeline has been in the Negotiation stage for more than 14 days, so I can intervene before deals go stale.' Include which Salesforce components to create, the configuration details, and any existing components that should be reused.

Create a detailed technical design for a record-triggered flow that replaces the workflow rule Update_Case_Status_on_Escalation. Include the trigger conditions (object, when to run, entry criteria), all decision elements, and update actions. Make sure the flow handles the same logic as the original workflow rule.

Create a record-triggered flow that replaces the workflow rule Update_Case_Status_on_Escalation. The flow should trigger on Case records when a record is created or updated. Entry criteria: Status equals 'Escalated'. Action: Update the field Priority to 'High' and send an email alert to the case owner.

I need to modify the flow Lead Assignment and Routing. Before I make changes, show me: (1) what this flow currently does, (2) what other components reference or depend on it, and (3) any other flows on the Lead object that might conflict with my changes.

The flow Opportunity Stage Update is not firing when expected. Walk me through the entry criteria and every decision element. Identify any conditions that might prevent the flow from executing when an Opportunity moves from 'Proposal' to 'Negotiation'.

I want to rename the Opportunity Stage Proposal/Price Quote to Proposal Sent. From my References list, here are the three flows that look highest-risk: Stage_Change_Notification, Forecast_Roll_Up, and Pipeline_Audit_Sync. Walk me through what each one does with the stage value and rate the risk of the rename as Low, Medium, or High.

Create a step-by-step plan for renaming the Opportunity Stage Proposal/Price Quote to Proposal Sent. Include: which components need to be updated first, the correct sequence of changes, and what to test after each step. Account for the fact that some components may need to be deactivated during the transition.

Write a SOQL query that returns all Contacts where the Account's Industry is 'Technology' and the Contact's Title contains 'Director'. Include the Contact's Name, Email, Phone, Account Name, and Account Industry.

Write a SOQL query for the custom object Project__c that returns all projects where Status__c is 'Active' and the related Account's Type is 'Customer'. Include all custom fields on the Project object.

Generate an Apex test class for the trigger OpportunityTrigger. Cover all trigger events (before insert, after insert, before update, after update). Include test data setup, positive test cases, negative test cases, and bulk testing (200+ records). Use @testSetup for test data creation.

The Apex class AccountService has three methods: mergeAccounts, calculateHealthScore, and syncToExternalSystem. Generate test methods for each one. Include assertions that verify the expected outcomes.

Generate a comprehensive UAT test script for the flow Case_Escalation_Process. Include: (1) Happy path, case escalates correctly when criteria are met, (2) Negative path, case does NOT escalate when criteria are not met, (3) Edge cases, what happens when required fields are blank, when the case owner is inactive, or when the case is already escalated. Format each test case as a row in a table with columns: Test Case ID, Description, Pre-conditions, Steps, Expected Result, Pass/Fail.

I just modified the validation rule Require_Amount_on_Close on the Opportunity object. Generate a regression test script that verifies: (1) the validation still fires correctly, (2) existing workflows that depend on the Amount field still work, and (3) no unintended side effects on related automations.

The requirements document says we should have: (1) A custom field Account.Risk_Score__c, (2) A flow that auto-calculates the score nightly, (3) A dashboard showing accounts by risk tier, (4) Field-level security restricting the field to managers. Check which of these exist in the org and which are missing.

Verify that the flow Lead_Auto_Assignment matches these requirements: It should trigger on Lead creation, check the Lead Source and State fields, and assign to the correct regional queue. Compare the actual flow configuration against these requirements and flag any discrepancies.

I'm planning to deploy these three components to production: the flow Order_Submission_Handler, the Apex class OrderService, and the custom field Order__c.Priority__c. I've already checked the References tables. Based on what each one depends on, recommend a deployment sequence and flag any high-risk steps.

Create a post-deployment checklist for the components I just deployed: Order_Submission_Handler, OrderService, and Order__c.Priority__c. Include verification steps for each component: what to check, what records to test with, and what the expected behavior should be.

Document the complete Case management process in this org from creation to closure. Include: how Cases are created (web-to-case, email-to-case, manual), assignment rules, escalation logic, all automations that fire at each stage, and the closure process. Include both a technical description and a business-friendly summary.

I just completed a project that added a new Lead scoring system. Generate technical documentation that covers: all new components created (fields, flows, Apex), how they interact, configuration details, and dependencies. This will serve as the project's technical deliverable.

Document the Lead-to-Opportunity conversion process for our sales team. Explain when to convert a Lead, what fields map to the Account/Contact/Opportunity, and what happens automatically after conversion (any flows or automations that fire). Keep the language simple and business-friendly.

Generate content for a training presentation on our custom Salesforce reporting. Cover: how to find existing reports, how to create a new report, available report types, key filters, and how to schedule reports. Include talking points for each slide.