◆ Salesforce

Pass parameter to Apex method

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWhen the 'Calculate Commission' flow runs, pass the Opportunity ID from the current record into…+
When the 'Calculate Commission' flow runs, pass the Opportunity ID from the current record into the Apex method 'CommissionCalculator.calculate' so it knows which opportunity to process.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptThe 'Calculate Commission' flow is failing intermittently, and I suspect it's not always…+
The 'Calculate Commission' flow is failing intermittently, and I suspect it's not always getting the correct Opportunity ID when it calls the Apex method. Review how the Opportunity ID is passed from the flow to the Apex method, and make sure it's robustly sending the right ID every time, even if the flow is triggered from different contexts.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'Update Inventory' flow just failed for a new order, and the error message points to the…+
The 'Update Inventory' flow just failed for a new order, and the error message points to the Apex method 'InventoryManager.updateStock' not receiving a valid Product ID. I'm worried this order won't ship on time. I don't know if the flow isn't sending it, or if the Apex method is expecting a different format. What's the quickest way to confirm what parameter the flow is actually passing to the Apex method and get this order processed?
The 'Update Inventory' flow just failed for a new order, and the error message points to the Apex method 'InventoryManager.updateStock' not receiving a valid Product ID. I'm worried this order won't ship on time. I don't know if the flow isn't sending it, or if the Apex method is expecting a different format. What's the quickest way to confirm what parameter the flow is actually passing to the Apex method and get this order processed?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternFlows frequently fail when calling Apex methods because the parameters aren't passed correctly,…+
Flows frequently fail when calling Apex methods because the parameters aren't passed correctly, leading to debugging headaches and delays.
Flows frequently fail when calling Apex methods because the parameters aren't passed correctly, leading to debugging headaches and delays. This often happens with new integrations or when an Apex method's signature changes. What habit should I change in how I design the parameter passing between flows and Apex to reduce these errors and ensure reliable execution?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.