The overall meaning is that you can on the fly, you can take an input by a user and validate it any which way you want. pattern matching, upper lower case, units, bespoke pattern matching, everything and anythign you want to ensure the user input is set to whatever you need. This is because on the AIF you are effectively using a bespoke remedy form and thus you can use any remedy workflow you want, so no restrictions here.
You can also on AIF, push answers given to other fields, so one thing AIF's in particular are good for, is dependant on user selection can drive workflow that can then set other fields, display other fields etc. So a menu item selection on one field with a certain value can drive the form to then show a certain tab and fields to the user, whereas another selection would show something different etc.
Thanks Stewart for the answer.The complex validation is pretty clear now.
Also one thing is there that i am now using a template with backend mapping. So far the procedure defined in pdf i have created a w orking list. Now i don't know how to move on,i mean what should be the next step.
I believe Deepti is refering to creating an AIF using one of the OOB AIF Templates installed.
The working list is created to ensure that when you make a copy of this Template, that you relate all the workflow from the original OOB Template form to your new form. This ensures that all the functionality is available on the copy (new) of Template you have used.
Your steps should be:
1. Open OOB AIF Template you want to use in Dev Studio
2. Create a copy of the Template
3. Create a Working List of the original OOB AIF Template
3. Open the Working List and relate all the workflow from the original OOB AIF Template to your copy of the form i.e. Add in (reference) your new form name to the original workflow.
The Working List helps you find all the workflow that is related to the original OOB AIF Template.
I also suggest you make a Working List of your new form, this way you can track all the changes and also package the form for deployment when it is completed.
Thanks to all for the reply.
Carl u r right ,i am referring to the OOB templates that are available in SRM and thanks for your answer
One template available is AIF with backend Mapping.. I don 't understand one thing that with which application we say that this template is mapped.
So far my understanding on SRM using SRM we can create Incident,Change and Workorder ticket. When i am using AIF how will the workflow be mapped with the particular application which we have specified in AOT
I hope my confusion is a bit clear
the function of the AIF is to present and provide an alternate way to capture data from the user for the Service Request from the normal DVT layout and OOB question types. This allows for greater flexibility when designing questions and the presentation of these questions to the end user. The AIF then, dependant on the type used, will push the values down to the SRM:Request form for use in the normal flow (PDT > AOT) or even capture the data on the AIF form itself.
The normal SRD > PDT > AOT flow still occurs and you configure this as you would any other Service Request.
Refer to the guides for further information.