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

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

Push Fields action

Use the Push Fields action in:

  • Active links
  • Filters
  • Escalations

The Push Fields action enables you to automate updates to the database. You can transfer values from selected fields in the current request to another request in a different form or in the same form. The Push Fields action can update or create a request.

You can push values from all field types, including tables, hidden fields, fields not in the active view, or fields in no views at all. However, you cannot push values to non-data fields, such as table fields, column fields, and panel holders.
Each Push Fields action can push data from the current form to one other form, although you can update multiple requests in that form. To push data from the current form to more than one form, you must create a separate Push Fields action for each destination form.

To define a Push Fields active link, filter, or escalation action

  1. Right-click the If Action or the Else Action panel header.
  2. Select Add Action > Push Fields.
  3. From the Data Destination list, select SERVER or SAMPLE DATA:
    • To specify a specific server and form, select SERVER, and go to step a.
    • To determine the server and form at runtime, select SAMPLE DATA, and go to step b.
    1. (Data Destination is SERVER) Select the Server Name (active links only) and Form Name to push data to.
      Servers that appear in the Server Name list are those to which you are currently logged in. In the Form Name field, the forms that appear in the Form Selector dialog box are from the server specified in the Server Name field.
      Filters and escalations can push data only to forms on the server where the workflow is running.
    2. (Data Destination is SAMPLE DATA) Define the sample and runtime server and form names or values:
      • In the Sample Server Name (active links only) and Sample Form Name fields, select the sample server and destination form name to use to design the Open Window action.
      • In the Runtime Server Value and Runtime Form Value fields, identify the fields on the current form or the BMC Remedy AR System server keywords that will identify the destination server and form at runtime.
        For more information, see Using a dynamic data source or destination in workflow.
  4. In the Qualification field, enter a qualification, if any, to specify the request to which the Push Fields action will push the data.
    Click the ellipsis button to use the Expression Editor dialog box, or type the expression directly in the Qualification field. For more information about creating qualifications, see Using buttons and menu bar items to execute active links.
    • To select fields in the Expression Editor dialog box, first select either the current form or the destination form in the Form list. The list of Available Fields changes to display fields from the selected form.
    • As you build the expression, fields from the current form are delimited with dollar signs ($). Fields from the destination form are delimited with single quotation marks ( ' ).
    • To use content assist to build the expression, press Ctrl+Space to get a list of all possible choices. Alternatively, type a dollar sign ($) to get a list of fields from the current form and keywords. Type a single quotation mark ( ' ) to get a list of fields from the destination form.
      If you associated additional forms and want to use a field from a form other than the primary form, enter the appropriate field ID in the appropriate format, for example, '$ fieldID$' or ' fieldID '. The field must exist on the form.

      Note

      Using a qualification causes the Push Fields action to run a query to obtain the list of matching requests, so make sure to optimize the Push Fields qualification for best system performance. See Creating efficient qualifications.

    • To create a Push Fields action that does not search for existing records but instead always creates a request, do not enter a qualification. Instead, select the following values:
      • In the If No Requests Match field, select Create a New Request.
      • In the If Any Requests Match field, select Take No Action.
  5. From the If No Requests Match list, select an option to control how the system responds when no matches are found in the destination form:
    • Display 'No Match' Error — Returns an error message and stops processing.
    • Take No Action — Skips this action and proceeds to the next action.
    • Create a New Request — Uses the data specified in the Push Fields action to create a request.
  6. From the If Any Requests Match list, select an option to control how the system responds when multiple matches are found in the selected form:
    • Display 'Any Match' Error — Returns an error message and stops processing.
    • Modify First Matching Request — Pushes data to the first request that meets the qualification.
    • Modify All Matching Requests — Pushes data to every request that meets the qualification.
    • Take No Action — Skips this action and proceeds to the next action.
  7. Use the field mapping table to map the fields and values to push from the current form to the destination form as follows:
    • To use matching field IDs to map the values of all matching fields from the current form to the destination form automatically, select the Matching IDs option. The field mapping table is disabled, and you cannot select specific field mappings.
      In this case, all matching field IDs (except for table columns, panel holders, and core fields such as Modified Date and Request ID) are automatically set in the destination form from the values in the current form.

      Tip

      When you use Matching IDs, the values are dynamic. This means that only the setting is stored as part of the Push Fields action, and not the actual values. Therefore, you can add data fields to these forms at a later stage and the action uses them when executed.

    • To use the Auto Map dialog box, click Auto Map.
      The Auto Map dialog box opens with all matching fields entered in the list. To delete a field you do not want to update, select the field and click Remove. After making selections in the Auto Map dialog box, click OK.

      Tip

      You can use Auto Map to map fields according to the field name or field ID. When you use Auto Map with field names, the mappings are dynamic. However, when you use Auto Map with field IDs, the mappings are stored with the form. In this case, if you later add fields to the forms, they will not be part of the action and must be added manually.

    • To map specific fields and to use an expression to define the value, follow the steps described in Mapping fields to values.
      In the Field column, select the fields in the destination form to which the Push Fields action will push data. In the Value column, use an expression to define the values that the Push Fields action will push to the fields in the destination form.
      To define the value, you can use field values from the current form, keywords, static values, or the result of a function. In active links, you can also use the result of a DDE operation. For information about using the result of a function, see Assigning values using function results. For more information, see DDE action.
  8. Save the active link, filter, or escalation.

Using a dynamic data destination

To create a Push Fields action that uses runtime information to identify the destination server and form, specify SAMPLE DATA instead of SERVER for the data destination. At runtime, the field values are pushed to a server and form defined by workflow or selected by the user. See Using a dynamic data source or destination in workflow.

Note

Dynamic Push Fields actions cause browsers to perform extra HTTP fetches and cause the BMC Remedy AR System server to perform extra queries to determine the data types for remote fields. To enable the mid tier to fetch these data types ahead of time and avoid performance degradation, avoid using field references to store the server or form names.

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

Comments