CA Service Management

  • 1.  Catalog Request filter

    Posted Nov 23, 2018 02:22 AM

    Hi Team ,

     

    We have following filters for catalog request :

     

    --> Stuck at approved
    --> Stuck at Queued
    --> Stuck at Submitted
    --> Stuck at SPAdmin
    --> Stuck at Pending fulfillment
    --> Stuck at Pending fulfillment (Report an Issue)
    --> Stuck at fulfilled
    --> Stuck at pending approval >21 Days

     

    we want to generate a report for the same. . 

     

    please help us automate , if you could help me with SQL command or any out of the box catalog feature which can help me automate these . 



  • 2.  Re: Catalog Request filter

    Broadcom Employee
    Posted Nov 23, 2018 08:36 AM

    Good Afternoon Kunal.

    Approved - Status = 800 Approved
    Queued - Status = 5000 Queued
    Submitted - Status = 200 Submitted
    Pending fulfillment - Status = 1000 Pending Fulfillment
    Pending fulfillment (Report an Issue) - unknown status code
    Fulfilled - Status = 2000 Fulfilled
    Pending approval >21 Days - Status = 400 Pending Approval

    I assume you want on overview of requests with the above mentioned status:
    You could execute the following query against the mdb database:
    select the requests with status and their subscription(s) with status:
    Select ur.status as request_status,usd.status as subscription_status ,ur.request_id,ur.name
    FROM usm_request ur, usm_subscription_detail usd
    where usd.request_id=ur.request_id and usd.status <> "The status code of your choice"

    Kind regards, Louis.



  • 3.  Re: Catalog Request filter

    Posted Nov 26, 2018 08:17 AM

    thanks for your help , query worked for me . however could you help me with below filter :



  • 4.  Re: Catalog Request filter
    Best Answer

    Broadcom Employee
    Posted Nov 26, 2018 08:21 AM

    Good Afternoon Kunal.

     

    An idea to get to the query used internally is:

    1. Set the view.log in TRACE mode

    2. Execute the search as shown in your screenshot

    3. Set the view.log back in INFO mode

    4. Check the view.log for the query details

     

    Kind regards, Louis.