Configurations works on a large majority of pages in IFS Aurena, but not everywhere. Configurations require that the implementation of pages and their underlying storage conform to framework guidelines and best practices. Architectural decisions taken when implementing a page can make it impossible to associate a configuration with it.
Note: This page lists a number of situations that is important to be aware of in order to work efficiently with Configurations. There are actually more situations that can be considered as a limitation than listed here.
To be able extend a View with Custom Fields or Information Cards, all records in the view must have a rowkey which correspond to a record in the base table. There are views defined which are created using joins or unions where this is not the case. Custom fields and Information Cards functionality would not work on these views.
For logical units without a base table but have a base view, only Read Only Custom Fields will be supported. The views of the LU (Base or Detail view) should have a Rowkey column with unique values. Therefore if a Utility Package has a Base View or a Detail View then Custom Fields will be enabled for those Utility Packages. Read Only Custom Fields will only be supported since there is no Base Table for Utility packages.
IFS Aurena Native Apps only support a sub-set of IFS Aurena controls. Care must therefore be taken when configuring IFS Aurena Native App Pages within the Page Designer to ensure the App displays the pages and data as expected.
If a control is added that is not supported in IFS Aurena Native then the control will not display in the App. Details on what controls are supported are documented in the IFS Aurena Native Development documentation here >>>
Any attributes that are added to Aurena Native App Pages must also be added to Entity Details for the data to display as expected.
Changes done with the Page Designer on attributes associated with a List of Values will not be fully reflected in IFS Aurena Native Apps.
Entity Modifications between IFS Application versions will be handled by custom_obj_sys.Handle_Lu_Modification. This method will update the Configurations related to Custom Entities and Custom Attributes. The user will need to manually update other Configurations.
Standard entities added to a projection configuration are read only, hence do not support CUD operations.
Custom fields connected to a standard entity are not supported.
Unlike ordinary application pages that have a straight forward interaction pattern where typically a user searches for data, update or add information and then explicitly save, assistants provide flexible implementation to suit the task at hand. Under these circumstances, it is not currently possible to provide custom fields on assistants.