This documentation supports the 9.1 version of Remedy Action Request System.

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

Defining a package

A package is a set of workflow object definitions, data, or Service Request Management objects that you create in a development environment so you can promote the package across environments, such as QA or production.

To create a release package

  1. In the AR System Deployment Management Console, click Create from the Manage Package tab in the navigation pane to view the Deployment Package Information form.
  2. In the Deployment Package Information console, enter or select the appropriate data for the following fields:

    • Package NameThe unique name by which you want to create the package.

    • Package Version—The unique version number for the package.

    • Package DetailsA detailed description of the package.

    • (Version 9.1.04 and laterNotification EmailEmail address to receive email notifications about the status of your package. You can configure single or multiple email IDs (separated by semi colon) or, an email distribution list.

    • StateThe current status of the package.

    • StatusThe details describing the build status.

    • Status ReasonThe reason describing the current status of the package.

  3. On the Deployment Package Contents panel, enter the information in the following fields to add contents to the package.

    • Content TypeThe content that you want to add to the package. The following table describes the type of file that you might add to the package.

      Content Type Description
      Add Packing List

      Adds the packing list along with the contents from the BMC Remedy Developer Studio to the current package. For more information, see Adding a packing list to a package.

      Best Practice:

      BMC recommends using this option to add packing list to an application package.

      Add Definition

      Adds the objects to the current package. For more information, see Adding a definition file to a package.

      Also, enables you to add the following AR objects to an application package:

      • Active link guide
      • Application
      • Packing list
      • Filter guide
      • Webservice

      For more information, see Adding AR object to an application package.

      Delete Definition

      Adds a delete object command to the package. The referenced object is deleted from the environment where the package is deployed. For more information, see Deleting a definition file from a package.

      Add Data

      Adds data to the current package. A deployment manager can create a package using this content type. For more information, see Adding data to a package.

      SRM

      Adds Service Request Management objects, like service request definitions (SRDs), process definition templates (PDTs) and supporting data to the current package. You can also add custom advanced interface (AIF) forms and custom workflows. For more information, see Adding SRM to a package. A deployment manager can create a package using this content type.
      For more information on using the AR System Deployment Console to migrate BMC Service Request Management objects and data, see Migrating BMC Service Request Management objects and data .

      HRCM Adds solutions from BMC HR Case Management to the current package. A deployment manager can create a package using this content type. For more information, see Add HRCM Data to a package.

      (Version 9.1.04 and later)

      Application Object

      The Application object allows you to deploy tasks or task group templates efficiently and reliably across environments.

      For example, if you have a task or a task group template on your AR Server then you can relate that task template or task group template with any application, such as Change Management or Incident Management. A deployment manager can create a package using this content type.

      For information about adding an Application Object to a package, see Add an Application Object to a package.

      (Version 9.1.04 and later)

      Deployment Payload

      The Deployment Payload allows you to create and deploy binary payload across environments. Binary payload is a set of binary files, configurations files, batch or Shell scripts, and executable files. For information about adding a Deployment Payload to a package, see Add a Deployment Payload to a package.

      (Version 9.1.04.001 and later) Smart IT Definition 

      The SmartIT Definition offers to import or export the SmartIT customizations without making any changes in the code. For example, you can configure the provider action for a specific field for running the attached workflows without changing code. For more information about adding a SmartIT Definition to a package, see Add a SmartIT Definition to a package.

    • Content Description – The name of the content you want to add to the package.

    • Sequence – The sequence field is used to define the order in which the objects will be built, validated and deployed. This field is auto-populated based on the number of contents you add to the package. You can use the increment or decrement buttons to change the order of the contents.

    • Status – The current status of the contents added to the package.

    • Status Reason – The reason describing the current status of the contents added to the package.

  4. (Version 9.1.04 and later) (Optional) Click Manage Pre-Check to build qualification for the package. 
    For more information about Pre-Check, see Defining Pre-Check.
  5. Click Add, and then click Save.

To add a packing list to a package

BMC recommends using this option to add packing list to an application package.

  1. In the Package Details console, from the Content Type list in the Deployment Package Contents panel, select Add Packing List.

  2. From the Include Object Type list, select if you want to add Base onlyOverlay only or Both type of objects to the package.
    • Base only – Displays all the out-of-the-box objects.
    • Overlay only – Displays only the overlay and custom objects.
    • Both – Displays all the overlay and custom objects along with their base objects.
  3. In the Packing List Name field, enter the name of the packing list or click Search to select existing packing lists created in BMC Remedy Developer Studio. For more information, see Creating packing lists.

  4. Click Add.

To add a definition to a package

  1. In the Package Details console, from the Content Type list in the Deployment Package Contents panel, select Add Definition.
  2. From the Include Object Type list, select if you want to add Base onlyOverlay only or Both type of objects to the package.
    • Base only – Displays all the out-of-the-box objects.
    • Overlay only – Displays only the overlay and custom objects.
    • Both – Displays all the overlay and custom objects along with their base objects.
  3. Enter the information in the required fields:
    1. From the Type of Object list, select the required definition type.
    2. In the Name of Object field, enter the name of the relevant object.
      (Version 9.1.03.001 and earlier) You can also click Search to select object you created in BMC Remedy Developer Studio.

  4. Click Add.
    Version 9.1.04 and later, you can select multiple objects by clicking CTRL + Select.

To add AR object to an application package

  1. In the Package Details console, from the Content Type list in the Deployment Package Contents panel, select Add AR Definition.
  2. From the Type Of Object list, select Container.
  3. From the Include Object Type list, select if you want to add Base onlyOverlay only, or Both type of objects to the package.
  4. In the Name of Object+ field, perform the following:
    1. If you know the name of the object, type the object name and press Enter.
    2. If you do not know the name of the object, open the object search form by pressing Enter in the field.
    The RDA:DeploymentObjectSearch form opens.
  5. From the Type ofContainer list, select an option.
    The following options are available:
    • Active Link Guide
    • Application
    • Packing List
    • Filter Guide
    • WebService
  6. Click Search.
    The list of available objects is displayed. 
  7. Click Select.

The selected AR object is added to the application package.

To add a delete definition command to the package

  1. In the Package Details console, from the Content Type list in the Deployment Package Contents panel, select Delete Definition.
  2. From the Include Object Type list, select if you want to delete Base onlyOverlay only or Both type of objects from the package.
    • Base only – Displays all the out-of-the-box objects.
    • Overlay only – Displays only the overlay and custom objects.
    • Both – Displays all the overlay and custom objects along with their base objects.
  3. Enter information in the required fields:
    1. From the Type of Object list, select the required definition file.
    2. In the Name of Object field, enter the name of the object.
      (Version 9.1.03.001 and earlier) You can also clicSearch to select the object that should be deleted from the environment when the package is deployed.

  4. Click Add to delete the files from the package.
    Version 9.1.04 and later, you can select multiple objects by clicking CTRL + Select.

To add data to a package

  1. In the Package Details console, from the Content Type list in the Deployment Package Contents panel, select Add Data.
  2. Enter information in the required fields:

    1. From the Form Name list, select the name of the form from where you want to add the data or click Search to select the form.
    2. The items in the Data Qualification list are populated based on the form you select from the Form Name list.
      From the Data Qualification list select the fields that you want to add to build the qualification to select the data.
    3. (Version 9.1.03.001 and later) Select an option from Import Option field.
      Merge No Rollback
      Overwrite and Rollback
      Merge and Rollback
    4. Select the following options for Suppress Filters:
      • Yes: Suppress all the filters that are applied on the records.
      • No: Execute all the filters that are applied on the records.
    5. From the Duplicate Request Ids list, select an option.

    6. From the Match Duplicates By list, select the fields with which you want to find the duplicate records.
      Ensure that the fields selected from Match Duplicates By list are same to the fields selected from the Data Qualification list. If duplicate records are found, the action is taken based on the option you have selected in step d.

      Important

      When you select the fields from the Match Duplicates By drop-down list, the field IDs are separated by whitespace. This causes the import to fail and creates duplicate entries.

      Ensure that you replace the whitespaces by commas.

  3. Click Add.

To add SRM to a package

  1. In the Package Details console, from the Content Type list in the Deployment Package Contents panel, select SRM.
  2. To add Service Request Definition, perform the following steps:

    1. From SRM RequestType, select Service Request Definition.

    2. From SRD Name, select the existing SRD created in Service Request Management. For more information on creating SRD, see  Creating a standard SRD .

  3. To add Process Definition Template, perform the following steps:

    1. From SRM RequestType, select Process Definition Template.

    2. From PDT Name, select the existing PDTs created in Service Request Management. For more information on creating PDT, see  Creating a standard PDT .

  4. To add Supporting data, select Supporting data from SRM RequestType.

  5. Click Add.

To add HRCM to a package

  1. In the Package Details console, from the Content Type list in the Deployment Package Content panel, select HRCM.
  2. Enter the information in the required fields:
    1. From the HRCM Data Type list, select Solution. For more information on solution data type, see  Introduction to solutions .
    2. The items in the Data Qualification list are populated based on the form you select from the Form Name list.
      From the Data Qualification list select the fields to build an expression to retrieve the data that can be included in the package.
  3. Click Add.

To add an Application Object to a package

  1. In the Package Details console, from the Content Type list in the Deployment Package Contents panel, select Application Object.
    Type and Name fields are displayed.
  2. Enter the information about  the package in the Content Description field.
  3. From the Type list, select either Task Group Template or Task Template. The Name list displays all the  tasks or a task group templates that are available on the AR System server. 
  4. Click Add.

For more information, see  Migrating application objects by using BMC Remedy Deployment Application .

 To add a Deployment Payload to a package

  1. In the Package Details console, from the Content Type list in the Deployment Package Content panel, select Deployment Payload.
  2. Select Deployment Payload Group Name from the list.
  3. Click Add.

For more information about Binary Payload deployment, see Defining a custom binary payload.

 To add a Smart IT Definition to a package

  1. In the Package Details console, from the Content Type list in the Deployment Package Content panel, select SmarIT Definition.
  2. Enter the Content Description.
  3. Select the specific Object Type that you want to export.
    For example, select Screen with Contents to export screen configuration information.
  4. Select an appropriate option from the Overlay Type field.
  5. Click Add.
    The FND:SmartIT Layout Object Search Dialog box is displayed.
  6. Select the screen for which you want to export the configuration information. To export the information of specific fields, you must select the screen and the panel where the fields appear.
  7. Click Add; Save.

For more information, see  Packaging and deploying Smart IT customization and definitions

 Defining Pre-Check for a package

Starting from version 9.1.04, you can define Pre-Check for a package. Pre-Check is a qualification that runs before you deploy or rollback a package. Using Pre-Check, you can build or modify qualification for your package and can customize the error messages.

For example, if you have a hotfix for BMC Remedy AR System 9.1.02 and you try to deploy it on version 9.1.01, Pre-Check performs a validation and shows an error message.

(Optional) To create a Pre-Check

  1. Create a package using the Deployment Package Information form.
  2. Click Manage Pre-check.
    Deployment Package Pre-Check form opens.
  3. Select Pre-check Type from the following options:
    1. Deploy
    2. Rollback
  4. Enter Pre-check Name.
  5. Select Form Name from the Form Name field.
  6. Build Qualification.
  7. In the Error Message field, enter an error message that you want to display when the qualification fails.
  8. Click Add to add a Pre-Check for the package and click Close.

(Optional) To modify or delete an existing Pre-Check

  1. Click Manage Pre-check on the AR System Deployment Management form.
  2. Select an existing Pre-Check from the Deployment Package Pre-check list.
  3. Modify or remove the existing qualification in the Qualification field.
  4. (Optional) Click Modify to modify an existing qualification and click Close.
  5. (Optional) Click Remove to delete an existing qualification and click Close.

The status of the package on the Deployment Management console changes to Deploy Error when the qualification you have set in the Pre-Check fails.


Related topics

Creating and deploying a package using BMC Remedy Deployment Application

Using the AR System Deployment Management console

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Timothy Onyskin

    Question: I have a filter that I disabled in DEV and then created two new filters. If I have the deployment manager grab all three and then deploy that to QA, will it automatically disable the one filter that I disabled in DEV?

    Feb 21, 2018 08:39
    1. Anagha Deshpande

      Hello Timothy,

      I will check your query with the SME and will write back to you.

      Regards,

      Anagha


      Feb 21, 2018 10:52
      1. Anagha Deshpande

        Hello Timothy,

        Yes, the deployment manager takes the objects as it is from the development environment and then moves it to QA and then to the production environment. 

        Regards,

        Anagha

        Feb 21, 2018 10:01