Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Enter a culture string to use as the display name of the field in the Display Culture String field if you want to localize this field name on a user-by-user basis (based on a user's assigned Culture). See Localization in the Admin Guide for details.

Linked Entity

...

  • Email: Fields with this extended type provide the functionality to automatically create a new email message. An email icon appears to the right of a field that uses this extended type. When the icon is clicked, Aptify opens a new mail message and inserts the email address contained in the field as the message's To field.
  • Fax: This type specifies that the field contains a fax number.
  • Phone: This type specifies that the field contains a phone number.
  • Area Code: This type specifies that the field contains an area code.
  • CountryCode: This type specifies that the field contains a country code.
  • WebURL: Fields with this extended type are created to hold URLs for web pages. The button to the right of these fields allows the user to go directly to the web page listed. Note that the specified URL must be in the proper format to successfully open a Web browser when this button is clicked (for example, the address should be in the format of http:
    www.aptify.com
    or www.aptify.com). 

    WebURL Field ExampleImage Modified
  • EXE: This type specifies that the field contains an executable file name.
  • City: This type specifies that the field contains a city. This field may be automatically populated when a user enters a ZIP Code in a ZIP Code field in the same entity.
  • State: This type specifies that the field contains a State. This field may be automatically populated when a user enters a ZIP Code in a ZIP Code field in the same entity.
  • ZipCode: This type specifies that the field contains a ZIP Code. When a user enters a ZIP Code in a field of this type, the system automatically populates other address fields in the same entity.
  • Country: This type specifies that the field contains a country. This field may be automatically populated when a user enters a ZIP Code in a ZIP Code field in the same entity.
  • County: This type specifies that the field contains a county. This field may be automatically populated when a user enters a ZIP Code in a ZIP Code field in the same entity.
  • USCongress: This type specifies that the field identifies an address's US Congressional district.
  • Repository Object: Fields defined with this extended type store the names of objects from the Object Repository. A button to the right of the field allows the user to select the object from the Object Repository.

    Repository Object Field ExampleImage Modified
  • File: Fields defined with the extended type of File include a page button that opens the Select File dialog, allowing the user to populate the field with the directory path of the selected file.

    File Field ExampleImage Modified
  • Folder:  Fields defined with the extended type of Folder include a folder button that opens the Browse for Folder dialog, allowing the user to select a folder location on the network or location computer. A user can also create new folder from this dialog. 

    Folder Field ExampleImage Modified
  • Password:Fields defined with the extended type of Password displays a series of asterisks on a form rather than plain text. This is designed to mask the password to prevent authorized access. Note that following when working with a password field:
    • The Password extended type functionality is only applicable for a Text Field. If your field's size is greater than 255 characters, the Aptify Baseline Form Template Generator will create a multi-line text field that displays the field's contents in plain text. In this case, use the Visual Designer to remove the multi-line text field and replace it with a text field that uses the Password extended type. See Modifying Field Layout with the Visual Designer in the Admin Guide for information on the Visual Designer.
    • Even though a Password field's value is masked on the form, the value will still show up as plain text within a view. Therefore, to adequately protect passwords, Aptify recommends that you encrypt any Password fields that you add to the system in addition to setting the Extended Type to Password. See Field Level Encryption for information on encrypting a field.

      Password Field ExampleImage Modified

Par. Linked Value

When creating a sub-type entity, the system uses this attribute to link to the parent entity's ID field on the ParentID field of the sub-type. It can also be used for second-level sub-types to link back to the top-level entity. See the PersonID field in the PersonCompanyFunctions sub-type entity for an example. See Creating Multiple Filegroups for  for more information on sub-type entities. Finally, it is also used in some instances for top-level entities; see the OrderMeetingDetail top-level entity for an example.

...

If your organization has configured Aptify to display localized content to users, this field specifies a Culture Strings record that provides localized versions of the Help Text content. See Localization in the Admin Guide for more information.

Help URL

...

When a user clears the option from the In Table option, a Virtual Field tab appears on the Fields form. See Virtual Field Tab.

Is System

This field specifies whether a particular field is considered to be integral to the functionality of the Aptify Framework. In most cases, system fields are not found in entities related to business applications.

...

  • When set to None, Aptify adds this field to a generated form as a standard multi-line text field. See Multi-Line Text Field for more information.
  • When set to RTF, Aptify adds this field to a generated form as a Rich Text Field part. See Rich Text Field for more information.
  • When set to HTML, Aptify adds this field to a generated form as an HTML Field part. See HTML Text Field for more information.

Anchor
_security
_security
Security Tab

This tab configures the field's security settings. Field Level Encryption setting appears by default. Additional options and tabs appear when Field Level Security is enabled at the entity level. See Field Level Security in the Admin Guide for details.

Fields Record - Security Tab

Group Permissions Sub-Tab

...

Selecting this attribute enables data encryption for this field. When enabled, the Security Key field becomes available. See Field Level Encryption in the Admin Guide for details.

Security Key

Security Key sets the key used to encrypt the field. This option is only available when the Encrypt Data option is selected. This field links to the corresponding Security Key record.

...

Selecting this attribute enables In Place Editing at the field level. This is only applicable if In Place Editing is enabled at the entity level (on the Entity's Security > Options tab). Once enabled at the field level, youcan specify Edit In Place permissions for users and/or groups in the field's User and Group Permissions records (under the User Permissions and Group Permissions sub-tabs).

...

For Standard + Script and Script Only, the Script sub-tab stores a validation script that either supplements (for Standard + Script) or replaces the GE validation (for Script Only) for the field. Field validation scripts should be in VBScript format. See Scripts Service for Adding Scripting to a New Entity for information on writing scripts in Aptify.

...

  • Static List: When this option is selected, an administrator manually enters one or more values in the Values sub-type list (by creating a Values record for each value; see About the Values Form). Also, see Standard Combo Drop-down List.
  • SQL Statement: When this option is selected, an administrator enters a SQL Statement in the Values field of a Values record (see Values Form) to define the list of records and the associated fields that appear in the selection list (both in a data combo drop-down field on a form and in a multiple selection dialog, depending on the configuration of the GUI Type Single Select and GUI Type Multi Select options). When selecting this option, you may also need to specify the Linked Entity and Linked Field in the Fields record's Top Area. See Data Combo Drop-down List.
  • Entity List: An entity list is a register of values that originates from a list populated with values from another entity. If this option is selected, all of the information within the Entity Link display information section of the associated Values records must be populated (see About the Values Form).

Anchor
_virtualField
_virtualField
Virtual Field Tab

...

  • None: Selected by default. This value is the default used for fields that are not virtual fields. Virtual fields should never be set to this type.
  • Manual: User must manually modify the Base View for the entity as necessary to - accommodate this field.
  • Joined: The virtual field displays a value from a field defined in a joined table. See Joined Virtual Field for information on how to create a Joined Virtual Field.
  • Calculated: Indicates that the virtual field is calculated from other values, including values from fields in other entities. The information is not stored in the database table but the relevant information is added to the entity's Base View.
  • Computed: Indicates that the virtual field is calculated from other values within the same table. Unlike a Calculated field, which is calculated within an entity's Base View, a Computed field is calculated at entity's primary database table. Note that a Computed field is not a physical field in the table even the Computed field appears in the table details when viewed using SQL Server Management Studio. You cannot create a constraint or an index for a computed field. (Aptify does not create Persisted computed columns.) Also, if you are adding a Computed field to an entity that has multiple base tables, the computed field and all of the fields that are referenced in its calculation must be in the entity's primary base table.

 

Note

See Calculated and /Computed Virtual Fields for information on how to set up Calculated and Computed fields. Also, refer to Microsoft SQL Server Books Online (https://technet.microsoft.com/en-us/library/ms130214(v=sql.105).aspx) for more information on Computed Columns and their requirements. 

...

Note

Required Join Types create Inner Joins in the Base View between the current and Joined Entities, and prevent all records that do not have corresponding records in the Joined Entity from being displayed in views.

Anchor
_calc
_calc
Calculated/Computed Field

...