In previous releases, the component container did not have application server communication when the user switched from one active tab to another. This was developed for performance reasons.
In some cases, there is a need to have server communication, e.g. if certain data needs to be gathered when a tab is pressed, but only if and when the tab is pressed. For this purpose a set of alternative component containers, which have server communication when tabs are pressed, have been developed. The new component container is implemented as variants of the existing component container.
Technical information for custom component developers:
The CIC framework calls the activate functions of all components in the framework immediately before the main front office screen is called. The deactivate functions of all components in the framework are called immediately after the call of the main front office screen. In turn, the activate function of the component container calls the
activate function of all its subscreens in one process.
In 4.6A CIC the new variants activate a subscreen only when the related tab is pressed and deactivate a subscreen when focus goes away from that tab.
Choose the required variant in customizing when assigning a component container to the framework.