Hi All,
Here i have a issue, I have to give options to users to take different input details for 24 criteria's
1. when user selected 1st radio button - I have to take input from user for 1st criteria - Text interface input tool
2. when user selected 2nd radio button - i have to take different input details from user for 2nd criteria - same text input interface tool
when changing the criteria i cannot disable/enable interface tools based on 24 criteria, now how can i fix the issue to take different details.
Kindly suggest me
This is controlled in your interface designer where you layout your interface tools and nest them. You will need your interface tools themselves out of the containers. They attach into standard tools IN containers. so for example:
radio button
file input.
action tool
input data.
only input data is in the container. action tool has required file unchecked. interface designer nests the file input under the radio button.
@apathetichell Could you please help me with example I’m trying to build the logic which is not working for me when I’m going to second radio button I’m getting error
Were you able to figure this out? This post discusses the radio buttons, which may help.
https://www.bigmountainanalytics.com/open-and-close-containers-with-radio-buttons/
You can use the interface tool to nest your options into a tree structure. If this helps, feel free to like the comment
Hello @NiranjanK1,
If you are trying to enable/disable containers on your workflow, both radio buttons and checkboxes are ideal. Radio buttons enforce single select, check boxes allow for multiple selections. Please bear in mind that you cannot have interface tools inside disabled containers.
However, I believe the issue you are having relates to enabling/ disabling certain interface tools themselves, based on a radio button selection. If this is the case, your issue can be solved by using the Layout view in the Interface designer, like others have suggested. You can access the interface designer by going to View >Interface Designer. Below are some examples of how changing the interface designer affects your app interface.
For reference, here is the sample workflow I'm using:
Please note that for each radio button, I have the "Collapse Group When Deselected" option selected.
Default:
The default is to have all elements separately. We can see, that each interface tool is surrounded in its own separate box (I have highlighted one of these in the image below). This means that on the app interface, all options are present at all times:
Interface designer:
App View:
Custom:
Using the arrows within the interface designer, you can embed different elements so they are dependant on one another. For example, if you click on the text box once, then press the up arrow once, you interface designer window should look like this:
The key thing to note, is that the text box, is now inside another box, with the "Option Two Radio Button". From the front end of the app, the text box will now appear, only when the second radio button is selected.
Using this idea. you can effectively enable/ disable interface tools based on your selection in other interface tools.
I have attached the sample workflow below, please let me know how you get on.
Regards - Pilsner