Using a Page as a routing checkpoint page

#1

Hie @vishsahu
I am trying to set up a system where there is a way checking the status of a user in order to be able to send them to the correct page or show them the right modal… Instead of routing logic being scattered everywhere in the app, every incomplete user registration can be sent here. e.g. This page checks:

  • profile complete?
  • role selected?
  • verification needed?
  • verification pending?
  • approved?
  • what is next?
    So this is the page that will decide: e.g.
  • go finish registration
  • go submit verification
  • wait for approval
  • enter dashboard
    So what I am looking at is how to make such a page contain the different logic to achieve what i have just mentioned and more. This way i can just dedicate time to placing conditions that check each user as they log in. I will send them to this page, the user wont see it but the page will land them on the right page or resume a flow…

Thanks

#2

Hie @vishsahu
Please respond to this. Is it possible to have such a page which i can direct all users to when they log-in? A page that simply checks everything about the user and directs them to the right destination…

Thanks

#3

@WillieMak You can create a field called Stage or Step on which the user is and then use conditional redirect on the basis of the stage on which the user is.

Thanks.

1 Like
#4

Oooh. Thanks @vishsahu This looks like what I am looking for. Let me try and understand it fully. Will revert with further clarifications if needed

#5

Hie @vishsahu. Clarification on Conditional Redirect Limitations and Multi-Field Logic… I need clarification on how Conditional Redirects currently function, particularly around field type limitations and multi-condition sequencing. Please confirm whether Conditional Redirects only work with specific field types such as: Static option fields (Dropdowns, Radio buttons, etc.); System fields like Roles and Permissions. And do not support : Reference fields; Boolean fields (in some cases); Other dynamic/relational field types. Is this understanding correct?
Most of my routing logic depends on data stored in Reference fields (e.g., Role, Cluster, Purpose relationships). Since these cannot be directly used in Conditional Redirects:
What is the recommended approach to leverage reference-based data for redirects ?
Is the intended pattern to: Mirror reference values into static fields (e.g., text or dropdown)? Use intermediate/helper fields? Or handle this through another Drapcode mechanism entirely?
Conditional Redirects appear to operate one field at a time per event . In cases where routing depends on multiple fields working together , for example: Registration Stage; Role / Purpose; Verification Status.
How can we properly control execution order or priority ? Specifically: How are multiple conditional redirects evaluated when attached to the same event? Is there a way to enforce sequencing or hierarchy (e.g., Registration check → then Role → then Verification)? Or are all conditions evaluated independently without guaranteed order?
Given these constraints: What is the recommended best practice to implement a centralized routing system? Is using a dedicated routing page (decision hub) the correct approach in Drapcode? If yes, how should conditions be structured to avoid conflicts or race conditions? I am trying to design a single, reliable routing mechanism that: Uses structured user data (including references); Avoids duplication across multiple collections; Ensures predictable redirect behaviour. I would appreciate clear guidance on the intended architecture for this use case.

Thank you.

#6

Hi @WillieMak,

Conditional redirect only work for Static/Dynamic Option fields as of now.

Reference and other type of fields are not supported.

Thanks.