Sample Pages and Best Practices

[satyaganti]

Can someone come up with best practices for each type of screens? Especially a Sample page would help newbees and non-developer like me to built after looking.

To start with: I am looking for the following:

1. search screen: Need to search customers with different parameters like first name, DOB, LastName, etc. and the results should be populated in grid or any other best option. The reason is I need to maintain/edit the information of customer after this. So there will be navigation link later.
2. I store CODES in DB instead of full decription. For example for SEX: Male/FEMALE I want to store M or F in DB. I maintain another table that gives be description of all these codes. I can join the tables and get value. But, What is best way to show description on screen but store short-VALUE in DB? I am looking for dropdown option.
3. Is it good to call the API directly on the field maping? How is it architected so that my API call is not exposed out in web?
4. May be better question… does all Workflow stay on server/backend or will be exposed to front end-website ?
5. How to do cascading dropdown i.e. selection of value in 1 dropdown populates value in 2nd drop down. For example if I select male in 1st DD, then I want Football,Hockey,Golf in the second drop down. Whereas when I select Female I want Sofbtall, swimming, skating in the 2nd
6. The list goes on and on.

I would be happy to have quick session to give some ideas.

I am looking for these in academy or docs.

[Joyce]

Hey @satyaganti

Great questions!

1. I’d suggest looking at our app templates and finding one that looks closest to the search screen you’re thinking of. Alternatively, you could work with Claude Design to think through this and wireframe a screen you like

2. The lookup and filterByKey formulas would be a good approach

3. I don’t understand the question.

4. If you create a workflow in the “Interface” tab, it’s a frontend workflow that’s exposed client-side. If you create a workflow in the “Data & API” tab, it’s a backend workflow that is NOT exposed client-side. You can use a frontend workflow to call a backend workflow. The details of the backend workflow will still not be exposed.

5. I’d suggest creating a separate topic for this with more details about how your database is structured and what you already tried.

6. We offer paid 1:1 coaching sessions here if you’d like to go through a bunch of similar questions. We also host free weekly office hours on YouTube

[satyaganti]

I am not able to find the backend workflow inside the front end workflow

1. Backend Workflow — Function

2. Backend W/F – Function not visible in the front end

3. Backend W/F – Function not visible in the backend-API-EndPoint

[jptrinh (Jean-Philippe Trinh)]

Hey @satyaganti

In the frontend, you have access to Backend endpoints by adding a new action → From Data & API

---

When you are in the backend workflows, you can call function the same way by adding a new action