Forum Discussion

BlakeBurns1's avatar
BlakeBurns1
Qrew Trainee
6 months ago

Secure Link Redirect to Rich Text Page

Hello!

Trying to setup a Secure Link where an unregistered user clicks on a link in an email, is able to check a box to mark inventory delivered, and then save and close.

However, after saving and closing, I want to redirect them to a rich text page I've made, however any version of the link I try to use now prompts a 400 Error.

Now, this might have something to do with the fact the first link I sent myself on another, unlogged in browser, still works. Not sure why that would be.

First link, without any Rich Text redirect: https://axisseed.quickbase.com/db/bvhrw62s5?a=er&dfid=13&accesskey=57730592963ae9115a8b8d58de74bc518cf87f33cc94d58e01e4bce09d0ce6a8&rid=2

Second link: https://axisseed.quickbase.com/nav/app/bq78x5qrf/table/bvhrw62s5/action/er&dfid=13&accesskey=df46c3330a5aa235fadbcb34849f0e0dd4bfc7965208570684b9ef2153f77c3a&rid=21&rdr=https://axisseed.quickbase.com/db/bvhrw62s5?a=dbpage&pageID=20

The part I'd like to focus on is:

&rdr=https://axisseed.quickbase.com/db/bvhrw62s5?a=dbpage&pageID=20

Adding this string to the end of the first link still doesn't work, it just goes to an unlogged in front page.

Thanks in advance!

4 Replies

  • Denin's avatar
    Denin
    Qrew Captain

    I had this same issue before and there's a few things to consider such as encoding of the Url and the compatibility of rdr with secure links. But setting that aside, an easy solution is set the rich text page as home page for EOTI, and just redirect there as it pretty much does already.

    • BlakeBurns's avatar
      BlakeBurns
      Qrew Member

      Denin, I appreciate the reply. I was hoping to avoid doing that, as when I do that it shows that page to anyone not logged in, including myself and my users when we're signed out overnight.

      • Denin's avatar
        Denin
        Qrew Captain

        Thanks for the clarification. A more advanced approach could be to build the form in HTML and send the updated values as an API payload. This would allow you to control the submission logic with JavaScript, including redirecting users as needed. It’s definitely doable, but it may not be straightforward without development experience. There's an example of generating an HTML edit form here: Code Pages - AddEditRecordForm.html

  • 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.