AgileApps Support Wiki Pre Release

Difference between revisions of "Smart Components for AgileApps"

From AgileApps Support Wiki
imported>Aeric
(Created page with "The runtime UI components in AgileApps platform are exported as HTML element tags (custom elements) to customize the platform user interface. All the custom elements can make RE...")
 
imported>Aeric
Line 1: Line 1:
The runtime UI components in AgileApps platform are exported as HTML element tags (custom elements) to customize the platform user interface.
The runtime UI components in AgileApps platform are exported as HTML element tags (custom elements) to customize the platform user interface. All the custom elements can make REST API calls internally and hence are knows as '''Smart Components'''.  


All the custom elements can make REST API calls internally and hence are knows as '''Smart Components'''. The user does not need to invoke API calls to render data in the Smart Components.
You do not need to invoke API calls to render data in the Smart Components. The Smart Components use internal API calls to perform CRUD operations on records. Inputs to the APIs are usually passed as DOM attributes to the custom elements. Most of the Smart components are able to accept input parameters and some of them are also able to dispatch certain element specific events.


The Smart Components use internal API calls to perform CRUD operations on records. The inputs to the APIs are usually passed as DOM attributes to the custom elements.
If there are any future updates to the internal APIs used in the smart components, the internal implementation of Smart components would be updated. The customized UI need not be updated upon every version/patch release of the platform, in usual circumstances.


Most of the Smart components are able to accept input parameters and some of them are also able to dispatch certain element specific events.
The following Smart Components are currently available:


If there are any future updates to the internal APIs used in the smart components, the internal implementation of Smart components would be updated. The customized UI need not be updated upon every version/patch release of the platform, in usual circumstances.
:*Activity history <ace-activity-history>
:*Application tabs list <ace-app-tabs-list>
:*Login Form <ace-login-form>
:*Notes Editor <ace-notes-editor>
:*Object view list ( <ace-object-views-list>)
:*Owner Assignment <ace-owner-assign>
:*Record Attachment <ace-record-attachment>
:*Record Form <ace-record-form>
:*Record Process <ace-record-process>
:*Records view <ace-records-table-view>
:*Record Task <ace-record-task-view>
:*Related information <ace-related-info>
:*Table grid <ace-table-grid>
:*View Configuration <ace-view-configuration>

Revision as of 04:54, 3 November 2019

The runtime UI components in AgileApps platform are exported as HTML element tags (custom elements) to customize the platform user interface. All the custom elements can make REST API calls internally and hence are knows as Smart Components.

You do not need to invoke API calls to render data in the Smart Components. The Smart Components use internal API calls to perform CRUD operations on records. Inputs to the APIs are usually passed as DOM attributes to the custom elements. Most of the Smart components are able to accept input parameters and some of them are also able to dispatch certain element specific events.

If there are any future updates to the internal APIs used in the smart components, the internal implementation of Smart components would be updated. The customized UI need not be updated upon every version/patch release of the platform, in usual circumstances.

The following Smart Components are currently available:

  • Activity history <ace-activity-history>
  • Application tabs list <ace-app-tabs-list>
  • Login Form <ace-login-form>
  • Notes Editor <ace-notes-editor>
  • Object view list ( <ace-object-views-list>)
  • Owner Assignment <ace-owner-assign>
  • Record Attachment <ace-record-attachment>
  • Record Form <ace-record-form>
  • Record Process <ace-record-process>
  • Records view <ace-records-table-view>
  • Record Task <ace-record-task-view>
  • Related information <ace-related-info>
  • Table grid <ace-table-grid>
  • View Configuration <ace-view-configuration>