Closed catalog request does not show in the closed tab in the service point

book

Article ID: 225862

calendar_today

Updated On:

Products

CA Service Catalog

Issue/Introduction

The closed catalog request does not show in the closed tab in the service point as below

Environment

Release : 17.3

Component : Catalog - Service Point/BUI

Resolution

I reviewed and compared the file within our inhouse environment. Please take a backup of the application.conf file as mentioned below and update the file accordingly and validate the behavior one again for the functionality i.e.

Checking application.conf in searchmicroservice/conf folder you can find:

    searchQueryInactive = """{
      "from":%d,
      "size": %d,
      "sort" : [
        { "open_dt": { "order": "desc" } }
      ],
      "query": {
        "bool": {
          "must": {
            "match": {
              "requested_for.id": "%s"
            }
          },
          "must_not": {
               "bool": {
                "should": [
                    {
                      "match": {
                        "request_name.asis": "-1"
                      }
                    }
                ]
              }
             },
            "must": {
               "bool": {
                "should": [
                    {
                      "terms": {
                        "status.code": ["2", "4"]
                      }
                    }
                ]
              }
             }
        }
      },
      "stored_fields": ["request_id",    "request_name",    "requested_by", "priority", "last_mod_dt", "open_dt", "resolve_dt", "status.code"]
    }""",

Note this above block seems to be incorrect.

Please update the entire block to:

    searchQueryInactive = """{
      "from":%d,
      "size": %d,
      "sort" : [
        { "open_dt": { "order": "desc" } }
      ],
      "query": {
        "bool": {
          "must_not": {
               "bool": {
                "should": [
                    {
                      "match": {
                        "request_name.asis": "-1"
                      }
                    }
                ]
              }
             },
            "must": {
               "bool": {
                "should": [
                    {
                      "terms": {
                        "status.code": ["2", "4"]
                      },

                    {
                      "match": {
                        "requested_for.id": "%s"
                      }
                    }
                ]
              }
             }
        }
      },
      "stored_fields": ["request_id",    "request_name",    "requested_by", "priority", "last_mod_dt", "open_dt", "resolve_dt", "status.code"]
    }""",

Once the solution is confirmed you can keep the updated application.conf file until a future RU, when the solution would be formally delivered.