Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Member should not reach profile complete window without visiting pervious screen. #100

Open
drasticdpk opened this issue Nov 9, 2021 · 3 comments
Assignees
Labels
question Further information is requested

Comments

@drasticdpk
Copy link
Collaborator

Go to url https://platform.topcoder.com/onboard/complete

Reference

image

@rakibansary
Copy link
Contributor

rakibansary commented Nov 10, 2021

@vikasrohit this one's interesting. In normal flow we would never get to such a link. If we want to handle this, we need onboarding_checklist to be working. onboarding_checklist is the only sure fire way of knowing which step of the onboarding flow the user needs to resume from or if they've completed the onboarding flow.

Should we hold off on this one for now?

@rakibansary rakibansary added the question Further information is requested label Nov 10, 2021
@LCDuggan
Copy link

Let me see if I can clarify the user flow regarding the steps...
• We are not requiring any of the fields to be filled out to move forward.
• The user should only be able to use the "steps mechanism" (overlay element) to see what is coming ahead,
OR to move backwards. They should not be able to move forward to a step that has not been completed.
• Our messaging is to give positive reinforcement to the user for getting "through" Onboarding. They do not need to have completed their profile, or to have completed any of the input fields at all. If they have seen a step in onboarding, they have completed it even if they chose to move ahead without filling any information.
• There would be no time that a user should simply get to the Complete screen without having visited the Build My Profile screen.

Let me know if this helps or if you have other questions. Thanks!!

@vikasrohit
Copy link

@rakibansary I guess this happens only when the user manually enters the URL (https://platform.topcoder.com/onboard/complete) in the browser, right? If yes, I guess we can handle it later. I don't think people would be doing that as our flow is already permissive and it does not prevent any one to skip the flow.

As far as its solution is concerned, ye onboarding traits can be helpful there and they are working. Only catch is that they are async in nature and we can not guarantee that one would see the traits immediately after they completed the onboarding step. However, I think that does not matter to handle this case because we are concerned when a user randomly enters the deep link (https://platform.topcoder.com/onboard/complete) and current onboarding traits should help us there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants