Before proceeding, be sure to review Interface Asset general concepts.
NOTE: You must own Premier or Enterprise plan to incorporate custom-built interface assets (IAs). Essential plan based Composer can open, run and edit experiences containing custom-built interface assets but cannot save any changes to those experiences unless the custom interface assets are removed. The ability to add custom IAs and save changes to those experiences is a feature exclusive to Premier and Enterprise plans.
This article is about custom-built interface assets. For more about working with Intuiface's out-of-the-box support for Excel, see this article.
- What resources (methods, events, …) are available?
- What kind of objects (schemas) can be accessed?
The Interface Asset descriptor has the form of a JSON file with the Intuiface-specific extension .ifd. This file syntax is based on the Google Discovery Service with some extensions specific to Intuiface. See the screenshot below. Click the image to zoom.
- The descriptor for a REST-based Web Service can be generated automatically through the use of API Explorer. There is no reason to hand-craft a descriptor for REST-based Web Services.
- To be visible in the Interface Asset panel of Composer, all hand-crafted .ifd descriptors must be saved here:
[Drive]:\Users\[UserName]\Documents\Intuiface\Interface Assets. This ensures all projects created on your PC will have access to these custom interfaces.
- Never edit any .ifd file while Composer is running, even if the associated interface is not being used in the experience you have opened in Composer. If you wish to make changes to a .ifd file, exit out of Composer first.
- If your new interface does not appear in Composer's Select an interface panel, check Composer's log file in
If using Intuiface Version 5:
This file contains useful information that may help you troubleshoot the formatting of your ifd file.
The following articles will teach you the specifics of IA descriptor creation: