I agree, option A matches what Revenue Cloud expects. Using a screen flow with InitiateRenewal lets you control the user experience and put it right on the record page as a quick action. Apex or custom fields wouldn’t be as seamless here, I think.
Q: 11
A company is implementing Revenue Cloud to automate its subscription renewals. A Revenue Cloud
Consultant needs to configure the system to allow sales reps to initiate the renewal process for a
customer’s active assets directly from a record page.
Which component must the consultant implement to provide this one-click renewal capability?
Options
Discussion
Not B, A. The screen flow with InitiateRenewal as a quick action is what Salesforce wants for one-click renewals.
Its A here, I think. Screen flow with the InitiateRenewal action is pretty much the standard for one-click in Revenue Cloud. Apex or checkbox field feels overcomplicated for a rep-driven process. Open if someone’s done it differently.
A tbh, screen flow with InitiateRenewal as a quick action is the standard way for one-click renewals in Revenue Cloud. Triggers or checkbox/process setups are more for automation, not rep-driven. Pretty sure that's what Salesforce expects, but let me know if you’ve seen it done another way.
I feel like it's A, but not totally sure. Salesforce usually pushes flows with invocable actions for user-triggered stuff like this, and quick actions fit perfectly on record pages. B and C sound more automated or less flexible. Open to other opinions if someone did it differently.
A
Yeah, pretty sure it's A. The screen flow with InitiateRenewal is built for quick actions so reps can hit renew right from the page. Triggers or custom fields seem clunky for this use case-unless I’m missing something?
A
Makes sense to use a screen flow with the InitiateRenewal action for this. A
Be respectful. No spam.
Question 11 of 25