Job application table: Getting started with Bubble (Lesson 6.5)

Section 6 (Lesson 5/9): In this lesson, we’re going to design the job application table to display jobs that the candidate has applied to. We’ll also set up a new data type called “Application,” which will be created when a candidate applies to a job.
We’ll be covering:
• Application data type: Setting up the fields required to capture all of the data necessary when a user applies for a job.
• Table refactoring: Redesigning a table that we created in the company dashboard to display the job application data.
Resources folder:
➡ e6387a14ba6d0b...
Bubble editor:
➡ bubble.io/page...
* * * *
Subscribe to this channel to be the first to hear about new videos!
Bubble is a software development platform that enables anyone to build and launch web applications without writing code. Rather than specializing in one or two aspects of web development (like designing landing pages or building databases), Bubble’s full-stack visual programming interface does it all. That means anyone from first-time entrepreneurs to enterprise-level companies can take an idea from concept to fully functional, scalable reality - faster and cheaper than you could with just code.
Have a question? Please visit bubble.io/support.
Learn more about Bubble:
Homepage ➡ bble.io/CCNpOg
Twitter ➡ / bubble
Blog ➡ bubble.io/blog

[@gobrandsprint]

So many hidden gems are scattered throughout the entire series! I wasn’t even aware of the distinction between link elements and text (link) elements from an SEO perspective.

[@gregory-john]

Nice! In Section 8, we're covering Technical SEO in a lot of detail.

[@gobrandsprint]

Excellent section ! The only part I'm uncertain is why set Candidate = Current User constraint, when privacy rule (once set) should take care of that.

[@gregory-john]

You ask such great questions! You are correct in your assumption about privacy rules protecting data. Regardless of this, we need to always construct our searches with constraints as well. There might be situations where rows are returned but fields are empty. There is also added risk when only relying on privacy rules. As your data type fields grow, mistakes can happen. The constraints provide that extra bit of safety.

[@bobdover9410]

I would normally opt to infer the Company data from the Job, rather than add a Company field to the Application data type. Is there a reason to do it like this (maybe Workload Units?) or was this just a design preference?

[@gregory-john]

It's for privacy reasons. Two parties need to access this data, 1. The candidate and 2. The company user. Therefore, they both need to be attached to the Application date type.

[@danieldah_music]

How can we login as a user to the preview in the demo app?

[@brianrios93]

User: username. Pass: password