Working with views, actions and state machines
Working with views, actions and state machines for "EnterpriseObject" model is very similar to regular models. See the sections below for a summary of the differences.
Actions
Platform by default honor the action mask for NK EDFs just like any regular NK field and developer don't have to do anything specific. The same will be honor on UI screens.
Views and Action Screens
Platform by default makes the ObjectKey and ModelName field hidden for views and action screens as there is no use of showing these two fields on UI. Unlike actions, the developer has to specifically select the retrieval fields in the view definition.
As one might expect, in views and reports Platform displays the first NK EDF as the hyperlink field rather than ObjectKey.
State Machine
Unlike other models, you can create a state machine for EnterpriseObject model in the EPT.
Inbound/Outbound Interfaces
For both inbound and outbound interfaces, Platform hides ObjectKey and ModelName fields in the Add fields dialog. Instead it displays EDF fields which are part of NK as key fields, and they will be required in the interface. The developer can mark them optional as per the requirement if not all fields are expected.