AppForms

The TreeView Control in ClaySys AppForms

Akhil N P | Last Updated on : June 4, 2019

 ClaySys AppForms V 2.5


The Treeview control will allow the end users to create a menu of navigation to different forms. This new control can also invoke rules in the same form. This post is to explain the functionalities of the Treeview control.

Tree View Configuration

1. Drag the Tree View control under the Navigation option in Toolbox into the form.

NewItem34
2. Click on the Tree View control in the form and then click Properties.

NewItem33

3. Choose Data Source for Tree View item/s by clicking the icon NewItem32 under Data Source.

NewItem31

Tree View Static Data Source Configuration

1. Select Static and Click on OK button in Data Source window and the Tree View Configuration form opens. The Tree View Configuration form has the following fields.

  • Tree View Builder: The left pane in the window (marked Blue in the image) where nodes can be added.
  • Id: A unique Id for the Nodes added in the Tree View Area is assigned automatically.
  • Name: A meaningful string for the node created.
  • Is Separator: Not required for Tree View.
  • Image: An image can be added for the node added by clicking on the NewItem30 icon though the Image Viewer window that pops up.

NewItem29

  • Enable: The node added can be either enabled /disabled by choosing the checkbox.
  • Visible: A node added can be made visible /invisible by choosing the checkbox.
  • Sort Id: When there is more than one node available a positive number can be entered for the nodes according to which they will be ordered in the Tree View.
  • Navigation URL: To provide navigation to a form from a Tree View item choose Navigation URL by clicking NewItem28.

o   A NavigateURLChildWindow opens from which a form (destination form on clicking the tree view item) can be chosen.

NewItem27

o   Change Title: The name of the form can be changed by choosing this option.
o   Form Name: This drop down box has the name of the form chosen.
o   Field Name: This drop down box contains all the controls available in the form selected.
o   Result Field: This drop down box shows the fields available in the current form.
o   Add: Click on Add button to map the parameters from the parent form to child form.
o   OK: Click on OK button to create the form selected as the form to which the Tree View item is directed to.
o   Cancel: Click on Cancel button to cancel all the actions performed.
  • OK: Click on OK button to apply the changes made in the Tree View Configuration form.
  • Cancel: Click on Cancel button to cancel the changes made in the Tree View Configuration form.

2. To add a tree view item right click on the tree view area and select Add Root Node.

NewItem26
3. To add child node/s to the added Root node, right click on the Root node and choose Add Node.


NewItem25
The context menu of a node has the following options:
NewItem24

  • Cut Node: A node can be cut by choosing this option.
  • Cut Node Tree: When there is a node with child nodes right click on the parent node of the child nodes and select cut Node tree to cut the entire tree including parent and child nodes.
  • Copy Node: An individual node can be copied by choosing this option.
  • Copy Node Tree: To copy an entire tree consisting of parent and child nodes click on the parent node and choose copy tree.
  • Paste: Cut/Copied node/node trees can be pasted on the Tree View Builder using this option.
  • Delete Node: An individual node can be deleted by choosing this option.
  • Delete Node Tree: A tree consisting of parent and child nodes can be deleted using this option.

In the images below, three root nodes are created namely Home, File and View. The File node has four child nodes –New, Open, Save, Save As with images assigned to three of them. The Save As node has its Visible checkbox disabled as a result of which it is not seen in the Preview. The New node has its Enable check box unchecked and thus shown as disabled in Preview.

NewItem23

Tree View SQL Data Source Configuration


1. Select the required data source from the data source screen.

NewItem22
2. Select the table from where the data needs to be filled.

NewItem21
3. Select criteria if any.

NewItem20
4. Map the Id, Key, Text and Parent ID

NewItem19
a. Id should be mapped to the unique Id columns for the data which is related to the parent id column for its child control.
b. Key should be mapped to the column which is the value member for the tree view item. If this is not mapped then the Id is taken as the value member.
c. Text should be mapped to the column which is the display member for the tree view item.
d. Parent id should be mapped to the column having its parent id.
e. Now continue with the wizard and click Finish.

5. Now continue with the wizard and click Finish.

6. Once data is configured the tree view control will be populated with SQL data once we call FillData(TreeViewControlID) from rules.

Tree View SP Data Source Configuration

1. The SP configuration for tree view control is same as that of other group controls like ComboBox,CheckBox Group etc. Except for the column mapping screen shown below:

NewItem18
a. Id should be mapped to the unique Id columns for the result data which is related to the parent id column for its child control.
b. Key should be mapped to the column which is the value member for the tree view item. If this is not mapped then the Id is taken as the value member.
c. Text should be mapped to the column which is the display member for the tree view item.
d. Parent id should be mapped to the column having its parent id.

2. Once data is configured the tree view control will be populated with SP data once we call FillData(TreeViewControlID) from rules.

3. For SQL and SP the tree will be a simple tree without Image/Visible/Enable bindings compared to static data source.

NewItem17

HTML Preview: NewItem16

Tree View Event Handling


The Tree View click event can be handled using rules. If you want some actions to be performed on clicking a Tree View item the below steps would help you do so.

Create a rule with the Tree View control as the trigger.

NewItem15
As you can see from screenshots we are comparing the Node ID in the decision to check for which node the user have clicked.

NewItem14

Akhil N P
0 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Best Practices in ClaySys Appforms Configuration

2019-06-04 11:23:19