Support Article
A page is submitted twice after passivation is completed
SA-55703
Summary
A page is submitted twice after passivation is completed. This page has messages on a property.
This does not occur if on running the tracer.
Error Messages
Not Applicable.
Steps to Reproduce
- Create a simple test activity and set a message on a property,TestA using Property-Set-Messages
- Create a harness containing a section with another property, TestB
- Add an action which refreshes the section and calls another activity. The activity that runs before the refresh should set the TestB property with information regarding the message on the TestA property. It should first check hasMessages on the step page and record the result. It should then obtain the message and should again check hasMessages and record the result. The hasMessages value is true before and after referencing
- Wait for passivation to occur. The hasMessage value is false before the referencing and true after referencing
Root Cause
A defect in Pegasystems’ code or rules. The @hasMessages() function returns false after passivation even though a property on the page does have messages. However, since the @hasMessages() function returns false, the messages are not cleared. This eventually results in application returning the same page to the user which submits the page twice.
Resolution
Apply HFix-42661. This is only applicable to an environment running on databasestorageversion with a value of 6. To identify this value, check the Dynamic System setting 'database/storageversion'.
Published August 24, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.