We have an automated system that creates pages and activates them. We have also a rollout config for mobile page creation. The problem is that sometimes activation happens before mobile page is created so mobile page remains inactive.
Is there a way to make sure mobile page is created before requesting activation? Any kind of notification to subscribe to?
Solved! Go to Solution.
Views
Replies
Total Likes
You can address the issue of activating pages before the mobile page is created by implementing a custom event handler with event listeners. This approach allows you to coordinate the activation process more effectively.
With event handling, you can create a custom event handler in AEM that listens for specific events related to page creation or updates. When a new page is created or modified, the event listener is triggered. Within the listener, you can check if the corresponding mobile page exists and is in the desired state, such as being activated. If the mobile page is present and ready, you can proceed with the activation of the main page.
In cases where the mobile page is not yet created or not in the expected state, you can handle the exception accordingly. This might involve logging the error, sending notifications to relevant stakeholders, or scheduling a retry for activation at a later time. By using event handling and listeners, you gain better control over the activation process and ensure that the mobile page is available before activating the main page. This helps to avoid inconsistencies and issues arising from premature activations.
You can address the issue of activating pages before the mobile page is created by implementing a custom event handler with event listeners. This approach allows you to coordinate the activation process more effectively.
With event handling, you can create a custom event handler in AEM that listens for specific events related to page creation or updates. When a new page is created or modified, the event listener is triggered. Within the listener, you can check if the corresponding mobile page exists and is in the desired state, such as being activated. If the mobile page is present and ready, you can proceed with the activation of the main page.
In cases where the mobile page is not yet created or not in the expected state, you can handle the exception accordingly. This might involve logging the error, sending notifications to relevant stakeholders, or scheduling a retry for activation at a later time. By using event handling and listeners, you gain better control over the activation process and ensure that the mobile page is available before activating the main page. This helps to avoid inconsistencies and issues arising from premature activations.