[Add onboarding for new workspaces being created] Create new setup tasks when users create a workspace

[francoisl]

Part of the project "Adding onboarding for new workspaces being created"

Main issue: #48591
Doc section: https://docs.google.com/document/d/19u6ZQbNuF-v5oovIkQlmwYV4SXeAgey50pymsj5QHRY/edit?tab=t.0#heading=h.vwt3yefp8jmh (External only)

Feature Description

When a user who didn't choose the option "Manage my team's expenses" during the initial onboarding eventually creates a workspace, create onboarding tasks to teach them what to do next.

Implementation steps

1. Prep work:

   1. Add new constant newDotTrackWorkspace to backendOnboardingChoices - Design doc section
   2. Extract the logic to generate the request and optimistic data for onboarding tasks out of completeOnboarding(), for clarity and reusability – Design doc section

2. Create new setup tasks when users create a workspace

   • Design doc section ('External' section only)
   • Update CategorizeTrackedExpense, ShareTrackedExpense, and CreateWorkspace to generate and pass the new onboarding task data to the API if the user doesn't already have a createWorkspace onboarding task

[francoisl]

(Keeping internal because we're going to work with a C+ on this)

[mananjadhav]

Reviewed the design document. Will take another pass to see if there are any gaps. Will start with the implementation by tomorrow.

[mananjadhav]

@francoisl Is there anything pushed on the backend to start this?

[francoisl]

One part is deployed, another one won't be until at least tomorrow, and the tasks won't be saved until both parts are.

For now, the part 1 "Prep work" I described above shouldn't require any backend changes. Also, for step 2 we can start saving the task data in the optimistic data of the API request, and test it offline?

[francoisl]

@mananjadhav the backend changes for passing guidedSetupData and engagementChoice to the API commands CategorizeTrackedExpense, ShareTrackedExpense, and CreateWorkspace are now live. Let me know if anything is not working as expected.

[mananjadhav]

Okay thanks. I'll check those and reach out to you if any questions.

[mananjadhav]

Started with this, the PR will be up by tomorrow.

[melvin-bot]

@francoisl, @mananjadhav Whoops! This issue is 2 days overdue. Let's get this updated quick!

[mananjadhav]

I was out sick yesterday. I am half done, will finish this by weekend.

[anmurali]

@mananjadhav - do you have an update on this PR?

[melvin-bot]

@francoisl, @mananjadhav Huh... This is 4 days overdue. Who can take care of this?

[mananjadhav]

Apologies I was unwell. I am just getting back and will have this ready in 1-2 days.

[danielrvidal]

Thank you @mananjadhav, let us know if you need anything from our side!

[melvin-bot]

@francoisl, @mananjadhav Eep! 4 days overdue now. Issues have feelings too...

[mananjadhav]

PR work in progress. Will be raising the draft today.

[francoisl]

Sounds good, feel free to send it my way even if it's not fully ready, I can start taking a look and testing.

[melvin-bot]

@francoisl, @mananjadhav Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[anmurali]

@ishpaul777 have you gotten started with a PR?

[ishpaul777]

yes here it is -> #55017, sorry forgot to link issue