Pages

09 March, 2014

Context Node and Attribute Properties

Hi,

I hope you all guys have looked on different standard UI elements of Webdynpro. If not Click Here

Today's post about most important concept Context Node and Attributes properties.

First of all let me tell you about Node and Attributes.

Node is something where you store the records. In other way Its like an Internal Table as in simple ABAP. So if you want manipulate with data you need a store place like Internal Table in ABAP. So Node is place where you can store the data/records so you can manipulate the data as you requirements.

And Attributes is something like variable which can be different data types. And Attributes hold the value for variables. Its like variable as in simple ABAP.

So now lets come to its properties.

Node Properties


So you can see in the above fig. There are different types Node properties. I will try to clear all properties of Node.

1. Node Name: When ever you create a node you have define Node Name. And its mandatory since in world every thing has name so Node as.

2. Interface Node: There are two possible value for this properties i.e "Yes" or "No". This properties of Node tells that you want make node as Interface. If you have choose "Yes" then this placed in Interface Controller so this node can be used in other Component as well.

3. Input Element (Ext): Through this property you can decide whether the new node should be available for an external mapping or not.

4. Dictionary Structure: If you want the fields / attributes from Table or Structure. Then give the name of that Table or Structure. And for adding the fields from Table Click on Button and select the required fields.
5.Cardinality: This properties is pair of values, which you can control the maximum and minimum number of elements at runtime i.e you can define the storage capacity of node as run time 
There are four possible values for Cardinality i.e
  • 0..1 : Node can store Minimum Zero Record or Maximum One Record at run time.
  • 1..1: Node can store exactly one record.
  • 0..N: Node can store Minimum Zero or Maximum n Record at run time.
  • 1..N: Node can store Minimum One or Maximum n Record at run time. 
6. Selection: Its like Cardinality, but its controls the maximum and minimum number of elements that may be selected at any one time. For example you have used Table UI element and If you want to select one row of table then define Selection property as 0..1 and if you want select the more than one row then you have to define the Selection property as 0..N.
And the possible values for Selection.
  • 0..1: i.e maximum you can select only one element or its also possible zero elements.
  • 1..1: i.e you can select the exactly one element.
  • 0..N: i.e maximum n elements or zero element
  • 1..N: i.e maximum n elements or at least one element.
7. Init. Lead Selection: At run time one of element of node has special position i.e is called Init. Lead Selection. This property tells you that whether the lead selection should be set automatically as soon as required.  Two possible values "Yes" or "No". The default value is "Yes".

8. Singleton: If you have created Nested Node i.e Node inside Node i.e Parent Node or Child Node. If you select the Singleton property of Child Node as "Yes" then there will be only one initiated of lead selection of Parent Node. If you define as "No" then there will be more than one initiated of lead selection of Parent node.

7. Supply Function: Its is special type of Function as node level. It is combinations with Singleton Property. If you have define the Supply Function for child node then you can capture the selected header record from parent node. Supply Function will triggered automatically when "Node is Empty" or "When you change the lead selection of Parent Node".
                   When you define the Supply Function for child node just double click on supply function then you will be able to see code which generated automatically. Here you have to write the Select query as you requirements.

Node Attributes Properties

There are different properties of Attribute

1. Attribute Name: Define the attribute name
2. Type assignment: Possible values "Type" or "Ref To"
3. Type: Assign the data type of attributes like int, String, or Elements etc..
4. Read Only: Set as "Yes" if you want to make it as Read Only
5. Default Value: Define the default value for Attribute.
6.Input Help Mode: Here you can define Input Help Mode as design time for Attributes. The possible values are
  • Automatic: It will show the automatic Input help mode of Attributes if you choose DDIC data element 
  • Deactivated: If you don't want to Input help the select this option.
  • Dictionary Search Help: If you want to Input Help from DDIC then choose this option. Give Search Help Name in Determined Input Help field
  • Object Value Selector: If you want to use OVS search help then choose this option and give the OVS component which used WDR_OVS component in OVS Component Usage field. 
  • Freely Programed: If you want to display the Webdynpro Component as Input Help which used the Interface IWD_VALUE_HELP then choose this option and give the name in Input Help Componet Usage field.


So today's post all about Node and Attribute properties. And I hope you guys will understand the properties of Node and Attributes. And it will be more clear once you practice as much as can.




Thanks and Yes don't forget to comment. :)



No comments:

Post a Comment