Hi @arunpatidar Thank you for your inputs and help.In servlet, we will be able to identify the wfname through request.getQueryString() originalURI embedded within a series of request wrappers has complete url along with query parameters
Hi @arunpatidar Thank you for your inputs. originalURI embedded within a series of request wrappers has complete url along with query parameters/{contextpath}/libs/cq/inbox/content/inbox/dialogs/dialogInjectionRender.html?item=%2Fvar%2Fworkflow%2Finstances%2Fserver0%2F2025-01-06%2Ftest-custom-appro...
Hi @arunpatidar Thank you so much for your inputs.originalURI, embedded within a series of request wrappers, contains the complete URL along with query parameters: /{contextpath}/libs/cq/inbox/content/inbox/dialogs/dialogInjectionRender.html?item=%2Fvar%2Fworkflow%2Finstances%2Fserver0%2F2025-01-06...
We are invoking servlet from a component dialog datasource node and not passing any parameters. wf model is dynamic as we have same servlet invoked by different workflows.
We are invoking servlet from a component dialog datasource node. And this component is included in Dialog path of Dynamic Participant step which will load when user takes action to complete that step. We will be able to get metadata map in any workflow implementation classes but not sure how to retr...
Hi, I have a workflow that includes a dialog participant step, and I am invoking a servlet to retrieve dropdown values. I have two different workflows calling the same servlet, and now I want to know the workflow name within the servlet. I tried the code below, but the workItem is always null.Any he...
Hi @Fanindra_Surat We have a configuration factory service to bind multiple config for different stakeholders. Whenever i update in one of the config instance and deploy code, I am seeing [CM Event Dispatcher (Fire ConfigurationEvent: pid=com.day.cq.mailer.DefaultMailService)] com.day.cq.mailer.imp...
Hi @Nupur_Jain In my case, I have a workflow that includes a custom process step to send email notifications. It works fine after starting or restarting the instance, or after starting and stopping the "Day Communique 5 Mailer" bundle. But, the issue occurs after some time.