Omatic Cloud
402 results found
-
Advanced address processing screen in the Omatic Cloud is needed
We need an advanced address processing screen in the Omatic Cloud. Right now my choices are to import addresses without knowing if they are valid, or ignore addresses We also need to be able to update a new address while saving the old address as a former address. Why? People enter their addresses online incorrectly and sometimes on purpose. (I've seen people who don't include their house number or apartment number, or enter "nowhere" street.") If I allow address information to come in that doesn't match to their current address I could be overwriting good address info in RE with…
240 votes -
Child object matching on address in Salesforce
Currently, address is not a child object in Salesforce, so when address fields are mapped, address data can be overwritten or duplicate contacts can be added when addresses are different (depending on matching criteria). Child object matching on address would help address this issue.
0 votes -
Add ability to only add certain mapped fields to new records
We would like to be able to decide specific criteria only applicable for new records added, not existing. Similar to applying default settings to new records in Importomatic.
Examples:
-Add addressee/salutation styles to new records
-Only add constituent code to new record
-Only add preferred name to new record112 votes -
Would like the ability to apply communication preferences in Encompass to the sub community where the email is sent out of.
have global categories at the root level, permissions for these categories are sub-community specific. This means that updates to categories at the root level do not affect sub-community levels
1 vote -
Add additional "Actions" to Ready Bucket
Have the other actions that you can do in Needs Attention available in the ready bucket (ie. The Add, Override and Delete button).
7 votes -
Add percentage of match results to ready buckets
The older version of Omatic Cloud displayed the percentage of matching information between records in our systems (Altru and Constant Contact). This was very helpful to us as we could minimize the amount of data being sent by only sending records with a percentage match under 100%. We would love to have this feature available again.
13 votes -
Have a repository for transformations
Can we have a have a repository for transformations so we don't have to rebuild and maintain them on different formulas? That would save a lot of time and double checking. Thanks!
231 votes -
Show Run Schedule in History and current last run date
We do not have a way to know what date/time range was used on any formula run. Also, we don't have visibility into the latest last run date. We are encountering issues with too much data being synced over and do not have dates/times to easily troubleshoot.
1 vote -
Include All Mailchimp API options - Member management
Mailchimp matching on email address sends an exception when Omatic Cloud - RE has a new email address for an existing contact in MailChimp
1 vote -
Formula type "BBCRM Constituents to Luminate Group" improvement
Currently when using this type of formula, the records need to be loaded to LO group all at once (automatically or send from Ready bucket).
My suggestion for improvement is to make the formula only rebuilds the group on each “fresh” run (at scheduled time), so we can process 1:1 match or 1:many match. Because we can not expect records in CRM and LO are perfect match at all times.
1 vote -
SSO Support for SAML 2.0 or OIDC
It would be great if there was improved SSO support for Identify Providers other than Microsoft.
Maybe SAML 2.0 or Open ID Connect to enable support for customers chosen IDP.1 vote -
Log when a formula is reprocessed in Activity History
Currently the activity history does not show when a formula is reprocessed. This info would be helpful especially when working through the exceptions buckets. it would all use to better track errors that are recurring.
4 votes -
Allow formula to always send full list of constituents from Luminate Group
Right now formulas are only based on time, I would like to build very specific queries in luminate to build groups and have omatic pull all records into RE every time from a group. This is important because group rebuilding once every day, and if a new constituent is missed the rebuild the next day will catch the constituent. But since the current formulas use last run date the only way that new constituent will go to RE is if it is modified.
1 vote -
1 vote
-
1 vote
-
Reprocess without Re-matching
Currently, when editing a formula you need to reprocess the data for the changes to take effect. What would be nice is there was an option to reprocess the data without needing to do the rematching.
For example, I edited a transformation after pulling in 100k records. Specifically updated the comments which is Defined not matched. Another example would be updating a transformation on a field that is not being matched by or routed by.
So essentially is an field is not being used to match or to route, then there is no reason to have to re-do the record…
4 votes -
Feedback requested for cascading toast notifications
With the release on July 2, 2024, we greatly reduced the cascading toast notifications and moved the notifications to the center of the page, as to not impede with interactions within the application. We want to continue to make incremental updates to notifications, so we'd love your feedback!
What information would you like to see in the notifications? Where and how would you like to access the notifications? How do you use the information to change a behavior or interaction within Omatic Cloud? What else?
0 votes -
Release Note Subscriptions
Allow users to subscribe for Release Notification emails and maybe even default that they're sent to client site admins. It could be as simple as a quick email saying when there will be a new release and a link to your Release Notes webpage (https://omatic-cloud.helpdocsonline.com/release-notes).
With other vendors, I add these notes to my work calendar so it's on my radar when changes are coming and helps me triage when something hiccups unexpectedly.
6 votes -
Add Ability to Clear Fields in Luminate Online
Currently, we are unable to clear fields in Luminate Online when we know data no longer exists or is inactive. It is a risk to not enable a way to clear data in Luminate Online, as the data could flow back into RE undoing the data staff changed. A null value should not clear a field, rather use a character like ~ to indiciate a field should be cleared. This should work for any data type (date, text).
3 votes -
Enhanced Mappable fields to Transformations
This was a previous uservoice story but there are still gaps with usability with the if/then ability in transformations. Specifically with if/then/else, the cascading transformations are challenging to build out for most users outside of onboarding.
The ability to include mapable fields directly to a transformation, outside of concatenated replace logic, would be very helpful and would allow for a more intuitive user experience. This is current functionality in P2GL and it would be helpful to have in Omatic Cloud as well.
3 votes
- Don't see your idea?