Your issue looks very similar to an issue one of my customer's reported recently.
When I inspected Fiddler data I found out that HTTP data showed BAD REQUEST
GET /secureapp/sip0/prweb/PRServlet/Fy7qvZgNMHTyvpO5QpamzVzLO2IEH_g-*/webwb/zutilities_harness_13303042646.js!pzdesignviewutils_11680242374.js!Failed%20to%20resolve%20rule%20file%20Rule-File-Text.webwb.pzharnessruleformutils.js!!.js HTTP/1.1
This request is issued from the response that is assembled when a harness ruleform is opened/created -
Can you capture Fiddler data in your scenario and check if you suffer from the same problem?
If yes, then check whether pzharnessruleformutils.js exists on your system where you experience the problem. On my customer's system it did not hence causing the reported problem.
Sunny and Phani, Thanks for taking time on this issue.
I am seeing same bad request when Fiddler is used.
GET /prweb/PRServlet/8pYz9onlp1qxMYOty2YodQ%5B%5B*/webwb/zutilities_harness_13303042646.js!pzdesignviewutils_1374457409.js!Failed%20to%20resolve%20rule%20file%20Rule-File-Text.webwb.pzharnessruleformutils.js!!.js HTTP/1.1
pzharnessruleformutils.js doesn't exist in my system. However, I don't see pzharnessruleformutils.js file in another application where we don't have this issue..
There are two approaches to resolving the problem -
- the quick one where you export the rule from a system that has the rule into the system where you experience the problem. This is how my customer chose to resolve the issue because it was blocking development for him.
- the second one where you get help from PegaSupport through your SR to determine the correct root cause first. This could be tricky and time consuming.
In my customer's case, he claimed all he did was "skimming' after which he saw the rule go missing. But I wasn't able to prove it locally nor was the customer able to justify this with evidence.
My theory is that somehow a rule that was supposed to be installed during the upgrade was missed, hence resulting in the reported problem.
You may want to do a ruleset/version counts between environments to see if you are missing more than 1 rule.
We are facing the same issue in our application which is in 7.1.7 (Harness design tab not loading). Just a few weeks back we worked on this harness and found no issues with it. But suddenly we are getting this issue, no code migrations happened in the meanwhile.
Also I checked for the js file pzHarnessRuleFormUtils in one of our higher app environments, although the file not present but still harness is loading correctly, so I guess this issue is not related to this file not being present?