Forum Discussion
curevick
6 months agoQrew Cadet
You could handle this by embedding the secure link inside a Code Page (iframe) and letting the Code Page manage the post-submit experience.
I’ve done something similar before with a sort of 'log-in' workflow. The secure link handled the edit action for unauthenticated users, and the Code Page wrapped it so we could control what happened after save — including refreshing the page or displaying a confirmation message instead of relying on rdr.
Since rdr is unreliable (and often incompatible) with secure links, using a Code Page gives you full control over the UX without exposing a Rich Text page globally or changing the app’s home page.