ºÚÁÏÕýÄÜÁ¿

Welcome to day one of the ºÚÁÏÕýÄÜÁ¿ 3.0 launch week! Over the next few days, we’ll be diving into a variety of exciting new developments, each designed to enhance the way you build and manage your apps. Each day, we’ll explore a different theme, offering insights and guidance to help you get the most out of ºÚÁÏÕýÄÜÁ¿ 3.0.

But let’s not get ahead of ourselves! We’re kicking off the week by diving into the new data experience in ºÚÁÏÕýÄÜÁ¿.

New data-first experience

Every great application starts with a strong foundation—its data. In ºÚÁÏÕýÄÜÁ¿, the Data section is your starting point for building powerful apps and lays the groundwork for everything that follows.

With this in mind, we’ve reimagined the data experience from the ground up, introducing five powerful features that make it faster and easier than ever to build secure workflow apps:

1. Enhanced Views
2. Default Values
3. Row Actions
4. View Joins
5. Dynamic Screen Generation

Control access with Enhanced Views

Controlling who can view, access, and manipulate data is crucial to building secure applications in ºÚÁÏÕýÄÜÁ¿.

That’s why with ºÚÁÏÕýÄÜÁ¿ 3.0, we’ve completely overhauled Views, making them the primary way permissions and access are defined in ºÚÁÏÕýÄÜÁ¿. You can now set up a new view for each role using your application, and seamlessly control what data they can see and manipulate.

By starting in the data section, we ensure a secure-by-design approach to managing access and permissions, making security step one in application development—not an afterthought.

For example, imagine a typical approval workflow with two roles: a Submitter and an Approver.

A Submitter should be able to:

• Create a new request.
• View, edit, and cancel their own requests.
• Not see other users’ requests or approve/reject requests.

An Approver should be able to:

• View all requests.
• Approve, reject, or cancel requests.
• Not see unsubmitted draft requests.

To keep things simple, we’ll just set up the Approver role for now, but we’d take the exact same approach for the Submitter role, too. The custom roles have already been created for this example, so let’s jump straight in and create a new Approver view.

Then, set the access level for the view to the Approver role.

We’ll set up a filter on our table to ensure that the Approver can only access requests to which they’ve been assigned. For this example, we’re checking that the Approver email column matches the email of the currently logged-in user to ºÚÁÏÕýÄÜÁ¿.

With Views, you can then customize and manage role permissions effortlessly. Use filters to control which rows each role has access to, or assign permissions to each column—edit, read-only, or hidden.

You can create as many Views as you want, which you can easily toggle between using the tabs above.

Previous to this release, View Access Configuration was a paid feature. With 3.0, this is now a free feature for all ºÚÁÏÕýÄÜÁ¿ users.

Set Default Values

Default values offer a streamlined experience for gathering data. You can set columns to a dynamic or static value when a new entry is created. For example, you can set the default value to In progress, Current employee, or the Date of a record’s submission. Default values eliminate the need for repetitive manual data entry, and ensure that information collected automatically is accurate and consistent.

Streamline data workflows with Row Actions

Row Actions link automations to your data, creating data-driven workflows that are both easy to set up and secure by design. This feature allows you to assign different actions to different users on the same dataset.

For example, in an approval workflow, an approver can Approve or Reject a request, while a submitter can Edit or Cancel it. This can be set up as four different row actions (aka automations), with each action only shown to the correct job role.

Let’s see how to set up the Approve action:

This targeted approach lets users take specific actions on a table, such as approving a request without full access to make unrestricted changes. By controlling user actions, ºÚÁÏÕýÄÜÁ¿ 3.0 enhances the usability and security of your applications, simplifying automation creation and role management.

Connect data with View Joins

View Joins allow you to display related data from other tables directly in your views, streamlining workflows, enhancing data visibility, and providing more ways to manage data security.

For instance, in an approval app, we might want to set up a relationship between the Requests and Approvers views. This way, using View Joins, we can easily pull in columns like the Approver’s name or email and show them directly in the Requests view without modifying your schema.

Related data, such as the employee’s name, is always view-only, preserving security while providing essential context. View Joins will also only display data from the immediately related table, keeping your views clean and manageable.

Dynamic Screen Generation

For our fifth and final feature today, we’re covering Dynamic Screen Generation.

You’ll now notice a new Generate button in your data section—this is where the magic happens. With the click of a button, generate fully-working apps and forms from the data you’re currently working with.

With just a click, generate screens from your Views and watch them come to life in seconds!

This is just the beginning

We hope you’ve enjoyed today’s release! As we’ve explored today, ºÚÁÏÕýÄÜÁ¿ 3.0 empowers you to build more secure, data-driven applications with ease.

From Dynamic Views that control role-based access to powerful new features like Automatic Screen Generation, the enhanced data experience streamlines app development and elevates what you can achieve with the platform.

Throughout the week, we’ll be unveiling more features that will transform your app-building journey. Tomorrow, we’ll explore Role-Based Access Control, reinforcing our commitment to secure-by-design app development.

Try out the new features above by logging into your ºÚÁÏÕýÄÜÁ¿ account or .