After upgrade of WCC to 24.x release, we do not see the new functionality (Monitor) access in ApplicationAccessPolicy.
There was a problem during WebUI policy upgrade phase, normally this is done automatically as part of upgrade. This could happen if there was a problem with EEM connectivity during the upgrade phase.
One example from cawa_installer.log for such a use case looks like:
2026-02-06 04:41:07,079 [main] INFO com.ca.wla.ae.installer.mm.action.wcc.RegisterWCCEEMPolicies(67) - Upgrading R12 EEM Policies for WCC
2026-02-06 04:41:07,081 [main] INFO com.ca.wla.ae.installer.eem.WccEEMUtils(63) - EEM is already initialized.
2026-02-06 04:41:07,092 [main] DEBUG com.ca.wla.ae.installer.mm.action.wcc.RegisterWCCEEMPolicies(77) - Cannot register wcc eem policies com.ca.wla.ae.installer.exception.AEEEMValidationException: [CAUAJM_E_112111] An internal error occurred while interacting with the CA EEM server.
2026-02-06 04:41:07,093 [main] WARN com.ca.wla.ae.installer.logger.LogHelper(52) - NonFatalException : W_AE_WCC_EEM_RegisterApp_Failed [CAUAJM_W_116420] Unable to register or upgrade the Web UI EEM application.
[CAUAJM_W_116420] Unable to register or upgrade the Web UI EEM application.
2026-02-06 04:44:17,812 [main] DEBUG com.ca.wla.ae.installer.customaction.AEBackUpLogs(288) - Exception occured while backing up EEM logs:
Reverting to a backup/snapshot prior to upgrade, fixing any errors during the upgrade phase might be the best approach.
If that is not possible and you have a backup of your original custom policies prior to upgrade, you can follow below steps to get the new functionality into custom policies:
NOTE: This assumes that you have a backup of WCC EEM policies from the older release prior to performing the steps below.