This article explains the Get Data from Other App block that can be used to design an app.
Click on the block and start editing on the panel that appears on the right side.
This is what appears as the label for the dropdown that shows the list of the items from the master app. Usually people provide labels like "Select the customer/project/item".
Next step is to select the app from which the data will be fetched. You should get a dropdown of all the apps that are there in your Workplace. If you don't see anything then probably this is your first app. In such a case, you should create a master app first.
These are the fields that you need to show to the end users so that they can identify the item to be selected. For example, the app designer is setting Customer's Id and Customer's Name as selection field.
As an example, if there are the following entries in Customer Master -
Now while making a submission, if the user types "CLAP50 Dav", the first two entries will match the search text. If the user types "CLAP50 David", only the second entry will show up.
Here you select the items that will be pulled against the main selection made by the user. For example, if the user selects a Customer from the dropdown, all the details selected below will be fecthed against that customer.
Clappia allows admins to set status for each submission. It can be configured in the app designer configuration tab. You can set the status of each item in the master app and then fetch only those items that have a particular status. For example, you can set the statuses as Active/Inactive customer or Available/Unavailable (for inventory master).
This is optional and you should configure the status in the master app first to configure this.
Enable this option to tell the user that it is a compulsory field.
Enable this option to allow the users to be able to pull all the fields from the source app. If not, only the fields that have permission will be allowed to pull.
Enable this to allow the field value to be changed after submission
A custom message to show to the admin that there are no submissions found
Dynamic Filtering is a feature in GET DATA from other apps which is used to filter the fields and pull the data according to specific requirements.
Click on this option to add a dynamic filter. It opens up a menu to select the filtering items.
Let us understand the working of dynamic filter more clearly with an example
Dynamic filtering will help to view only those tickets that are assigned to the support employee. One employee can view, access or change the status of the tickets which are assigned to them and not of others.
There are 2 apps:
This is a list of tickets assigned to employees in the Assigning Tickets app.
Consider an employee ID and the tickets assigned only for that employee.
Employee ID - CLP0008
Ticket Number - sup_clp14 and sup_clp3
When you type the employee name, the respective employee details are fetched.
Next when you want to select tickets assigned to that employee it shows the list of all tickets.
Edit the app and click on the Ticket Number block which is GET DATA from other apps block.
Assigning Tickets is the app selected to pull fields from.
Employee ID is selected - this implies that ticket numbers assigned to the employee ID will be displayed.
Status update on tickets is the current app.
Employee ID is selected - this implies that the employee ID of the current app will match the employee ID of the app from which the data is pulled from. In this example it is the Assigning Tickets app.
Click on save and now let’s search for the tickets assigned to the employee again