CCR Event Handlier superclass, this does nothing but provide interface for the real
event handler classes to use. Subclass from this and implement the methods
The interface methods are all implemented as class methods so that the system
can make their handler persistent if they so choose (the would need to fire the
appropriate save logic from within one of the callback methods).
During a Refresh call, the same instance of the CCREventHandler class will be used to call
RefreshPrepare() as well as RefreshFinalize(). This means that properties can be initilized in Prepare
and used in Finalize.
To activate the custom event handler, set the following global in CCR-controlled namespace: ^SYS("SourceControl","EventHandler","Class")="Custom.MyEventHandler"
Where the Custom.MyEventHandler.cls class extends %Studio.SourceControl.CCREventHandler.cls
property RefreshPrompt as %Boolean [ InitialExpression = 0 ];
This property is set to 1 if the Refresh is being run interactively and it is safe to prompt the user for input.
If it is not true, do not issue any Read commands as it will hang when Refresh is run from Studio
This method is called by the CCR Refresh logic, after the items have been refreshed into the namespace. It is intended for any additional configuration work which
may be necessary (e.g. initialization of reference tables, building of 3rd party sources, etc)
This method is called by the CCR Refresh logic, after the branch has been synced but before any of the items have been loaded into the namespace.
It is intended for use to do any preparatory work that must be done in a certain order (e.g. creation of csp application definitions, security objects, etc).
If abortRefresh is set to 1 before returning to the caller, then the caller will abort the Refresh