Attribute node has the following properties:
Attribute's name.
Attribute's description. Represents the caption of the textblock which will appear next to the attribute itself in the form if "Show description" property is True. In the example above attribute is PersonFirstName while its description is FirstName. So, 'FirstName' will appear next to PersonFirstName attribute, like we can appreciate below.
Specifies an icon or plain text type tag for attributes and variables. The property is visible only in View mode.
Represents a label that will be inserted next to the attribute if this property is not empty, in the same cell as it. The theme that will be assigned to this label will be taken from WWP Configuration -> Theme -> Att/Var Right text.
Specifies a description that will be displayed as a tooltip when positioning the mouse/cursor over the field, over the description or over a help icon next to the attribute (depending on the main configuration).
For example, if the configuration is set to show tooltip on values, it will look like the following image:
More information about this feature: Tooltip Help for attributes and variables
Specifies whether to generate the prompt rule in case this attribute belongs to some foreign key of the transaction. Only applies for attributes that are foreign keys to some other transaction. The value <default> will take its value from this property in WorkWithPlus Configuration -> Template.
If some Foreign Key is formed by two or more attributes, one of them must have this property on True so that WorkWithPlus adds the rule. Also, it is necessary that none of the attributes (FK or inferred) that are involved in the prompt rule have a manual Prompt (added as a child of that attribute).
For example, in Person transaction if we want the prompt rule for Company, we have to set this property on True for CompanyId (True or <default> when the default value is True):
And after saving, WorkWithPlus adds the rule:
Specifies a message that will be displayed in the attribute's field in order to describe what you should fulfill on it. When the end user starts to write something on the attribute, this message disappears. It is supported only when property 'Document type' property of the KB is HTML 5.
Example:
Specifies whether to generate links to other instances of the pattern through its description attributes. It only applies if the attribute we are modifying represents a description attribute of some transaction.
Example: Attribute CompanyName is Company's description attribute (and is an inferred attribute in Person). If we add this attribute into some table within TabGeneralPerson object, WorkWithPlus pattern will generate a link to the Company associated.
We run the application, and we go to visualize Person named John.
We can appreciate that a link has been generated to Company Name attribute. If we click this link, we will see information about the Company:
Attribute's theme class. If this field has an empty value the theme class that will be assigned to the attribute will be taken from WorkWithPlus Configuration > Theme node > properties Attribute, ReadOnlyAttribute and ReadOnlyBlobAttribute.
Description Theme class: theme class of the description of the attribute (textblock which will appear next to the attribute itself). In the example above attribute is PersonFirstName, and its description 'FirstName'. This property refers to FirstName's theme class.
Specifies whether the attribute will be visible on screen or not.
Specifies a condition so the variable would be visible only if that condition is verified.
Possible values:
- IP Address
- Thousand separator
- CPF
- CNPJ
- CPF or CNPJ
For more information visit Mask.
Specifies the appearance of the control when the page is loaded, before the condition is evaluated. The options are hidden or visible.
For example, if we want to see the the Hair Style attribute only if the Gender is a Female we should add the following condition:
By adding this condition, on runtime if 'Male' is selected the attribute Hair Style won't be visible:
If we select 'Female' the attribute will be visible:
If you want to read information about the Location in father table - description properties, follow this link: Location in father table
The properties inside this category refer to the variable's control type.
Specifies whether the variable will have a specific control type based on some domain/attribute, etc or will be defined customized. If you leave this property in its default value (based on) with empty value in 'Control info based on' property the control type of the variable will be the same as its definition.
Depending on the value of 'Control Info' property some properties are visible or hidden automatically.
Specifies the domain or attribute in which the variable's control info will be based on.
Specifies the conditions to be added to the control (only if the control is Dynamic Combo, Listbox or Suggest).
Specifies the attribute's control type.
Most of the options that GeneXus allows for control types are supported in this property:
Depending on the control type selected, other properties may appear. For instance, if the control type is Combo box, the properties Values and Empty Item will be visible.
The option "DVelop Combo" allows you to define a new kind of combo with advanced features. You can read more about this in the following link: DVelop Combo
Gives the option to assign specific properties to attributes, properties that are not available within the attribute node. This should be used in just a few cases. Detailed info: Custom Properties for Grid, Attributes and Variables
The properties within this category are only visible when the application has advanced security or is integrated with GAM Security.
Specifies the name of the permission that the attribute will have for defining whether that attribute will be editable for some role. If it is <default>, the value will be taken from the same property in the attribute's definition (explained below in the same page). If the value is empty, it won't add edit/read-only security to the attribute in this object.
Specifies the name of the permission that the attribute will have for defining whether that attribute will be visible for some role. If it is <default>, the value will be taken from the same property in the attribute's definition (explained below in the same page). If the value is empty, it won't add show/hide security to the attribute in this object.
It is important to have in mind that every time that we change some 'Security Functionality Key' and we want to impact these changes in the application at runtime, we have to follow the steps of the section Update Security Functionalities of Advanced Security or GAM (depending on the Security that we have enabled):
Then, at runtime, the administrator will configure the security of the attributes for each role, in the same way that he configures the whole application security (security for objects, modes of a transaction, etc).
Specifies whether the attribute will be required in the transaction or not. In other words, this property determines if user will be able to set an empty/null value to this attribute) or will be obliged to input some value when creating or modifying a record.
When the attribute is required (this property is True), it will look like different from attributes that are not required so that user at runtime could differentiate them. In order to do this, we set by default a specific theme class by default. Also, we create an error rule to ensure that this attribute has set some value when creating or updating a record.
The theme classes that we assign by default to required attributes and its descriptions are parameterized in WWP Configuration (Theme node, all properties within Required attributes category). So, by modifying this properties once in the Work With Plus Setting, all the required attributes that have their default value theme in the instance (empty field), will take their theme classes from this parameters.
When the property 'Is required' is True, the following properties appear:
:
If the 'Is Required' property is set to 'true' you can set a condition in order to specify when the attribute would be required or not.
For example, if we want the person Home Telephone Number to be required when the Cellphone Number is empty we should add the following condition:
Specifies the message that will be displayed when the end users leave the field empty. The value '<default>' will take the message from WorkWithPlus Settings à Labels à Required Attribute.
When the property value starts with and ends with the message will not be surrounded with " when inserting it in the rules, so that you can include variables and procedures in your error message. For example
Value of property: ""Home Address (" + &Pgmname + ") is required"" will insert the following rule: Error("Home Address (" + &Pgmname + ") is required") If PersonHomeAddres.IsEmpty();
Value of property: Home Address is required will insert the following rule: Error("Home Address is required") If PersonHomeAddres.IsEmpty();
Specifies whether to insert or not a NoAccept(<ATT>) rule assigned to the attribute within transaction object. The possible values for this property are the following:
- <default>: will have the same behavior as previous versions (adds the noaccept() rule only when the attribute is foreign key, and this rule has a condition)
- True: will add the NoAccept(<ATT>) rule without conditions, regardless of whether the attribute is foreign key or not.
- False: will not add the NoAccept() rule ever for that attribute.
There are some properties that do not belong to the attribute node (within some object), but they belong to the attribute itself. That is why WorkWithPlus adds some properties in the attribute's definition:
Specifies whether to use the Date Picker control or not. Only applies for attributes that are Date or Date Time. This property is also available on domains, and will be considered when you create a variable based on that attribute or domain.
Specifies whether the attribute will have edit/readOnly security enabled. If True, the administrator of the application at runtime will be able to determine which persons (that belong to some roles) will be able to edit the value of the attribute, and which won't.
Specifies the name of the permission that the attribute will have for defining whether that attribute will be editable for some role (the default values for both properties are taken from WorkWithPlus Configuration -> Security (Advanced Security or GAM + WorkWithPlus).
Specifies whether the attribute will have show/hide security enabled. If True, the administrator of the application at runtime will be able to determine which persons (that belong to some roles) will be able to visualize the value of the attribute, and which won't.
Specifies the name of the permission that the attribute will have for defining whether that attribute will be visible for some role (the default values for both properties are taken from WorkWithPlus Configuration -> Security ( Advanced Security or GAM + WorkWithPlus).
More info: Security in Attributes and Variables
|