Credentials

You will need the following items from iMIS

Mapping

You have three options for pulling data out of iMIS into FUSE

  • IQA - This is usually the preferred method as it provides you with additional control over what data FUSE will be able to ingest. If you need fields to be mapped that are not available via the Rest API, or if you want to create some custom query logic to only pull specific fields or results, you can optionally create an IQA in iMIS. You can add whatever fields you like to the IQA, complete your field mapping, and FUSE will sync the data every as specified in your onboarding document.
  • Drill down on iMIS Documents - This process uses the REST API and will do a drill down into document folders and index every document it finds below the main folder or any of its subfolders. The intial path should be provided, otherwise the drill down will start from the root and process everything. This works well for website pages data, but it doesn't support processing other datasets like events, contacts and even some office documents like PDFs if it is not associated with an imis document.
  • Rest API - This is also possible, but multiple times FUSE ends up pulling unwanted data records or records that don't contain some fields that FUSE would need to either display the data correctly or to decide whether to display the data at all, so most of the times the IQA path is preferred over this. If you're happy with the fields and records that the rest API provides, feel free to take the REST API path.