Custom Entity¶
Making a Custom Entity Time zone Aware
Custom Entities are created using Entity Configurations page in IFS Cloud.
Custom entities are suitable to use as lookup values for custom attributes, or to store arbitrary in flat "tables". They are not suitable for creating complex structures (e.g. hierarchies of master-child-grandchild etc.) because they do not have truly user-defined key columns, but instead rely on the unique ROWKEY column. Alternate Keys can be defined but they exist only in the metadata (so they do not enforce restrictions at the oracle table level), and null is accepted as a value in alternate-key columns. For complex data structures it may be better to recommend a customization.
Create Custom Entity¶
In IFS Cloud, navigate to Solution Manager > Configuration > Entity Configurations page to create a custom entity.
During the Custom Entity creation, you have the option to create a default Projection specific to the new Custom Entity. Once created, this Projection is not allowed to be modified. It is listed with type Generated Projection (Custom Entity)under Projection Configurations.
Making a Custom Entity Time zone Aware¶
If you wish to create your custom entity with time zone awareness, you can use the Time Zone Default Setting drop down menu in General section.
Value selection for Time Zone Default Settings drop down:
- None : Custom entity will not be annotated as time zone aware.
- Server : Custom entity will be annotated as time zone aware.
- Site : Custom entity will be annotated as Server time zone aware.
- Once selected, a new field labeled Site Source will appear. This field must be filled with an attribute containing Site ID. You can enter an attribute name from the same entity chosen for the Entity section or add a function to reference an attribute from a different entity.
Note:
- If you selected None in Time Zone Default Settings drop down, custom entity will work according to browser time zone. However, since the entity is not time zone aware, using it within any IFS Cloud Web page will not support time zone conversion features.
- Annotating the Custom Entity as time zone aware ensures that all its attributes inherit time zone awareness.
- Consider annotating entities as time zone aware as much as possible, depending on your application's requirements. This practice helps minimize potential confusion when handling date/time values.