2 of 2 people found this helpful
First, a quick clarification: you can use AIFs when submitting requests via Smart IT. See Submitting service requests - Documentation for Remedy with Smart IT 19.02 - BMC Documentation
But that involves invoking the mid-tier UI to render the custom view (which is what an AIF is), and that's certainly not the best user experience.
From that perspective, and for other reasons, we generally recommend to go with SRDs that use configured questions vs. AIF.
I would recommend to take a step back and look at the use case from scratch. What are the requirements? What action should happen, when the request is submitted, and what info is needed to perform this action? Do I really need to ask for all this info (the fewer questions, the better). I'd use the opportunity to redesign the whole request interaction for the scenario that the AIF covers.
There are a few best practices how to convert certain elements of an AIF which are not covered by the SRM question types into something that is supported by AIF. For example, if you have complex search capability in AIF, because you have too many options, you can think about implementing this via a sequence of menu questions which subsequently narrow down the choices.