A data driven configuration to allow end users the ability to add a form to collect data in the portal without the need for a developer to surface the form in the portal. Entity Forms are created in the CRM and and then be placed into web pages in the Portal or used in conjunction with Sub-Grids and Entity Lists to build out complete web applications
Adding a form to your portal
The Entity Form contains relationships to web pages and additional properties in order to control the initialization of the form within the portal. The relationship to Web Page allows dynamic retrieval of the form definition for a given page node within the website.
To view existing Entity Forms or to create new Entity Forms navigate to Portals > Entity Forms
When creating a new Entity Form the first step is to decide the Entity and Form Name that you will be rendering as well as the mode: Insert, Edit, or Read Only. The mode selected will determine if you are creating a new record from the portal, editing an existing record, or just displaying info about a record on the portal
The Web Pages associated with the Entity Form can be viewed by clicking the Web Pages link listed in the Related navigation links in the left-hand menu.
When creating or editing a Web Page, an Entity Form can be specified in the lookup field provided on the Web Page form.
The various master pages used by the portal found in the Adxstudio Portals installation directory contains declarations of the EntityForm server control. When redering the Web Page containing either the Page (~/Pages/Page.aspx) Page Template or Full Page (~/Pages/FullPage.aspx) Page Template, the controls will determine if the Entity Form lookup contains a value then the form will be rendered.
Securing your Forms
In order to secure your forms, you must create Entity Permissions that determine access and ownership of the records in the CRM according to Web Roles. If a user lands on an Entity Form and does not have permissions, they will receive an error message. In order to Enable Permissions for an Entity Form. the boolean field "Enable Entity Permissions" must be set to true.
Read here for more info on the various configuration settings and attributes for Entity Forms
The Entity Form Metadata contains additional behavior modification logic to augment or override the functionality of form fields that is otherwise not possible with CRM’s native entity form editing capabilities.
Essentially metadata lets you configure specific pieces of the form - such as a field on the form, a sub-grid, the Notes section, or an entire Section or Tab of the form. These cannot be modified at the top-level configuration of the the form as a whole, so for each element of the form that we want to modify a separate metadata record needs to be created.
Adding Subgrids to your Managed forms on the portal is easy - just add the subgrid to the CRM form that you are managing through the OOB CRM form designer and your'e done. The grid will use the view that is specified in the CRM form designer, show only related records if that option was chosen in CRM, optionally show a search bar, and even respect Entity Permissions. It doesn't get any simpler to display a readonly list of records. In order to enable actions for the grid - Create, Update, Delete, etc., you must configure those actions using metadata configurations.
Just like with Subgrids, adding notes to your Managed forms on the portal is easy - just add the notes control to the CRM form through the OOB CRM form designer and your'e done. You can configure the behaviour of the notes control with metadata.
Note that Notes also respect Entity Permissions, Just like Sub-grids do.
A managed form can be configured to display a map control to either display an existing location as a pin on a map or to provide the ability for the user to specify a location.
By default an Entity Form will allow for reading or updating of an existing record, or the insertion of a new record. However, you can easily enable and configure additional actions for records in an Entity Form as well (Delete, Activate, Deactivate, etc.). It is also possible to override default labels, sizes, and other attributes that will appear if there are actions enabled.