Skip to main content
All CollectionsIntegrations Hub
Integrations Hub - Pushback with iMIS EMS (OAuth)
Integrations Hub - Pushback with iMIS EMS (OAuth)

Creating a Pushback in IH using iMIS EMS (OAuth) | Average Task Time: 40-60 minutes

Julia Delk avatar
Written by Julia Delk
Updated over a week ago



In this article, we'll go over the steps for setting up an Integrations Hub Pushabck with iMIS EMS.

*** Not sure if you have EMS or iMIS Web Service? Here's an easy way to check:

Within your iMIS account, navigate to:

Settings > About iMIS > iMIS version

Version 20.3 or later = EMS
Version 20.2 or earlier = Web Service

Here is a screenshot of what this settings area will look like or similar to:

Important Note: In order to set up a Pushback through Integrations Hub, you must configure an Integrations Hub SSO first.

If you do not have an Integrations Hub SSO, please configure one here first.

Basic Setup within Your OpenWater Instance

We're going to create a program for where our Pushback will be used, a form for our program (that collects the data we are pushing back to iMIS), then, a few test submissions. If you already have these items in place, feel free to skip to the next section: Basic Setup within Integrations Hub

1. As an OpenWater admin you can login to your organization's instance here:


2. Follow the prompt to login then you'll be brought to your dashboard that will look similar to this:

3. We're now going to add a program.

4. Once you're done adding your program, you'll create your submission form. This form can be updated and changed whenever you like, so for the purpose of building this Pushback, just focus on including all of the fields you know you need in general (name, email, title, etc) and fields specific to the Pushback.

5. Next, create a few test submissions in your new submission form:

  • For your test forms, fill in whatever test data you'd like i.e. John Doe, Test Company, etc.

  • Make sure to fill out the entire form and use unique data for each form so you can tell them apart during testing later.

6. Once this is done, you can return to your dashboard. We have a few more items to complete in your instance in the next section.

Basic Setup within Integrations Hub

7. Get Started with Integrations Hub.

8. Add a new Pushback connector from the Integrations Hub dashboard.

9. You will be brought to a page with different Pushback options. Select iMIS (Applications).

10. You should now see the page below. We'll need to fill in a few settings:

  • Select the program that has your sample applications from your OpenWater Instance.

  • For credentials, choose the saved credentials from your previous SSO integration mentioned at the beginning of this article.

  • Set the CRON Expression to how often you'd like the Pushabck to trigger. We normally suggest Every Hour.

  • Once the above is added, click Save in the top left corner of your screen.

11. Select the Field Mapping tab towards the top of your screen and click Create Panel with Basic Mapping.

12. Give the panel a name and click create. I suggest a name like ow_ Pushback2023. My example uses ow_samples.

13. This will add a panel to your iMIS account. Press Run Once toward the top of the screen.

14. Great, now let’s see the data in iMIS. Keep this screen open in your browser. We'll be jumping over to your iMIS account to adjust some settings but we'll need to return to this page once we're done.

iMIS Side Settings

15. In a new browser tab, go to your iMIS organization account URL: https://{instanceurl}/staff


My organization is called King of The Hill and my website is This means my iMIS account login link should be:

16. Request admin login credentials from your staff if you don't have them already (it's important that these credentials are admin, other account types will not have access to what we need). Once you have the proper credentials, login to iMIS with these credentials on the above page.

17. Now we're going to begin adjusting some settings and gathering a few items from within your organization's iMIS account.

18. Let's see where the data from this Pushback is going in iMIS. Looking back to your iMIS dashboard items located on the far left of your screen, click Rise > Intelligent Query Architect. Once this page loads, click "New" (located at the top), and select "Folder".

19. Write "OpenWater" as the folder name and then click "Save".

20. Save this gist then import it into the OpenWater folder. Do this by selecting the folder OpenWater, and click Import at the top of your screen. A new popup will appear with a file importer. Select the gist we had you save, and click "Upload".

21. Ensure you update the destination with the new folder and click "Import".

22. Within your new IQA, go to Define > Sources > All Sources.

23. Next, search for the panel we just created:

24. Click into the panel we made and then go to the display tab and choose all columns.

25. Check off all available properties, press Save, then press Run.

26. This is where the data from OpenWater will be captured.

Back to Integrations Hub

31. Jumping back to Integrations Hub in the browser tab you left open earlier, we need to add your field mapping to wrap up the Pushback integration.

32. Now that we've added the panel iMIS, refresh the Integrations Hub Field Mapping page and choose Add Field.

33. You can now map any OpenWater form field to the iMIS Panel by using the drop-down options to connect your OpenWater Field to its corresponding iMIS Field. Then select Save in the top left corner of your screen.

34. Once you're ready, remember to Start the integration so it runs on a recurring basis.

Additional Tip:

If you wish to add custom fields to the Pushback, simply add more fields via the Rise Panel Designer in iMIS.

Testing Your New Pushback

35. Wait for your pushback's CRON Expression to trigger (the amount of time depends on what you selected in the settings in Integration Hub in Step 10).

36. After the designated time has passed, log in to iMIS and navigate to the IQA we created in Step 18. Here you should see the data from your test submissions populate.

Did this answer your question?