Summary

Rule resolution works differently for the agents rules, because agents are system-wide, rather than being enabled for a particular user. 

Suggested Approach

When the Agent Manager gets a list of Agents rules, the database returns the best version for each instance, using rule resolution.  If the highest version of rules on the system is 05-04-01, the Agent Manager sees only that version, so it runs the most recent version of the agents.

NOTE:  Multiple copies of an agents rule may be created in one RuleSet, but with different version numbers.  However, circumstances and date/time qualifiers are not valid for agent rules.

Developers on the system who don’t have access to the highest-numbered version of the RuleSets (05-04-01) in their profile will see an older version (05-02-01) of the Agents rule; they will not be able to see the new version of the Agents classes in Class Explorer, since they don’t have access.  The Agent Manager is not subject to user authorization issues, however, so it will use the highest-numbered version of the instances for each RuleSet on the system.

Example:  A system has three versions of the Pega-ProCom RuleSet:

• 05-04-02
• 05-04-01
• 05-02-01

When you double-click on the Pega-ProCom Agents rule in Class Explorer, you will see the rule you have access to, based on your RuleSet List (05-02-01).  When the Agent Manager gets a list of the instances, however, it will only “see” version 05-04-02.

NOTE:  Since the Agent Schedules are data instances (class Data-Agent-Queue) and data is not rule-resolved, you see all the Agent Schedules for the system (even if you don’t have access).