Action |
Model Option |
Discouraged ? |
Alternative |
|---|---|---|---|
Add a stereotyped Entity operation (e.g. <<ns>>, <<nsreadmulti>>, etc.) |
None |
Discouraged |
Rather than using Subclass with Replace, add the stereotyped operation through the use of Subclass without Replace. This will ensure that your subclass (and thus your new stereotyped operations) will be treated as 'External', and that you won't get discouraged warnings in Eclipse when you reference them. Note that you will continue to get discouraged warnings if you directly reference stereotyped operations in the base Entity, as these are Internal - this is by design. |
Add or Change a non-stereotyped Entity operation |
None |
Discouraged |
Rather than using Subclass with Replace, add a non-stereotyped operation through the use of Subclass without Replace. This will ensure that your subclass (and thus your new non-stereotyped operations) will be treated as 'External', and that you won't get discouraged warnings in Eclipse when you reference them. Note that you will continue to get discouraged warnings if you directly reference operations in the base Entity, as these are Internal - this is by design. Customers are discouraged from providing new implementations for non-stereotyped application Entity operations. |
Change the structure of an Entity operation |
None |
Discouraged |
Create a new stereotyped operation 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 Server Modeling Guide for more information on how to do this. |
|
On Fail Operation Post Data Access Operation Pre Data Access Operation |
Allowed (Partially) |
Customer are still allowed to implement application Entity exit points. If customers want to perform processing in exit points for which there is a default implementation, the default implementation must be invoked at the beginning of the customer exit point implementation (i.e. there must be a call to 'super()' at the beginning). Customers are not allowed to switch off application exit point implementations. |
|
Treat Readmulti Max as Informational Exception Readmulti Max Records Returned |
Allowed |
||
Change an Entity class option |
Enable Validation |
Allowed (Partially) |
Customer are still allowed to implement application Entity exit points. If customers want to perform processing in exit points for which there is a default implementation, the default implementation must be invoked at the beginning of the customer exit point implementation (i.e. there must be a call to 'super()' at the beginning). |
Abstract Allow Optimistic Locking No Generated SQL |
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 |
Discouraged |
Use Extension classes to override these options on an application Entity class. |
|
Replace Superclass |
Allowed (Partially) |
Implicitly allowed to support other 'Allowed' actions described in this section |