What are the Child Records Widget Properties
Child Records Widget
Child Records widget and its properties can help you to add different forms in your single workflow.
For example—if you have created a workflow ‘Floor details’ earlier, then you can use that ‘Floor details’ workflow in your main workflow ‘Building Details.’ Here, your child workflow is ‘Floor Details’ & ‘Building Details’ is the parent workflow. When you design a ‘Building Details’ workflow, you don’t have to create fields multiple times like floor 1-meter information, floor 2-meter information, floor 3-meter information, floor 1 AC information, floor 2 AC information, floor 3 AC information etc. Just create a child workflow once, and you can add multiple records. (for floor 1, floor 2, etc.)
Child forms can cut the repetitive fields – all you have to do is create child workflow only once and add that in the main workflow. Using one child record workflow in your main workflow, you can add multiple entries. (Like multiple students’ information, etc.) So, while filling up the workflow, the user can just keep on adding floor details in the parent for without having to create multiple fields. Before using a child workflow in the main workflow, you will have to create one. Once you create that, go to the digital mobile screen in the middle – on the top of the screen, you will find a name of the workflow. If you click that, the properties on the right panel will show Parent Workflow. You can set the parent workflow here – which will be ‘Building Details.’
Now you have created a child workflow (Floor Details), and also set its parent workflow (Building Details). When you are designing the primary workflow, you can drag the ‘Child Forms’ or records widget properties from the left panel and drop that to digital mobile screen in the middle.
Child Records Widget Properties
You can set the child workflow by using this property. Just select the workflow that you have created as a child workflow. For example, you can set ‘Floor Details’ as the child workflow. Your current workflow ‘Building Details’ will be the main/primary workflow.
You can change the name of the ‘Child Records’ using a label property. It is ‘Children’ by default. On the right panel, go to the label section and you can type the required text that you want. The same name will appear on the workflow. For example, you can keep the label of your Child Workflow as ‘Floor Details.’
You can use this property to make that ‘Child Records’ mandatory to be filled. Some fields in your workflow might be mandatory, while some might not be.
For example, ‘Child Records’ field can be set to ‘Yes’ in the required property when you want to make the field mandatory. So, while filling out a workflow, the user will have to compulsorily add details in the Child Workflow while filling the mobile workflow, without which the workflow wouldn’t be submitted.
Every field will have a unique identifier. No two unique identifiers for fields will be the same. Please note that ‘Unique Identifier’ property is just for reference purpose only. The user need not have to do anything to this property. It can be referred when there are fields created with the same names. When you create two fields with the same names, it might get confusing when you are setting a condition and you wouldn’t know which field is which.
For example—if you have created a field ‘address’ – and set a visibility condition to it saying the ‘address’ field will be only visible if you have entered the ‘Phone number.’ But if there are two fields that say ‘Phone Number’ – it will be difficult to set a visibility condition since both the fields have the same name. Both of these fields ‘Phone Number’ will have different unique identifiers. You can check the unique identifier and then set the condition accordingly.
Visibility Condition in the property for the ‘Child Workflow’ is used to specify a condition. If you apply any visibility condition, it implies that the ‘Child Records’ will only be visible if it satisfies the condition that you have set. Visibility condition can be set by specifying the condition – you can do that by clicking ‘condition not specified.’
For example—you might create a child record ‘Floor Details’ which will be only visible if the user chooses ‘Yes’ option in the previous choice list ‘Are you capturing floor details?’ Visibility conditions can help you control the type of input during the filling of a workflow by the user.
Validity Condition in the property for the ‘Child Records’ is used to specify a condition. If you set any validity condition, it implies that the ‘Child Records’ will only be valid if it satisfies the condition that you have set. Validity condition can be set by specifying the condition. You can do that by clicking ‘condition not specified. For example, You might create a child records ‘Student attendance’ which will be only valid if the user enters ‘Student attendance’ in the earlier choice list ‘Choose Attendance.’ Otherwise, it would be invalid and show an error message. Validations can help you control the type of input during the filling of a workflow by the user. You can also customize an error message that you want to display by typing the message in ‘Validity Error Message.’
This message will be displayed when the validity condition does not match with the given input.
The error message could be “This is for student attendance only.”
Datamyte Digital Clipboard