Exclude Entities from having Custom Attributes¶
Due to architectural design decisions, some Entities or some Application Forms may not be extended with Configuration functionality. In such a case, such Entities and Application Pages should be explicitly excluded from Configuration logic so that a user will not be misguided.
The Excluded Entities page lists the manually registered Entities that cannot be extended due to architectural reasons. Reasons for this can be including, but not limited to:
- Performance impact. Custom Attributes adds a very small performance overhead when used on an Entity. For particular Entities in heavy use, this overhead can add up to a performance problem.
- The design of an Entity. IFS has implemented a particular Entity such that it is impossible to use it with the Custom Attributes framework, e.g. for performance reasons. This could be due to the design of both the client code or the server code.
Join and union views. All records in a view must have a rowkey which corresponds to a record in the base table to extend it with Custom Attributes. There are views defined as joins or unions where that is not the case.
Framework Entities. All Entities in the components FNDBAS and FNDCOB are excluded. Extending some of the Framework Entities with Custom Attributes is simply not possible, due to their nature and different use compared to normal business object Entities.
There is a possibility to add a reason of why the Entity is not suitable to use together with Configurations.
You can export the Entities that you don't want to be able to extend with Custom Attributes. You can either export All Entities or All Entities for one component. The file can be used to run during the installation of IFS Cloud to avoid Configurations on certain Entities.