Course Content
Apps – Expert
0/8
UI Logic – AI App Builder
00:00
Events – Conditional logic – AI App Builder
00:00
Variables – AI App Builder
00:00
Tables – AI App Builder
00:00
Modals – AI App Builder
00:00
Address Finder – AI App Builder
00:00
Kanban – AI App Builder
00:00
Course Exercise: Build a Secure Salesforce Customer Portal with OTP – AI App Builder
00:00
Apps – Expert

Lesson: Conditional App Logic Based on User Input

Forms become significantly more intelligent when they don’t just change visually, but actually alter how your application processes data behind the scenes. In this lesson, you will learn how to configure Conditional Logic within your app’s button event handlers. This allows your app to dynamically switch backend execution paths based on user input—routing “Personal” sign-ups down one pipeline while spinning up full enterprise account structures for “Business” selections.

Why Conditional App Routing Matters

Not all user submissions are created equal. A customer registering as an individual should not be processed the same way as an enterprise client. By embedding conditional logic directly into your app’s button triggers, you can split your application’s data pipeline into separate, specialized pathways, ensuring records are structured correctly in your CRM automatically.

Step 1: Locate the Submission Event Trigger

  1. Open your Contact Us page inside the Noca Web Builder workspace.

  2. Open the Events panel from the top-right toolbar.

  3. Locate the interactive button element row labeled On Click “Send Message”.

  4. Click the Plus (+) icon to open a clean Noca Flows canvas tied directly to this button interface.

Step 2: Add a Logic Condition to the App Flow

  1. Click the Plus (+) node block directly following your initial app action trigger.

  2. Select Logic from the options menu, and choose Condition.

  3. This block acts as a sorting gate right inside your app’s processing engine, splitting your workflow paths based on what the user chose on the page.

Step 3: Define the Condition Mapping Rules

Configure the condition block to evaluate the user’s form selection:

  1. Open the condition properties and target your Client Type dropdown element.

  2. Set up Rule 1: If Client Type Selected Value is Equal to... Personal.

  3. Add a secondary branching rule row targeting the same dropdown element: If Client Type Selected Value is Equal to... Business.

  4. Label your split pathways clearly as Personal and Business to keep your canvas clean.

Step 4: Map the “Personal” App Pathway

If the application detects the user selected the “Personal” option, execute a streamlined record setup:

  1. Drag a Salesforce Create Object node onto the Personal logic branch. Set the target object to Contact.

  2. Link the form inputs from the left-side Data Kit directory (First Name, Last Name, Email, Phone Number) straight to the matching Salesforce Contact properties.

  3. Append a secondary Salesforce Create Object node immediately downstream. Set this target object to Case.

  4. Map the form’s Message input box to the Case Description field, and map the Contact ID using the automated reference variable generated by the preceding step.

Step 5: Map the “Business” App Pathway

If the app detects the user selected the “Business” option instead, configure it to build a more complex, relational hierarchy:

  1. Drag a Salesforce Create Object node onto the Business branch. Set the target object to Account.

  2. Map your form’s conditional Company Name text input to the Salesforce Account Name property.

  3. Add a subsequent Salesforce Create Object node to generate a Contact. Connect the standard user fields, but crucially, map the Account ID to the ID generated by the preceding Account creation step.

  4. Add a final Salesforce Create Object node downstream to create a Case, automatically tying the issue ticket back to the parent Account ID and mapping the Description from the user’s message.

Step 6: Go Live and Run a Multi-Path Audit

  1. Toggle the logic workspace switch to Go Live and click Save inside the main page builder window to compile the updated click listeners.

  2. Click Preview App to open the simulator and test both distinct app paths:

    • Path Audit A (Personal): Fill out the form fields, select Personal, type a message, and click send.

    • Path Audit B (Business): Click send another message, fill out the form, select Business, fill out the newly appeared Company Name field, and hit send.

  3. Open your Salesforce dashboard. Verify that the “Personal” submission created a standalone contact with an attached case, while the “Business” submission automatically generated a fresh Account entity, holding both the contact and case records completely nested inside it!

Previous
Next