PRPC 7.2: steps gone missing
Getting some weird behavior from 7.2, and I'm wondering if anyone else has seen it or knows how to recover from it.
I somehow managed to delete all the steps from an existing process. (I think what happened is I accidentally clicked next to the process name, thinking it would give me a drop-down, but instead it deleted it and all the accompanying steps. I then closed without saving, since there's no undo, in the process losing some work I had previously done on a step. When I re-did the work on the step and then saved, the steps seemingly vanished.)
Even weirder, and what makes me think this is a bug rather than a feature: the "Add Step" button that's normally at the bottom of the stage/process/step list is also gone. So not only are my steps gone, I can't add any more. (See stage 2 below.)
Getting some weird behavior from 7.2, and I'm wondering if anyone else has seen it or knows how to recover from it.
I somehow managed to delete all the steps from an existing process. (I think what happened is I accidentally clicked next to the process name, thinking it would give me a drop-down, but instead it deleted it and all the accompanying steps. I then closed without saving, since there's no undo, in the process losing some work I had previously done on a step. When I re-did the work on the step and then saved, the steps seemingly vanished.)
Even weirder, and what makes me think this is a bug rather than a feature: the "Add Step" button that's normally at the bottom of the stage/process/step list is also gone. So not only are my steps gone, I can't add any more. (See stage 2 below.)
If I click on the process name, the process flow is still there, so the steps still exist in that capacity. I can view and even modify the flow. I can run the case and it gets to the steps, but it tells me no view has been created for the first step. I did create a view for this step, and its section still shows up in the app explorer, but I don't see how to re-attach it to the step.
So, questions: Where did my steps go, and why did the "Add Step" button go with them? How do I get them back? If I can't get them back and have to rebuild the whole stage, so be it, but then how do I re-attach the section/view to the step? Suggestions very much appreciated.
Pegasystems
US
In your diagram, not only is the "add step" gone, but I also see an hour-glass cursor, which suggests that maybe a script error occurred.
Can you please try enabling the announcement of script errors in the browser and bringing up the rule again, such that you see the hourglass and the lack of the expected "add step" instruction, and see if there is an associated script error.
If you do save-as on this case type rule, does the new one have the same behavior (both hourglass and missing "add step"?)
if you make a brand new case type rule without using save-as, can you do a similar scenario as before and make the issue occur again?
/Eric
CACI
US
I'm not getting any script errors upon opening the case type.
I tried to duplicate the case using save-as, and got an error:
| Status | fail |
| Message | There has been an issue; please consult your system administrator |
| Operator ID | [email protected] |
| Requestor ID | H3E905A7723A55994634515D43D42CBE2 |
| Timestamp | Mon Apr 11 16:45:49 EDT 2016 |
| Engine Version | PegaRULES 7.20 ML0 (coreAssemblyCached_72_868) |
2016-04-11 16:45:49,753 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] (l.library.LibraryMetadataCache) ERROR feldspar|200-users.caci.com [email protected] - Problem invoking function: pega_desktop_pxrulemanagement.pzPageCopyFromThread--(String,String,String)
2016-04-11 16:45:49,763 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] ( internal.mgmt.Executable) ERROR feldspar|200-users.caci.com [email protected] - Exception
I'm not getting any script errors upon opening the case type.
I tried to duplicate the case using save-as, and got an error:
| Status | fail |
| Message | There has been an issue; please consult your system administrator |
| Operator ID | [email protected] |
| Requestor ID | H3E905A7723A55994634515D43D42CBE2 |
| Timestamp | Mon Apr 11 16:45:49 EDT 2016 |
| Engine Version | PegaRULES 7.20 ML0 (coreAssemblyCached_72_868) |
2016-04-11 16:45:49,753 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] (l.library.LibraryMetadataCache) ERROR feldspar|200-users.caci.com [email protected] - Problem invoking function: pega_desktop_pxrulemanagement.pzPageCopyFromThread--(String,String,String)
2016-04-11 16:45:49,763 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] ( internal.mgmt.Executable) ERROR feldspar|200-users.caci.com [email protected] - Exception
2016-04-11 16:45:49,775 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] (l.library.LibraryMetadataCache) ERROR feldspar|200-users.caci.com [email protected] - Problem invoking function: pega_rules_utilities.getStackTrace--(Throwable)
2016-04-11 16:45:49,777 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] ( internal.mgmt.Executable) ERROR feldspar|200-users.caci.com [email protected] - Exception
2016-04-11 16:45:49,779 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] (l.library.LibraryMetadataCache) ERROR feldspar|200-users.caci.com [email protected] - Problem invoking function: pega_rules_utilities.getStackTrace--(Throwable)
2016-04-11 16:45:49,781 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] ( internal.mgmt.Executable) ERROR feldspar|200-users.caci.com [email protected] - Exception
2016-04-11 16:45:49,783 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] ( internal.mgmt.Executable) ERROR feldspar|200-users.caci.com [email protected] - Exception
2016-04-11 16:45:49,784 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] ( internal.mgmt.Executable) ERROR feldspar|200-users.caci.com [email protected] - Exception
2016-04-11 16:45:49,785 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] ( internal.mgmt.Executable) ERROR feldspar|200-users.caci.com [email protected] - Exception
2016-04-11 16:45:49,786 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] ( internal.mgmt.Executable) ERROR feldspar|200-users.caci.com [email protected] - Exception
2016-04-11 16:45:49,787 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] ( internal.mgmt.Executable) ERROR feldspar|200-users.caci.com [email protected] - Exception
2016-04-11 16:45:49,788 [fault (self-tuning)'] [TABTHREAD2] [ ] [ Contract:01.01.01] (ngineinterface.service.HttpAPI) ERROR feldspar|200-users.caci.com [email protected] - 200-users.caci.com: com.pega.pegarules.pub.PRRuntimeError
I have tried duplicating the problem with other stages/processes in this case, but so far I haven't been able to reproduce it. Tomorrow I'll try rebuilding the original stage/process and we'll see what happens.
CACI
US
I created a new stage, moved it over, set it up with the same steps as the original stage 2, and deleted the original stage 2. All well and good until I attempted to configure the first step. As soon as I modify the fields I get this:
I created a new stage, moved it over, set it up with the same steps as the original stage 2, and deleted the original stage 2. All well and good until I attempted to configure the first step. As soon as I modify the fields I get this:
if(pega_uiengine_offlinesupport.pzIsForOfflineTemplate()) { ** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ** pega_uiengine_offlinesupport cannot be resolved ** ---------- ** 2. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 236) ** 3. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 261) ** tools.appendString(pega_uiengine_formatter.pxFormatTrueFalse(pega_uiengine_pzcontrol.pzGetActiveValue((PegaStreamAPI)tools,true),"True","False",true,"text","",""));tools.appendString(" <label>"); ** ^^^^^^^^^^^^^^^^^^^^^^^ ** pega_uiengine_formatter cannot be resolved ** 4. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 261) ** ^^^^^^^^^^^^^^^^^^^^^^^ ** pega_uiengine_pzcontrol cannot be resolved ** 5. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 263) ** if("".equals(pega_uiengine_pzcontrol.pzGetActiveValue((PegaStreamAPI)tools,true)) && !"true".equals(tools.getParamValue("FORMAT_PLAIN_TXT")) && ((pzAuto.getBrowserUtils().isIE() && !pega_uiengine_harness.pzInStandardsMode()) || "true".equals(tools.getParamValue("fromAPI"))) ){ ** ^^^^^^^^^^^^^^^^^^^^^^^ ** 6. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 263) ** ^^^^^^^^^^^^^^^^^^^^^ ** pega_uiengine_harness cannot be resolved ** 7. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 313) ** tools.appendString(pega_uiengine_harness.pzConvertToRDLIndex(tools.getProperty(".InterestedParty").getEntryHandle(),"entryHandle"));} else{ ** ^^^^^^^^^^^^^^^^^^^^^ ** 8. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 319) ** tools.appendString(pega_uiengine_harness.pzConvertToRDLIndex(tools.getProperty(".InterestedParty").getEntryHandle(),"entryHandle")); ** 9. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 324) ** tools.appendString(propName.substring(propName.lastIndexOf(".")+1)+pega_uiengine_harness.pzConvertToRDLIndex(tools.getProperty(".InterestedParty").getReference(),"",true)+"' ");} else{ ** ^^^^^^^^^^^^^^^^^^^^^ ** 10. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 327) ** pega_uiengine_pzcontrol.pzAddClientValidation(tools,pyOnInput,pyEditValidate,pyStringType,pegaValidation.toString()); ** ^^^^^^^^^^^^^^^^^^^^^^^ ** 11. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 328) ** if(!bOptimizedMarkup && pega_uiengine_pzcontrol.pzGetActiveValue((PegaStreamAPI)tools,true).equalsIgnoreCase("true")){ ** ^^^^^^^^^^^^^^^^^^^^^^^ ** 12. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 334) ** 13. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 339) ** tools.appendString("</span>");pega_uiengine_pzcontrol.pzAddMessages(tools,"SIMPLELAYOUT"); ** ^^^^^^^^^^^^^^^^^^^^^^^ ** 14. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 357) ** cellPage.putString("pyValue","#~"+pega_uiengine_harness.pzConvertToRDLIndex(tools.getProperty(".InterestedParty").getReference(),"")+"~#"); ** ^^^^^^^^^^^^^^^^^^^^^ ** 14 problems (14 errors) ** Compile failed.
Test compilation failed: ----------
1. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 226)
if(pega_uiengine_offlinesupport.pzIsForOfflineTemplate()) {
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pega_uiengine_offlinesupport cannot be resolved
----------
2. ERROR in /Rule_HTML_Section_CACI_Contract_Work_Protest_EvaluateProtestorStatus_1_Stream_20160331T193605_766_GMT.java (at line 236)
if(pega_uiengine_offlinesupport.pzIsForOfflineTemplate()) {
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pega_uiengine_offlinesupport cannot be resolved
Pegasystems
US
When you say "made a new stage and moved it over", I assume you mean within the same case type rule that we already know is in an unknown state (blank steps and "add step" instruction missing).
If your goal at this point is more to move forward with your project, and less to know how the unknown state occurred, I think a conservative stance would be to use a new case type rule entirely rather than trying to fix up this one that is an unknown state.
Would it be easy for you to delete this case type rule and make a brand new one ? I guess it would depend on how extensive your customizations to this one have been. /Eric
CACI
US
I'm thinking that's the way to go--this case type now seems to be blowing up at every turn. I'm not TOO far down the road with it, and starting from scratch won't kill me.
It just worries me in case this happens again, if and when I do have several weeks of customization work in place.
Pegasystems Inc.
IN
Hi Carl, Good morning!
- not sure of the error...
- but could we double check if the case type is enabled with Offline processing under advanced tab of case type rule?
- and un-check if the case and learn the observations...
- but could we double check if the case type is enabled with Offline processing under advanced tab of case type rule?
Thank you!
psahukaru
Independent
NL
I have encountered the same problem: the steps as-defined are no longer available & visable in the life cycle. Though, they are when opening the process-flow where I had defined them. When testing, all works as designed. When saving get an error message: Process is stale.
Design Studio 7.2: works as designed or a bug? Is this something to be worried about?
Regards,