- 3,677,157 Users
- 7,715 Discussions
- 12,830 Comments
Our Cloud Operations Team is currently investigating an incident where clients on POD 3 and POD 4 cannot access secure landing pages.
Would love to see a design-editor style WYSIWYG available within the Dynamic Content editor. Currently stylizing things like buttons, etc. is more complicated and time consuming in just the rich text editor.
My dream is to be able to choose the Last Modified/ Last Created/ First Created CDO Record when using Signatures Rules with a Key Field that is a CDO field. This is important when the CDO is setup so that one contact can have more than 1 record.
Currently, the Signature Rule setup is to always choose the First Created record.
According to Oracle Support :
"The exact behaviour for Signature Rules is:
- Order CDO records by Date Created in Ascending order.
- Pick the first record in the ordered list.
Therefore it will always pick the first created CDO record, not the last created. Unfortunately there is no any resolution or workaround to reach the goal."
If we can choose Last Modified/ Last Created/ First Created on the Signature Rule like we do with Field Merges, that'd be great.
Better yet, as this other idea was posted in the dream it, use Field Merges direclty within the Email setup rather than the tedious Signature Rules setup: https://community.oracle.com/topliners/discussion/4403956/using-field-merges-on-email-sender-settings
Thanks for the upvote !
In the native integration we were able to pass a link to Salesforce task object showing Form Submission data.
However, in the Salesforce Integration App this does not seem possible. Please provide this parity feature in the App!
The enhancement request ticket is EMCS-133480.
The native integration allowed an auto-synch to import directly into a picklist but it's not available in the new app.
This dreamit is to add the functionality to import any Salesforce object into a picklist.
It would be great to be able to block form submissions from certain domain or even free domains
That way we stop people giving us their personal, say Gmail email address, as we need their work email address
See example from another platform that has this feature
Google - "block-form-or-pop-up-form-submissions-from-specific-email-domains"
Hi, it would be super helpful to have segment/shared filter logic criteria to check whether a contact or cdo record are currently residing within a specific program or campaign canvas. Also, having the option to select the membership timeframe 'as of now' or 'within the last X days/hours' etc.,. would help cut down on the recurring entry to program volumes. Thanks for reviewing.
We can export integration errors from the native integration really easy at the moment and select a large time frame. We've been doing this for years to fix any integration errors over time.
Now that we've moved to the salesforce.com integration app this functionality no longer exists so we need to go through every call for every day and copy and paste the errors - this isn't reasonable and takes a massive amount of effort.
Please add the similar functionality to the salesforce.com integration app.
Thank you 😉
we installed several apps (CWM, Form Submission, Salesforce Integration,..) which we are using in automated programs which synchronize leads/contacts via Eloqua + CRM and modify data fields on these leads/contacts or set their consent status. Unfortunately the token of these apps needs to be reinstalled after 1 year and by sudden stop working. We experienced this is a big issue because it took us some time to figure out what's the issue and leads weren't created. A simple notification from the app would be helpful, to notify admins or the admin who installed the app, that the token runs out in some weeks. This will prevent any business impacts.. It is not a solution that we have to mark any date in our calenders to maybe be on time to avoid issues.
When building segments and filter criteria, often we want to use dynamic date filters, e.g.
The problem is that the dynamic date comparisons are based on US Eastern Time only. This is problematic for customers in other timezones (e.g. APAC customers) where there is up to an 18 hour time difference compared to EST.
To better explain, consider a New Zealand example, where NZ is currently observing Daylight Saving Time -:
A segment filter configured to include NZ contacts with a Date field value that is dynamically equal to Today, will not correctly evaluate until 6pm NZ time. Evaluating the segment at any time prior to this will exclude all target contacts as - according to EST, at least - the current date is not "today" and is in fact "yesterday".
This makes it incredibly difficult to build effective, timezone-relevant segments leveraging dynamic date filters.
Ideally, we would be able to specify a timezone to be used for dynamically evaluating dates in segment filters, e.g.