PPM Purge-Tool Entity Type field not active

Working with customer to use the PPM Purge-Tool for the first time. PPM v10.02

  1. Installed tool on local windows desktop with access to the PPM database
  2. Configured and connected to UAT DB.
  3. Initial Run
    1. Criteria: Request
    2. Entity Type: some_request_type
    3. Status: Checked All
    4. Date Before: 2011-01-01
    5. Went to Pre-Processing, didn't like the results so decided to create a different criteria
  4. Run #2
    1. Criteria: Request
    2. PROBLEM is the Entity Type and Status fields are no longer active, can't get dropdown list to appear. Just get a red circle with a line through it when attempting to click on field. (See screenshot).

Troubleshooting Steps:

  1. Removed tool and re-installed
  2. Configured and connected to UAT DB.
    1. Same results.
  3. Switched from Chrome to MS Edge
    1. Same results
  4. Dropped all DB Objects created by purge-tool.
  5. Removed tool and re-installed
  6. configured and connected to UAT DB
    1. Same results.

I assume the tool is reading the request_types table to get the list of Entity Types on the fly. The tool seems to be able to collect the DB statistics each time so I believe the connection is still good. The fields are gray and not editable so it's not just an empty drop down list. The field just isn't active now.

Not sure what else to try. Any suggestions?

Thanks,

Rich

Tags:

  • 0  

    Hello guys,

    This is Kevin from R&D.

    I can't reproduce the issue in R&D lab

    1. Try to clear the browser cache and re-try it.
    2. If the issue persists ,please get the json file when access the localhost:9999/.../purgeCriteriaResource ,replace your URL
    3. Get the HAR file when click "Run PPM Purge Tool"

    Could you please submit a support ticket .

  • Verified Answer

    +1   in reply to   

    Problem solved. 

    Started the browser Inspect tool and then clicked on the "Run PPM Purge Tool"

    Observed purgCriteriaResource network request was in a pending state.

    I expected it to timeout and report an error. Instead after 2.8 minutes it completed and the Entity Type field became active and available to edit. The json in the response was 1.4mb. 

    Conclusion: It may take a very long time (several minutes) to load the criteria resource data. The network request will remain in a "Pending" state while the query is running.