This documentation supports the 20.02 version of Remedy Action Request (AR) System.

To view an earlier version, select the version from the Product version menu.


Listing filters and escalations by using the Like Operator Object Identifier utility

Use the Like Operator Object Identifier utility to list all filters and escalations where the LIKE operator is used without a wildcard in the Run If qualification. This utility is available in the artools folder. You can use this utility to identify and list the workflows that contain the LIKE operator that is used without a wildcard.

The wildcard symbols are interpreted as wildcards only when they are used with the LIKE operator. Otherwise, they are interpreted literally. Conversely, when the LIKE operator is used without the wildcards, the LIKE operator functions like an Equal To (=) operator. This utility provides you with the list of objects. As a part of post-deployment tasks, you must use this utility and then check and correct those objects. Otherwise, you might lose your customizations or experience breaking of business logic.

Before you begin

  • Make sure that you go to the artools directory and then set the JAVA_HOME path to C:\Program Files\Java\<jre version> in the Command prompt.
  • Make sure you log on to BMC Communities and download the objectswithoutwildcardinlike.zip file on your system.

To run the utility

  1. Navigate to the directory where you have downloaded the objectswithoutwildcardinlike.zip file and then extract the ZIP file.

    Important

    (Windows) Run the objectswithoutwildcardinlike.bat file.

    (Linux) Run the objectswithoutwildcardinlike.sh file.

  2. Edit the objectswithoutwildcardinlike.bat file or objectswithoutwildcardinlike.sh file to specify the path to the artools directory where you downloaded the ZIP file.

  3. Run the utility.

    For example:
    C:\Program Files\BMC Software\ARSystem\artools>objectswithoutwildcardinlike

Parameters used

The following table describes the parameters that you can use with this utility:

ParameterDescription
-uSpecify the user name that identifies the user account for the AR System server.
-pSpecify the password for the user account. If the user account has no password, use -p "".
-aSpecify the name of the external authentication string or Windows NT domain. This is related to the Login window's Authentication field. See Authentication String Alias introduction.
-xSpecify the name of the server to connect to.
-tSpecify the TCP port number to connect to. If the port number is unknown, use -t 0.
-timeout

Specify the timeout period for connecting to the server. You can specify Normal, Long, and XLong seconds after which the timeout occurs. Use the following format to specify the timeout values:

-timeout Normal:Long:XLong

Important

You must specify all three values even if you want to set one timeout value.
For example, if you want to set the Long timeout value to 400 seconds, use -timeout 120:400:1800.

-fSpecify the location to create the file containing the list of objects having no wildcards in the LIKE operator.

Example

Output

The objectswithoutwildcard.txt and objectswithwildcard.txt files are generated in the directory that you provided in the -f parameter. These files contain the lists of all filters and escalations with the LIKE operator without a wildcard and with a wildcard, respectively.

Important

This utility provides you with the list of objects. Make sure that you check those objects and then correct those objects.

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

Comments

  1. Jason Miller

    Looks like an interesting utility. I am not seeing in the documentation why it matters if a LIKE is used without a wildcard. The page that describes the wildcard operator does indicate LIKE is used with a wildcard but it is just kind of glossed over without any detail.

    I imagine many people that develop in Remedy may not understand why this is important. It must be important since there is a tool to find these cases but what are the details and issues these cases cause? It can't be assumed that all people performing Remedy development are developers. Many people have Remedy dropped in their lap and need to learn (Remedy, databases, web applications, web servers, etc.) as they go.

    If this is documented someplace, there should be a link to that page here.

    Sep 27, 2020 11:35
    1. Onkar Telkikar

      Hello Jason,

      Thank you for your feedback on the documentation.

      We have added the following information to this topic:

      The wildcard symbols are interpreted as wildcards only when they are used with the LIKE operator. Otherwise, they are interpreted literally. Conversely, when the LIKE operator is used without the wildcards, the LIKE operator functions like an Equal To (=) operator. This utility provides you with the list of objects. As a part of post-deployment tasks, you must use this utility and then check and correct those objects. Otherwise, you might lose your customizations or experience breaking of business logic.

      Regards,
      Onkar

      Oct 01, 2020 06:19
      1. Jason Miller

        Thank you very much!

        ...And oh my... I didn't even know all of those details. Is this a newer (9.x Java rewrite) behavior? For years (v4.x to v8.x) I have seen wildcards used with the Equal operator as wells as LIKE operator without a wildcard.

        Oct 01, 2020 09:00
        1. Onkar Telkikar

          Yes, this is a newer behavior that is introduced in version 20.02.

          Thanks,
          Onkar

          Nov 11, 2020 02:34
      1. Stefan Hall

        and who cares about the OOB BMC filters with the wrong usage, such as: SHR:LHP:Svc_CheckGlobalSearchPermssion_SRM

        Jan 04, 2021 08:16
        1. Onkar Telkikar

          Hello Stefan,

          We checked the SHR:LHP:Svc_CheckGlobalSearchPermssion_SRM OOTB filter, which already has a wild card character. Therefore, there's no need for any modification by the Like Operator Object Identifier utility. This utility checks and corrects only those workflows and form field qualifications in which a user hasn't inadvertently used a wild card character for the LIKE operator.

          Thanks,
          Onkar

          Jan 07, 2021 08:16
  2. Peter Ekendahl

    Firstly I would assume that filters in objectswithwildcard.txt does not need to be handled at all? The utility lists 1009 ootb objects...

    Secondly, regarding objectswithoutwildcard.txt, the utility only lists 14 ootb objects. Are we suposed to overlay these and correct them - or are the instructions on this page only meant for custom and overlaid objects?

    Oct 15, 2020 09:36
    1. Onkar Telkikar

      Hello Peter,

      Yes, filters in "objectswithwildcard.txt" do not need to be handled at all.

      The BCT hotfix for ITSM can fix the OOTB filters.

      Thanks,
      Onkar

      Nov 16, 2020 07:43
  3. Scott Skeate

    Is this BCT hotfix after the 20.08 release or any subsequent release? Is it included in 20.08, Included in the on premise patch 2 for 20.02 that came out with 20.08? Or something that needs to be requested from support?

    Jan 07, 2021 11:29
    1. Onkar Telkikar

      Hello Scott,

      Thank you for your comment on the documentation. We are working on your questions.

      Regards,
      Onkar

      Jan 22, 2021 07:14
      1. Onkar Telkikar

        The BCT hotfix is included in the 20.02 Patch 02 of Remedy ITSM Suite (on-premises) and further releases. The BCT hotfix is applied to make your Remedy ITSM applications (which are on version 20.02 or earlier) compatible with Remedy Platform version 20.02.02.

        Thanks,
        Onkar

        Jan 25, 2021 12:14