Omatic Cloud
296 results found
-
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 -
When copying a formula, copy all the setting of that formula (summary grid, matching settings, etc.)
1 vote -
1 vote
-
1 vote
-
Excessive number of duplicates - when donors give twice within same flat file
If a donor donates twice within the same flat file, Omatic Cloud will generate duplicate records for that donor in Raiser's Edge (because it sends records all at once). In contrast, ImportOmatic sends records one at a time, so if a new donor gives twice, it will be matched the second time.
This is especially problematic for events, when a donor will both buy a registration ticket and make a donation within the same flat file. Multiply this by the majority of the attendees for the event and it results in an excessive number of duplicates. This is a big…
1 vote -
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 -
Mailchimp Unsubscribe Formula - campaign information missing
In the unsubscribe export file on Mailchimp, it lists the email campaign that prompted the user to unsubscribe under the 'UNSUB[underscore]CAMPAIGN[underscore]TITLE' field. Unfortunately this campaign field is currently not information available within the unsubscribe connector API. Neither is UNSUB[underscore]TIME. it would be good to be able to add this information to RE through Omatic Cloud as it is vital additional context on unsubscribes.
1 vote -
Add ability to route to "ignore" and filter records from processing
When building a formula, it would be extremely helpful to define a set of criteria or matching rules that would automatically route a record to Ignore or a queue to Confirm Ignore.
3 votes -
Add/Update Gift Data as part of PostOmatic Processing
We often use PostOmatic (POM) to apply complex logic, concatenating data from multiple sources in RE to determine the final Debit/Credit accounts to which transactions should be written in our financial systems.
There is no simple way to look at a gift in RE and say, "This is the Debit/Credit that was used."
While the output data from POM can be re-imported to RE, currently, this is a secondary manual process. Could POM be updated to include an option for automatically adding the final Debit/Credit outputs to the source gift record?
4 votesThanks for the idea JPP. Can you be more specific about where you want the debit and credit used to be added back to the gift? There are certainly limitations as to where data could be written back to the gift due to field size constraints as well as considering all of the output that is typically in Post to General Ledger files.
Here are a few more questions for consideration:
What is the goal of having this data in RE/how would that data be used?
Should there be any considerations if an adjustment is being posted due to adjustments creating reversing entries to reverse out what was previously posted and then having new journal entries created for the updated information?
What other scenarios might we need to account for if we added a write-back feature?
Thank you
Steve Brewer
Product Manager
-
Ability to map Action Notepad Type
When importing CC data into NXT via Omatic, the default for Action Notepad Type is "Added via Web View". This default is not effective in allowing us to report to our Board and stakeholders outcomes. After uploading actions we will have to manually change this field.Having the option to define or map this field will give us richer data and better metrics to report on.
4 votes -
Allow matching on fuzzy address formats
Incoming address may be the same as existing, but with different format. We do not want to overwrite the existing address with one that has an incorrect address format and be constantly doing data clean up to correct. Need an option to only update address if it is different from existing address by a percentage. If it is 90% the same, then don't update address. OR it should give value update option, as it does if incoming title is different
72 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.
2 votes -
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…
136 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 -
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 record68 votes -
List Management available
Given the plan for RE to move to a "total web solution" which will ultimately replace database view, for users of IOM List Management, could this feature be made available through Omatic Cloud?
6 votes -
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).
3 votes -
Add ability to specify the Constituent Code sequency (Primary Consituent Code) when adding or editing
Blackback RENXT considers the first or top Constituent Code on a constituent record to be the primary code. This primary constituent code is automatically used in reporting and is the default on new gift records.
We are requesting the ability to specify if a constituent code should be in the top spot when importing (creating or editing) a constituent record.
The skyapi for constituents allows a sequence to be specified when creating or editing a constituent record however Omatic Cloud has not exposed access to specify a sequence value.
The current behaviour appears to add a new constituent code to…
3 votes
- Don't see your idea?