Form
Overridden rate is calculated as the ratio of the number of forms, where a method is overridden, to the total number of forms.
What does the diagram say?
Not surprisingly,
init
method is almost always overridden. run
, close
and closeOk
methods are often overridden. All other methods are rarely overridden.The following methods are never overridden in standard application:
addHistory
blockPersonalization
closedCancel
controlMethodOverloadObject
copy
getActiveWorkflowConfiguration
getActiveWorkflowTrackingStatus
getActiveWorkflowWorkItem
initWorkflowControls
loadUserSetting
reload
send
setApply
skipSaveUserSetting
updateWorkflowControls
Datasource
Overridden rate is calculated as the ratio of the number of datasources, where a method is overridden, to the total number of datasources.
Top overridden methods are:
init, active, executeQuery, write, validateWrite, initValue, delete, linkActive, create
.All other methods are rarely overridden.
The following methods are never overridden in standard application:
defaultMark
findValue
markAllLoadedRecords
refreshEx
Conclusion
This standard application statistics reflects what is usually overridden by a developer on a regular project:
-
init
, run
, close
methods on a form-
init
, active
, executeQuery
, write
methods on a form datasource.