Omatic Cloud
228 results found
-
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 -
Ability to silence or "x" out toast notifications in Omatic Cloud
Toast notifications can be distracting especially when multiple users are in an Omatic Cloud instance. The notification blocks the "X" button on the formula and prevents another user from closing a formula. When those notifications stack or another user is processing records, it can be a long wait.
It would be helpful to silence those notifications per user and have the ability to close out of the notification before the processing bar is completed.
5 votes -
Request to add ability to use sub forms in VolunteerHub
Current functionality is to use the "All Users" form when pulling fields for VolunteerHub. It would be nice to use subforms as sometimes we want to simplify the list of fields volunteers are selecting.
4 votes -
OC Date transformation for D/M/YYYY
Currently there is a transformation for M/D/YYYY but not D/M/YYYY
Seeing a lot of "data differences" simply because of OC adding back in a zero when we do not want one.6 votes -
Allow pulling an unsubscribe list from constant contact
Currently cannot pull this list. We tried to set this up pulling from the edit date, but that date is not updated when a contact unsubscribes. How else can we pull an unsubscribe list from constant contact?
9 votes -
Allow Replace transformation to apply to partial string replacement.
Currently, the replace function will impact the entire string. Example: When formatting an address, 111 West 3rd Street, I want to replace West with W & Street with St. In this scenario, the current functionality will give me an output of “W”. I would like to request the functionality to replace individual elements of a string. Example: When formatting an address, 111 West 3rd Street, I’d like to replace both West with W and Street with St, giving me an output of 111 W 3rd St. Without this additional functionality it is impossible to keep aligned with our database standards…
18 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…
77 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.
1 vote -
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 record39 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
37 votes -
Pull Tribute Data from the Encompass Transactions
Currently, the Tribute Data is not being pulled from the Encompass Transactions Endpoint. We need that information to import.
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).
2 votes -
Upload source files directly from Integrations/Formulas page
I'd like to upload the Source files for Flat File as-a-source formulas directly from the Integrations/Formulas pages, without the need to navigate back to Data Queue page and search for my formula every time.
1 vote -
Post-to-GL prepost feature
Many Salesforce and Virtuous clients who have FE NXT but migrated from RE NXT are used to the 'prepost' feature in RE / FE integration.
P2GL for Salesforce or Flat File does not have a similar feature that can be used to validate a posting before it creates an open J/E batch in FE NXT. A number of clients have asked about this.
2 votes -
Option to add mapped data only if records are new
We have a couple one off scenarios where we only want to bring over information IFF the record is a truly new record in BBCRM.
For example: addresses, BBCRM is usually the most accurate in terms of our data. While we have some "Add if not matched logic" we often run into the flags being set to false for new records.
So it would be nice to have a blanket "Always add address for new records"
1 vote -
Floating Column Headers in Buckets
When scrolling down a bucket, the headers do not follow and it's difficult to remember which field is associated with which header.
0 votes -
Populate More Example Rows from Luminate Surveys
It would be good to have more example rows populating for Luminate Surveys when working on the Data Mapping page in a formula. When building transformations it's nice to cycle through a few records to make sure the data is transforming as expected.
3 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.
3 votes -
Abilitly to do relationship matching in RE NXT based on Constituent Import ID
Currently, when importing relationships to existing constituents in RE NXT, the only option for matching to existing constituents is to map to either 'Constituent Lookup ID' or System Record ID. We really need to be able to map to Constituent Import ID. Especially when using a hybrid approach using both IOM-Classic and IOM+/OC, IOM-Classic furnishes the Import ID as an output field, but not the 'lookup ID' nor the System Record ID. This would be a very useful and valuable feature, and would allow clients to leverage the benefits of both versions of IOM.
7 votes -
Allow for email campaigns to be excluded from data push to database of record
Would love to be able to exclude email campaigns that are pushing back from Constant Contact to Altru.
3 votes
- Don't see your idea?