Omatic Cloud
296 results found
-
Enforce Unique Formula Names
Formula names should be unique in Omatic Cloud. Multiple formulas with the same name can cause confusion during processing or reporting an issue with support.
3 votes -
Add ability to filter transactions from Engaging Networks
It would be nice to be able to filter incoming Engaging Networks transactions by the status. The status being returned from Engaging Networks is either "success" or "reject" and we'd like to be able to filter the declined, or rejected, transactions.
3 votes -
3 votes
-
Review specific fields that don't match the source destination
When importing we are overriding values in our destination system that we may not want to. For example, field X has a value of A in the source data and value of B in the destination - we'd like a way to review this prior to sending to the destination (similar to data differences) so we can make a choice if it's overridden or not. Ideally we'd be able to define these fields as they are unique to our organization and business rules.
This is similar to the following idea but seemed a little different. Other idea: https://omatic.uservoice.com/forums/950413-omatic-cloud/suggestions/48105404-option-to-get-user-input-when-incoming-data-doesn
3 votes -
Add option to skip New User Creation
In certain cases, there are reasons that if no user is matched it would be more applicable to skip that user rather than have new users created. It would be nice to add the option to automatically skip/ignore New Users. Currently they do go into a new user bucket, but we have to manually go in and repeatedly empty the bucket.
3 votes -
Name fields from Stripe to populated
Stripe specific parsing reques
3 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 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
3 votes -
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 -
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 -
Make unmapped fields used in Record Match Search available in Summary Grid View
address, email, and phone are all helpful in identifying matches, but unless the fields are mapped, we can't access them in Summary Grid View. Please also allow fields used in Record Match Search to be added to grid view for ease in identifying correct matches
3 votes -
Print out P2GL formulas
Currently there is no ability to print out P2GL formula configuration or logic threads. Since formulas cannot currently be copied, they have to be replicated manually and the inability to print formula configuration tremendously hampers that effort. This is even true when working to apply logic from one client's formula to another -- since the logic thread cannot be printed, it's challenging to recreate from memory and/or to toggle back and forth between formulas/monitors, etc.
2 votes -
Sample Data (not enough of it)
Sample data provided when configuring new P2GL formulas is limited to 20 or 25 rows of transactions, which typically is not enough sample data to ensure that formula configurations are accurate and doing what the client needs. Two examples:
In one case there were transformations configured that looked right on the first 20 rows of data, but we couldn't see that the logic was incorrect on other rows. It was not until the client ran the post and saw an error on row 190 that we were alerted that the logic needed to be refined.
In another case, skip row…
2 votes -
Date Cleanup Format in mapping for Unix timestamps
We have a handful of connectors, example Hubspot, that save dates in a Unix timestamp format. A cleanup for date fields that will automatically changes dates to this Unix timestamp format would be helpful when integrating with these connectors. This will reduce destination exceptions caused by date format issues.
2 votes -
P2GL Activity History
It would be helpful to have Activity History for Post to General Ledger formulas. This would allow for an audit trail when trying to troubleshoot errors or instances when a formula was work previously and is no longer working.
2 votes -
Additional Scheduling Options
Right now, we have 3 scheduling options generally (weekly, daily, continuous). A client has requested that we have additional scheduling options, example: twice daily, twice weekly, every two weeks.
2 votes -
Ability to Schedule Formula to do Refund Pulls in Classy to Update Opportunities in Salesforce.
We need the ability to pull Refunds from the Transactions Connector on a Scheduled basis. Currently, this would have to be a manual run because when a formula is scheduled it only pulls based on the created date not the Refunded date.
2 votes -
Make popular / favourited translations available with one click
In Importomatic, to add Proper Casing takes one click. In Omatic Cloud it takes around 7. It would be useful if we could "favourite" certain translations, so that these are able to be applied with a single click.
2 votes -
Classy Transaction Filters
I would like to include the following filters in the Classy Transaction Endpoint:
- Company Gifts based on if Company is provided or Individual Gifts Based on if Company is not provided.
- Only Recurring Donations or Only Individual Gifts
- Status: Include Succesful or Pending(ACH)
- Date filters Refund Date, Date Modified, Date Added, or Payout Date.
2 votes -
1: Many, Freeze Incoming Record
If the potential matches in a 1:Many triage bucket record is greater than 5 and you scroll down to see if one of the lower potential matches might be it, the Incoming Record row disappears. It's like working in a spreadsheet where the top row isn't frozen to always display. Can we have something like Freeze Panes in the 1:Many triage buckets?
2 votes
- Don't see your idea?