The Entity Details screen displays all Entities defined per Application. It can also be used by Administrators to add custom attributes to an Entity. These can be existing fields in the Logical Unit that are not currently synchronized with the Aurena Native application or Custom Attributes.
When an Entity is selected the details and attributes of that Entity can be viewed as shown below:
All Entity Details are read-only and for information purposes only.
The Default Where statement shows the Where clause that is applied to the view when synchronizing the data to the Aurena Native application. Although this Where clause cannot be modified, it is possible to add an additional Where clause by creating Filters for the Security Group Grants associated with the Entity as displayed in Synchronization Rules.
Publish Custom Attributes
Once the Custom Attributes have been amended they must be Published so that they become available to the Users of the Aurena Native application. To do this the command Publish Custom Attributes must be used. This will mark all custom attributes as Published and all Users of the Aurena Native application will be notified that an Initialization is required to synchronize the new table configuration and data.
Create Permission Set Filter
Additional row level filtering can be added to any Entity that is synchronized with an Aurena Native application by adding Filters to the Security Group Grants. See Security and Filters for more information how to set up the Permissions Sets against Security Groups and how to add Filters to Security Group Grants.
When this is done and is granted to the end user it will take effect on the next Sync whether that is Push, Batch or manually triggered via Sync Now.
Note 1: It is important to remember that large data sets should be filtered to ensure the synchronization processes (Push, Batch on the server & Initialize on the client)
Note 2: It is important to ensure that any permission set filter that is added to an entity is efficient and does not impact the synchronization process.
The Entity Details and Attributes represent the tables and columns that will be created as tables and columns within the Aurena Native applications local database. Only the Entity Details and Attributes displayed in this screen that are Published will be synchronized with the Aurena Native application.
All Attribute Details are read-only and for information purposes only (with the exception of Boolean True Value and Boolean False Value for Boolean Custom Attributes).
Add Custom Attributes
It is possible to Add new Attributes that will be synchronized with the Aurena Native application via the command Add Custom Attributes. This will allow the addition of any field that exists in the Application Projection that is not currently being synchronized with the Aurena Native application or any Custom Attributes created against the Logical Unit.
On selecting the command Add Custom Attributes a dialog will be displayed showing all attributes that can be added to the Entity.
Once new attributes have been added they must be published via the command Publish Custom Attributes.
If multiple changes are to be made to entity attributes then the publishing can wait until all entity attribute changes have been made. This will minimize the impact on the Aurena Native users as publishing will notify all users of the Aurena Native application that an Initialization is required to synchronize the new table configuration and data.
Note 1: It is only possible to Publish Custom Attributes against an Active Application Version
Note 2: It is possible to delete Custom Attributes.
Note 3: When adding a Custom Attribute that is a Boolean, the Boolean True Value and Boolean False Value fields must be set if the values used in the Boolean Attribute are different to the standard "TRUE" and "FALSE".
Note 4: Custom Attributes of type Reference are not supported by the IFS Aurena Native Framework.
Note 5: Custom Attributes of type Enumeration with a Multi format are not supported by the IFS Aurena Native Framework.
Change Detection Block
If the Entity is defined with a Grouped Push Synchronization Rule Delivery Method then the tables used to maintain the Grouped Push data will be shown in the Change Detection Blocks tab. This lists all Tables and Columns that are used in the Grouped Push synchronization process to maintain the Entity data for the Aurena Native users.
For details on the Grouped Push Synchronization Process can be found on the Aurena Native Framework Synchronization Guide