Omatic Cloud
269 results found
-
Add connector for Marketo
Add a connector for RE and Marketo to capture consent/solicit changes and campaign results to Actions.
5 votes -
Add text fields to facilitate documentation of formula configuration background
For each group heading in an ImportOmatic+ formula (in the mapping section of its definition), add text fields to allow the addition of notes by the creators/managers of the formula. This would improve the product by providing a mechanism for documentation directly within the formula. Information that could be included could be explanations of why certain configuration decisions were made, idiosyncrasies and deficiencies expected in the data, where to find current mappings/value lists from data source systems, and other considerations etc.
11 votes -
Applying Gift to Head of Household (HOH)
Would like to apply incoming gift records to the Head of Household in Raiser's Edge, even if the gift matches the email address of the spouse. If the gift matches to the spouse email address, spouse will also receive soft credit.
6 votes -
Comparative Logic for Date Inputs
We would greatly benefit from the addition of a function within transforms to compare a date input with a dynamic date provided at runtime. For example: if End date < Today’s Date then Replace input value with “Inactive”.
In our Raiser’s Edge database, we rely on the Constituent Code “Start date” and “End date” fields to determine when a donor opted into a program and whether they are still active with that program.
Presently, to update the status fields in our destination records, we’re forced to build a distinct NXT List for each pairing of program and status, as well…
17 votes -
Multiple Route to Ready Criteria Options
It would be helpful to have the OR operator for "Route to Ready" based on critera.
Ex: If Classy ID matches, Route to Ready
OR
If First Name/Last Name/Email matches, Route to Ready
4 votes -
Include flat file name on omatic cloud formula history page
Include flat file name on omatic cloud formula history page. Currently the page shows information like "Formula file upload started," "formula ingestion completed," and "export completed" for the Event column, and details on the number of records processed in the Description column, but it would be nice to include the name of the uploaded file in the Description column so you can easily identify which file was being handled. We use a flat file formula pretty frequently, with unique file names, and this would be very useful.
10 votes -
Allow us to stop/pause formula when running
Give us the ability to "Pause" or "Stop" processing. We currently have to open a ticket with support to kill a process. It would be more efficient and timely if we have that control.
6 votes -
Add connector for RENXT and Cvent
Add a connector for RE and Cvent to capture new/updated contact and consent updates and event campaign outcomes.
3 votes -
Advanced Name Processing for Omatic Cloud
Currently there is only a way to have exact matches on records. It would be helpful to have an Advanced Name matching option in Omatic Cloud, which is similar to the IOM option to score likelihood that a similar record exists in the system.
When a similar record is found, the records could go to Needs Attention for review, with an option to create New or Match.
The example of this is if a last name has an extra space or with multiple last names with a hyphen separating them.
It is faster for me to review Needs Attention records,…
8 votes -
Related Record Queue Display
It would be helpful to see all records in the Related Record Queue by page rather than a scrolling view. This will make review of records faster and more efficient.
1 vote -
Enable Importing Event Registrations from GiveCampus
The GiveCampus integration currently supports only importing gifts. Events is another large use for the platform and one we're looking to leverage. Being able to utilize this would improve our process flows greatly.
4 votes -
Allow phone match as a search scenario
Currently, OC does not have phone number available as a search scenario even when phone is mapped within a formula. This is essential to have because we otherwise wind up with unnecessary duplicates that could have been prevented.
2 votes -
Partial string 'Replace' transformation
It was a sad day when I realized that there wasn't a Transformation for address abbreviation standardization like there is in IOM (https://support.omaticsoftware.com/s/article/RegularExpressionDictionaryforAddressAbbreviations) and sadder still when I learned that I couldn't create a transformation of my own. While the 'Replace' transformation will IDENTIFY a field value containing a qualifying text string just fine, it will also replace the ENTIRE field value (not just the identified text string) with whatever replacement value you designate. Thought you could use a transformation for common address standardizations like replacing "Street" with "St"? Think again, because the way it exists now will…
4 votes -
Allow import or update of gift reference on existing gifts
Allow us to import updated gift reference data on existing gifts
3 votes -
Split gift by percentage
Add the ability to transform gifts by a set percentage of the gift amount in order to create a split gift with multiple funds. Example, 80% of the gift to one fund, 20% to another
3 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 -
ZIP code matching in Salesforce
Currently, 5-digit ZIP codes and 9-digit ZIP codes (where the first 5 digits are the same) will not match when attempting to match incoming records using address as matching criteria. This allows duplicate contacts to be added to Salesforce since Omatic does not match on the address when ZIP is one of the address field criteria.
0 votes -
ability to select what fields are updated separate from mapping/matching fields
It would be helpful if we could use fields for matching but then select which ones we actually want to be updated.
For example, match on name or Constituent ID/Donor ID, but only update the email address or web appeal activity information.3 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 -
Omatic Actions Sync in RENXT from Omatic Cloud to RENXT WebView: Custom fields with a value of a Link to a record
Omatic Actions Sync in RENXT from Omatic Cloud to RENXT WebView: Custom fields with a value of a Link to a record
As you are moving away from DB view, so will Omatic move away from using Profiles in the IOM Database view system. It will start using the cloud version which connects to RENXT Web View.
In DB view you can add Actions with Action Custom Fields that connect to records. I am expecting that this functionality will also be available soon in the Cloud API for Omatic. It is not currently available.
Please make sure that this is…
1 vote
- Don't see your idea?