Skip to content

Omatic Cloud

Welcome to the Omatic Cloud feedback forum. Do you have an idea to improve the product? Do you recognize a good idea when you see one? You can create your own ideas and also vote on existing ideas. We want to hear from you!

79 results found

  1. Post to GL: Logic Actions/Drop Down Options

    It is possible to put the logic actions/drop-down options in alphabetical order?

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Post to GL  ·  Admin →
    completed  ·  Emily Dalton responded
    You can now see that these have been implemented when you log into a Post to GL Formula
  2. secondary Addressees and Salutations

    As I am starting to work on the Cloud, it would be great to be able to additional addressees and salutations besides the Primary.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    This is available under the section called "Other Name Formats". Blackbaud rebranded Additional Add/Sals to be called "Name Formats" in RENXT.
  3. Defined Fields more dynamic

    It would be neat if defined fields had the flexibility to include both a defined value, plus a concatenated value or the current date. For example, on import if possible we would define a "Source" field on imported donations with: "Online Gift Omatic Import dd/mm/yyyy" where the date is automatically today's date, and the text is input by us.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    In tomorrow's release"," we will be including a new update to the concatenation tool. You will now be able to concatenate a mapped value with a defined value or a current date.
  4. Option to add contact information to the source system on line-by-line basis

    Currently there is no option to edit billing information and often, donors make typo mistakes. It would be nice to have an option to manually pick and-choose when to send billing information to our source system, CRM, on a line-by-line basis. This would be a time-saving enhancement.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    Good news! This request has been addressed on the upgraded Omatic Cloud platform: https://omatic-cloud.helpdocsonline.com/buckets$inline-editing We are planning to upgrade users to the new platform starting in Q1. Our goal is to ensure a seamless transition for you. You can find more information about all of the new capabilities and FAQs on our resource page: https://help.omaticsoftware.com/omatic-cloud-upgrade
  5. Add filter to a formula

    Is there a way to add some sort of filter into the formula to exclude re receipted gifts so that they aren't pulled back into the formula due to the gift being modified?

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    Resolved by changing the date to pull gift data to use 'created date' vs 'modified date'
  6. Formula type: Luminate TeamRaiser Registrations and Donations to BBCRM Constituent/Revenue

    Currently, the Luminate TeamRaiser Registrations & Donations to BBCRM Constituent/Revenue formula type pulls in all records based on Date Modified in Luminate Online. Many times, other record updates (i.e. donations completely independent of TeamRaiser registration) are made to the record that should not indicate a 'new' registration. This idea is to improve this functionality to pull only from the date of registration and remain independent of record updates themselves, so as not to pull old records masked as new.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    I wanted to follow-up that this work is in development and should be released in April 2022! We'll follow-up once the functionality is live.
  7. Please add ability to export fundraiser information from RE NXT

    We need to send the following fields out of RE NXT:

    Fundraiser Name

    Fundraiser Type

    Fundraiser Date From

    Thanks!

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Ability to send first/latest gift information out of RE NXT

    We need the ability to export fund descriptions from our constituent's first and latest gift through the Omatic Cloud connector. Please let us know when this capability is added!

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Add Fields to TeamRaiser donations Formula

    Please add the fields below. They are currently in the other TeamRaiser formulas, but these will not work for TeamRaiser donations:

    a. Participant / Fund Designation
    b. Participant / DIY Fund Designation

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    It appears those fields are custom your Luminate Online instance. We believe you should be able to get those TeamRaiser field options to show in whichever TeamRaiser formula you choose by adding those values to gifts since those field options are automatically pulled in when Omatic Cloud requests the data from Luminate Online. Hope this helps!
  10. Ability to map to an Emma group

    The current behavior for mapping an inbound constituent to a group in Emma creates one row per Emma group on the mapping page and you set a defined value of TRUE for the group you want to map to. This is problematic when you have a large number of groups (thousands) as the page becomes very long. A better solution would be to have a row in the mapping table for GROUP with the ability to either define a group name or map to an incoming CRM field. The latter would also enable you to reduce the number of CRM…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    We implemented this idea as of this week. When mapping fields"," you will now see three new sections: Contact / Preferences: we have isolated the current method of mapping (by individual groups and subscriptions)"," so that users can continue to map fields the same way they have. This is ideal for small numbers of groups and subscriptions. Contact / Add Group: this new section allows users to map groups in a more generic manner. For example"," you could have an attribute category of Emma Groups and a value of November Group. When mapping to this field in your Omatic Cloud formula"," you will want to map the Group to the attribute value for that category. The Status field indicates whether the individual will be added to the group (value of YES) or removed from the group (value of NO). Contact / Add Subscription: works in a similar manner to the…
  11. Additional Addressee/Salutation imports

    It would be great if it were possible to import additional Addressee/Sals. I know this isn't currently possible from RE NXT, but hoping they can make it possible so you can too.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    This is currently available under the section called "Other Name Format". Blackbaud updated the verbiage for Additional Add/Sals in RENXT to be called "Name Formats".
  12. Option to include deceased records in the search for BBCRM

    Currently Omatic Cloud does not look for deceased records. It would be helpful to have an option to have a formula look for Deceased individuals. Right now they appear as "New", while we can override this and manually match, it would save us time/steps if the formula matched to deceased individuals as well.

    It may be nice to have a small flag or color change to signify that these records are deceased or inactive. It would potentially aid in finding duplicates in CRM or if needed adjust other business processes.

    The main thing we will be using this feature for…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    Hi Michael - I wanted to let you know that we have released this capability. When you go to your formulas, there are now Additional BBCRM Settings where you can choose to include inactive or deceased records in the search results. Please let us know if you have any questions. I do have a follow up question or two for you. Now that deceased or inactive records could appear in your search results, based on your decision in the formula configuration, when these records now appear as potential matches, are there any things that you would be looking for/want to see about these records in the search results (e.g. 1:1 bucket, 1:Many bucket)? If so, what would you like to see? What does this information tell you and why is it important to know?
  13. Add ability to append custom text to incoming field

    When creating a new formula, it is our practice to first build the formula connected to staging sites before pushing to a production environment. It is common for data in staging environments to be slightly altered. One example of this is that user email addresses are prepended with a short string of characters in-order to invalidate the email. This makes it impossible to match on email when using the omatic connector. I would like to request that the ability to append/prepend a small string to the value in the transformation section or perhaps in the concatenation section.

    Example: The outside…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    Good news! In tomorrow's release, we will be including a feature update that enables you to concatenate a mapped field with a defined value or a current date.
  14. import Education Relationship Attributes (RE NXT)

    As I am starting to work on the Cloud, it would be great to be able to import Education Relationship Attributes. Thanks!!

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    We have been working with Blackbaud, to encourage them to make Education Attributes available in the SKY API. Good news - that work is in progress! Once Blackbaud makes these fields available in the API, we will add the functionality to Omatic Cloud.
  15. Add Admin to support tickets

    Although I'm the Omatic Admin and I create the majority of any support tickets, there are others within my organization who use the product and have the ability to create tickets. Because they don't always think to CC me when they create a ticket, I'm hoping there's a way to set us up so that I'm always included on support tickets regardless of who is creating them.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    Unfortunately we don't have a way to CC users on support tickets. But we do have the ability to give you access to see all of the support tickets created by other users at your organization. We have now set up your profile so that when you log into our Support portal, you will see all tickets. Hope this helps!
  16. Need ability to use multiple Concatenate Spacers when creating a field to upload to Mailchimp

    I would like to be able to create a new field to upload into Mailchimp, combining different spacers, like have a space between 2 fields and then having a forward slash between another two set of fields within the same definition.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Admin →
  17. Option to Delete Page within the Ready bucket

    We have a need for the option to Delete Page within the Ready bucket. Currently, the only option is to delete by row or delete all. This takes a lot of time when we have 600-900 records to delete.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →
  18. Filter out profile picture when sending request to the server to avoid error message

    When a constituent has a profile picture in their bio, we get an error - Error on DataFormSave 'Individual Edit' Maximum request length exceeded. Per Omatic, the picture is showing in the metadata causing request to be too large when sent back to server. This idea bank is to request a long term fix to filter out the profile picture when trying to send the "edit" request to the server.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    Hi Melisa and Michael, we have released the fix to remove the profile picture from the Constituent edit request before sending it. Existing pictures on your side will remain in place after the edit. You don't need to take any action.
  19. Treat matches with inactive Altru records as data differences or exceptions

    Currently when formulas apply matching criteria to find matching Altru records, inactive Altru records are ignored and if there are no other possible matches, the incoming record is considered a New record. This can cause duplicates to be added to Altru, especially if New records are routed to the Ready bucket. It would be better if formulas with Altru as the destination would classify matches on inactive records as either a data difference or an exception so they can be handled separately from true New records.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Emily Dalton responded
    We have added the ability to match to inactive records. There is a new checkbox you can select called "Include Inactive Records in Match Results".
1 2 4 Next →
  • Don't see your idea?

Omatic Cloud

Categories

Feedback and Knowledge Base