OpenDefault Rule Not Triggering in User Portal – Pega Constellation 25.1.1

User Experience
1

Hi Team,
In Pega Constellation 25.1.1, I have a requirement to trigger logic when a case is opened. I have configured this logic in an OpenDefault extension rule.

Issue:

  • When I open the case in the Dev Studio / Dev Portal, the OpenDefault rule triggers as expected.
  • However, when I open the same case in the User Portal, the OpenDefault rule does not trigger.
  • I have traced the execution and confirmed that the OpenDefault rule is not being invoked in the User Portal.

Is this expected behavior in Constellation (25.1.1) applications?
Are there any known limitations, differences in lifecycle handling, or root causes for OpenDefault rules not triggering in the User Portal?

2

@Zumry it is expected behavior…OpenDefault extension is not available in constellation app…what is the purpose of the logic you are trying to run when a case is being accessed?

3

Hi @Chunzhi_Hong, Thank you for the clarification.

Our requirement is to capture a case-level audit entry (for example, “[UserID] viewed this record”) whenever a user opens or views a case in Review Mode (read-only). We want to automatically create a case-level audit message indicating that the case was viewed.

4

@ZumryThis is correct OpenDefault is not triggered. There is similar rule pyUpgradeOnOpen but description of this rule clearly states that it shall be used for for upgrading inflight cases.

Requirement of creating an audit log basin on a fronted end event looks like a good use case for DX components that fires audit creation whenever the screen is open.

5

@Zumry let me check internally. pyUpgradeOnOpen migth be a miss. Documentation is not mentioning it as a good extension point for your use case.

If it run multiple times it means that you might need to implement inside it some logic to check if it was already run for given case, which makes that is not a solution for what you want to achieve.

6

Hello @Kamil Janeczek , Thank you for the clarification.

pyUpgradeOnOpen is triggered when a case is opened. I saved pyUpgradeOnOpen in our application layer and added the required logic to create an audit entry.

The audit entries are created successfully and work as expected in review mode. However, I am observing that multiple audit entries (six) are being created for a single case open instead of just one. I have attached a screenshot for reference.

Could you please review this behavior and advise on how we can restrict the audit creation to a single entry per case open?

Audit History Issue_0.docx (348 KB)