This documentation applies to the 8.1 version of Service Request Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Creating AIFs from templates

BMC Service Request Management ships with three advanced interface forms (AIFs) that you can copy and then modify, as needed. This enables you to use the AIFs provided as templates. As a result, you can create an SRD and attach one of these AIFs as shipped with your service request.

The following AIFs are included:

Form name


With Backend Mapping (SRS:AdvancedInterface_With BackendMapping)

This example of the AIF uses a Regular form, which can be used to store data on the form itself, while also mapping some of the field values on the form to the fulfillment application fields. The fields on the form are used to pose questions to users and capture responses to those questions.

Without Backend Mapping (SRS:AdvancedInterface_Without BackendMapping)

This example of the AIF uses a Regular form, which can be used to store data requested of users directly on the form, without mapping this data to fulfillment application fields.

Password Reset (SRS:AdvancedInterface_Password Reset)

This example of the AIF uses a display-only type of form, and illustrates a password reset use case. A display-only form does not store any data. This type of form can be used only to map field values to fulfillment application fields.

The AIFs include requestable offering data. This data is passed when AIFs are displayed in the Request Entry console. The following fields are automatically copied from the Service Request Definition form to the AIFs when you upgrade to BMC Service Request Management 8.1.00 and later versions. If you customized the AIFs in releases versions earlier than 7.6.04, you must add these fields to the forms.

Field name

Database ID


RO Instance ID


Requestable Offering Instance ID



Requestable Offering Reconciliation ID



Requestable Offering Dataset ID


  • You must have BMC Remedy AR System Administrator permissions and knowledge of BMC Remedy AR System development to modify and enhance the advanced interface forms.
  • Create a copy of the advanced interface form and modify the copy, so that your work is not overwritten when you upgrade the application. Run tests on the copy to verify that it works the same as the original.
  • Create a packing list of the advanced interface form that you want to modify, and add all the related objects. This packing list makes it easier to identify the workflow that must be updated to use your new advanced interface form.
  • To avoid migration issues, do not copy and rename the workflow that is attached to the advanced interface forms, except as directed in the following procedure.
  • If you include date fields in the body of an advanced interface form (for example, if you add a question that requires the user to enter a date), create a custom workflow to ensure that the date is not copied when a user clicks Request Again to create a new request.

To create advanced interface forms from templates

  1. Log on to BMC Remedy Developer Studio.
  2. From the AR System Navigator, open one of the sample advanced interface forms.
    For example, open the SRS:AdvancedInterface_WithBackendMapping form.
    When opening the SRS:AdvancedInterface_WithBackendMapping form in BMC Remedy Developer Studio, you should modify only the fields on the Your Fields tab and only the field labels on the Mapped tab. Following is a description of the tabs and the fields on those tabs:
    • The Your Fields tab contains the fields that are saved to the form. This tab and all of its fields should be visible to users.
    • The Mapped tab contains fields that are pre-defined to map to fulfillment application fields on the Details tab of a work order. The labels on these fields can be changed to pose questions to users. This tab and any fields used to pose questions to users should be visible. Any fields not used should be hidden from users.
      These fields are mainly character and integer type fields. If a user response requires a selection field, data/time field, or a currency field, those fields can be placed on the Your Fields tab, and additional workflow with an execution order of 0 can be created to set the field values on the Mapped tab to the value of those fields. This would be done with the hidden fields that are not used to pose questions to the users. This enables those data types to be mapped automatically by using the pre-defined mapping.
    • The Mapped 10-27, Mapped 28-47, and (version 8.1.02 and later) Mapped 48- tabs contain additional fields that can be mapped to fulfillment application fields by using the Question Selection and Fulfillment Application Field Mapping dialog box during SRD configuration. These tabs should be hidden to users.


      The fields on the Mapped tab can also be mapped in this manner if the target fulfillment application field is not on a work order, that is, an incident or change request.


      Do not modify the other fields on this form—they are the core set of fields that map to the service request, and are needed to create the service request. You can, however, add specific workflow to the advanced interface fields for validation, and so on.

  3. Create a packing list of the advanced interface form that you want to modify, and add all the related objects.
  4. Save a copy of the advanced interface form that you want to modify.
    1. Choose File > Save Form As.
    2. Enter a new name for the copy.
      To ensure that a URL that contains the form name is not interrupted, do not use a plus sign (+) in the form name.
  5. Add your advanced interface form to the form attach list in the BMC workflow.
    1. Open the packing list you created in step 3.
    2. Open all the workflow objects from your packing list (for example, Active Links) and associate your form, except for the four following active links:
      • SRS:ADN:WithMapping_OnSubmit_109_SubmitRequest_CheckReqFields
      • SRS:ADN:WithMapping_OnSubmit_109_AddToCart_SetFlag
      • SRS:ADN:WithoutMapping_OnSubmit_109_SubmitRequest_CheckReqFields
      • SRS:ADN:WithoutMapping_OnSubmit_109_AddToCart_SetFlag
    3. Check the Filters, Active Link Guides, Menus, and Filter Guides, and associate the new advanced interface form to them as well.
  6. Perform the following actions to the preceding active links.
    You must modify this workflow to set the flag in the RequiredQuestionsAnswered field that determines whether the user entered all of the required information to submit the service request or the cart.
    1. Copy and rename the active links.


      Do not use the BMC prefix (SRS:ADN) when you rename the active links.

    2. Modify the form name to your own interface form.
    3. Modify the Run If qualification to match the required fields on your form.
  7. Edit the SRS:ADN:SHR_OnSubmit_SubmitInReview active link guide by adding your submit request active links to it.


    Add your active links under the SRS:ADN:WithMapping_OnSubmit_109_SubmitRequest_CheckReqFields and SRS:ADN:WithoutMapping_OnSubmit_109_SubmitRequest_CheckReqFields active links.

  8. Edit the SRS:ADN:SHR_OnSubmit_SubmitInCart active link guide by adding your cart active links to it.


    Add your active links under the SRS:ADN:WithMapping_OnSubmit_109_AddToCart_SetFlag and SRS:ADN:WithoutMapping_OnSubmit_109_AddToCart_SetFlag active links.

  9. Test your copied version of the advanced interface form.
    It should work just as the original form.
  10. Modify your copy of the advanced interface form.
    If you used the SRS:AdvancedInterface_WithBackendMapping or SRS:AdvancedInterface_WithoutBackendMapping form as a template, you can modify the fields in the Your Fields data fields sections.


    Do not delete or modify any other fields on these forms. BMC supports only changes to appearance items, such as the header, background, labels, and so on.

Where to go from here

You must now register the form.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.


  1. Todd Lazar

    In section 4a it says to open the packing list created in Dev studio, etc

    However there is nothing in the documentation that talks about this packing list, how to create it, what the content is and how you have to overlay all of the objects first 

    Oct 06, 2014 08:55
    1. Catherine Siderine

      Thanks for your comment, Richard. I have created an internal tracking record to update this documentation as soon as possible.



      Oct 15, 2014 02:57
  2. Abdul sarkar Shaik

    The document is not updated yet...!

    Aug 11, 2016 11:47