◆ Salesforce

Reduce large internal view state

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 taskReduce the view state of the 'OpportunityDetail' Visualforce page by 30% so it loads faster for…+
Reduce the view state of the 'OpportunityDetail' Visualforce page by 30% so it loads faster for sales reps.
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 acceptBefore the end-of-quarter push, analyze the 'OpportunityDetail' Visualforce page. Identify the…+
Before the end-of-quarter push, analyze the 'OpportunityDetail' Visualforce page. Identify the components contributing most to its large view state and suggest specific changes to reduce it, so our sales reps don't get performance errors when updating deals under pressure.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA sales rep just reported the 'OpportunityDetail' page crashed while they were trying to update…+
The 'OpportunityDetail' page crashed for a sales rep trying to close a deal.
A sales rep just reported the 'OpportunityDetail' page crashed while they were trying to update a critical deal before the 5 PM deadline. I'm afraid this could cause them to miss their quota and impact the team's month-end numbers. I can't tell if it's a specific user's data, a general view state issue, or something else. What's the likely diagnosis for this page crash, and what's the best next move to prevent it from happening again, especially with quarter-end approaching?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur Visualforce pages frequently hit view state limits, leading to errors and frustrated sales…+
Our Visualforce pages keep hitting view state limits, causing errors and user frustration.
Our Visualforce pages frequently hit view state limits, leading to errors and frustrated sales reps, especially during peak usage. I keep losing time reacting to these emergencies instead of building stable applications. What habit should I change to proactively manage and reduce view state in our Visualforce pages, ensuring they remain performant and reliable?
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.