If you have a comment on this topic, contact Aptify Documentation. If you want to return to the Aptify Community Site, please click here.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This service stores User Interface parts, which store HTML, JavaScript, CSS and other UI elements used to display forms, dashboards, and other features in Aptify's browser-based interface. The UI Parts service can be used to get these components via AJAX.

 

UI Parts Record

Attachments Tab

The Attachments tab lists any files relevant to the UI Parts record. The tab becomes available when the record is initially saved.

General Tab

Name

The name of the UI Part. If the part is generated (that is, generated by one of Aptify's Metadata Generators) the part is named based on the type of element that is generated. For example, if it is a form template, the ID of the Form Templates is followed by the UI Part Type. For example, Form Template ID:12345 Form Template UI Part CSS.

Part Type

The type of UI element, as defined by the UI Part Types service. The default options are Container, HTML, CSS, JavaScript, and JSON.

Description

A description of the UI parts. If the part is generated (that is, generated by one of Aptify's Metadata Generators) the description is based of the type of element that is generated. For example,

Generated

When selected the UI Part was generated by one of Aptify's Metadata Generators. When cleared, the record was created manually.

Key Value

Reserved for future use.

Text

Depending on the on the type of UI part, defines the metadata for the part. For example, if this is a HTML part, the HTML syntax for the part if defined in this field. If this is a CSS part, the CSS syntax is populated in this field.

Part Links

If this UI part is related to any other part, those parts are listed on the Part Links tab of UI Parts records. UI parts that are containers, are used to contain multiple UI Parts under a single UI Parts record. For example, a form template will link to one UI Part that is a Container for HTML, CSS and JavaScript UI Parts, all which will be listed on the container part's Part Links tab.

  • No labels