Process, Facade, WebService, WSInbound

Table 1. Extension Classes as Applied to Other Modeled Classes
Action	Model Option	Discouraged ?	Alternative
Change a class option	Abstract Generate FIDs Replace Superclass WS Binding Style WS Is XML Document Document Type Generate Facade Bean Provider Name Request Handlers Response Handlers Validate Request XML Document XML Schema	Discouraged	If you feel you have a valid need to change these options on application Process, Facade, WebService or WSInbound classes, please raise a Support case
Add an operation	None	Discouraged	This was never encouraged via extension classes, in that it would have required customers to perform in-place modification of application Java code. If you want to add an operation to a Process, Facade, WebService or WSInbound class, wrap the class and operation in your own project-specific class and operation.
Change an operation (e.g. operation visibility)	None	Discouraged	Create a new operation in a project-specific class, wrapping External APIs of the application class functionality if appropriate. If no appropriate extension point exists, but you feel you have a valid need to change the functioning or structure of an application operation, please raise a Support case.
Change an operation option	Audit BI Calls	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.
	Business Date Field Bytes Message Encoding Character Set Generate Security Is XA Transactional Message Type Queue Connector Factory JNDI Name Reply Queue JNDI Name Response Message Timeout Shadow Type Transactional Transmission Queue JNDI Name	Discouraged	If you feel you have a valid need to change any of these options on application Process, Facade, WSInbound or WebService operations, please raise a Support case.
	Secure Fields	Discouraged	Customers wishing to alter which fields of an application operation are to be treated as Secure should wrap the operation in their own Facade class and operation, and set the Secure Fields option on this new operation to the desired setting. Affected UIM screen definitions should be repointed at the new operation if required.
Change an operation parameter option	Mandatory Fields	Discouraged	Customers wishing to alter which fields of an application operation are to be treated as Mandatory should wrap the operation in their own Facade class and operation, and set the Mandatory Fields option on this new operation to the desired setting. Affected UIM screen definitions should be repointed at the new operation if required.