Hi All,I have a question on how SMS works with mid-source architecture. We have a hybrid/mid-source deployment (https://docs.adobe.com/content/help/en/campaign-classic/using/installing-campaign-classic/deployment-types-/mid-sourcing-deployment.html). This means the mta is running on mid-source insta...

For running workflows (mainly the scheduled ones, with external signals) the corresponding operator relation is stored in the table xtk:workflowLogin. Whenever an operator needs to to be deleted, you can just run a query on this table for any references of this operator and then update the record wi...

Hi Anumol,This is because emails use HTMLs and SMS texts. So in email a HTML can be defined as<a href="https://www.google.com">https://www.google.com</a> OR <a href="https://www.google.com">Click Here</a> . So when the email is viewed we see "https://www.google.com" or "Click Here", but the when hov...

Hi Anumol,If we are enabling tracking in a delivery, Adobe campaign modifies the url to a tracking server url. On clicking on this, you will be redirected to the original url. The reason for this is : the tracking url contains the identifier for the broadLog (recipient+delivery) in the id attribute....

Hi,Try setting the value of  allowUserPassword="true" and check the result.Thanks,Subhajit

Hi Thomas,Please the attribute dateOnly. e.g. DateOnly(@eventDate) = DateOnly(DaysAgo(3))Thanks,Subhajit

Hi All,We have have enabled LDAP authentication on our on-premise instance. The users are getting automatically created and assigned to the operator groups (based on their corresponding group in LDAP) , when they login to Adobe Campaign. However, their email IDs are not getting updated in the operat...

Hi All,I need some details on the deliverability url : https://deliverability-app.neolane.net/deliverability of Adobe. We are not able to make GET or POST calls to this url from our campaign instance. The error code returned is - 400 (Bad Request). We have the Deliverability monitoring and the Inbox...

Hi David,We have resolved the issue. The sessionTokenOnly value was set to false in the serverConf.Thanks,Subhajit

Hi David,We are using SOAP UI and passing the session token in the SOAP body. Below is the example of the post event call. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:xtk:workflow">  <soapenv:Header/>  <soapenv:Body>      <urn:PostEvent>        <urn:ses...