Entity

Table 1. Extension Classes as Applied to Entity Classes
Action	Model Option	Discouraged ?	Alternative
Add a stereotyped entity Operation (e.g. <<ns>>, <<nsreadmulti>>)	None	Discouraged	Rather than using an <<extension>> class, add the stereotyped operation through the use of subclass without replace.
Change an entity Operation (e.g. parameters)	None	Discouraged	Create a new stereotyped operation with the desired structure using subclass without replace. If you feel you have a valid need to change the structure of an application Entity operation, please raise a Support case.
Change an Entity operation option	Auto ID Field Auto ID Key No Generated SQL Optimistic Locking Order By SQL Where	Discouraged	Create a new stereotyped operation using subclass without replace. If you feel you have a valid need to change these options on application Entity operations, please raise a Support case.
	Database Table-level Auditing	Discouraged	This option is settable via runtime properties. See section 12.3.6 of the Cúram Server Modeling Guide for more information on how to do this.
	On Fail Operation Post Data Access Operation Pre Data Access Operation Treat Readmulti Max as Informational Exception Readmulti Max Records Returned	Discouraged	Customers should only change these options on application Entity operations by using Subclass with Replace.
Change an Entity class option	Enable Validation	Discouraged	Customers should only change this option on application Entity operations by using Subclass with Replace.
	Abstract Allow Optimistic Locking No Generated SQL Replace Superclass	Discouraged	If you feel you have a valid need to change these options on application Entity operations, please raise a Support case.
	Audit Fields Last Updated Field	Allowed	Currently only supported via Extension classes, and this will continue to be the case from 6.0.3
Add an Entity attribute	None	Discouraged	Customers wishing to add data to application screens should add new customer-specific Entity classes, and should wrap Cúram CRUD operations in their own process classes to maintain both tables atomically. Cúram screens can then be changed to point to the new process classes
Change an Entity attribute option	Allow Nulls	Discouraged	If you feel you have a valid need to change this option on application Entity attributes, please raise a Support case.