Question

Declare Trigger Not Catching Saves of System-User-Recents

Because PRPC does not catch the sign-off time of a user if they do not use the 'log out' button, we have a requirement to capture the time of the user's last action as their 'log out time'.

To do this, I made a declare trigger rule in the System-User-Recents class, and when an instance is saved it should launch an activity that fetches the user record for the recent and update the logoff time to the current time.

However, after checking out and in several rules arbitrarily and generating several entries in the recents table, I see that my trigger is never firing. Can declare triggers not see recents being saved?

***Updated by moderator: Lochan to update Categories***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

February 1, 2017 - 5:11pm

Hello ,

You can follow below steps to trace the declare trigger .

Using the Tracer, you can watch the evaluation of a Declare Trigger rule if the Execute field value is Immediate:

1.     Start the Tracer and select a requestor session.

2.     Click the Options button (Options) and check the Declare Trigger box in the Event Types to Trace section.

3.     Select the RuleSet that contains the rule to be traced.

You can follow below article to find more

https://pdn.pega.com/sites/pdn.pega.com/files/help_v722/procomhelpmain.htm#rule-/rule-declare-/rule-declare-trigger/related.htm

Thanks,

Arun

 

February 2, 2017 - 10:08am

Hey there, Arun!

I appreciate your response, but I've already added declare trigger to the list of events to trace and have been tracing all rulesets; the declare trigger still never seems to fire off.

Pega
February 2, 2017 - 2:23pm
Response to AaronP75

Can you show a screenshot of your trigger?

February 2, 2017 - 3:02pm
Response to AaronP75

Aaron,

I'm not familiar with what you are trying to fire the trigger off of, but there are ways to tell the system not to fire declaratives. The easiest way is to have, on the Security tab of an activity, a Usage of type onChange. You might want to confirm that something like that isn't happening. 

Thanks,

Mike