More about Agents rules

Changes

After you save a modified agents rule, changes take effect only after the Agent Manager master agent updates the agent schedule instances. By default, the Agent Manager checks for new and updated agents rules (and manually updated agent schedules) every 10 minutes.

Agents are not authenticated requestors

Agents are not full, authenticated requestors. As a result:

• Agents do not have an associated organization, division, or unit.

• Agents cannot execute activities that have the Authenticate? check box (on the Security tab of the Activity form), unless the Bypass activity authentication check box (on the Security tab of the Agents form) is checked.

• Although the Agents rule form contains a Version, the Agent Manager does not use rule resolution to determine which version of an agents rule to run. The highest version always runs.

Testing and Troubleshooting

For information about testing agents, see Pega Developer Network article PRKB-21572 Troubleshooting agents.

Starting and stopping agents

Normally, all agents start each time you start your Process Commander system. Agents running on a specific node start as that node starts. For testing, or when otherwise necessary, you can use the System Management application to monitor or control agents:

1. Start the System Management application.
2. Select a node.
3. Select the Agent Management menu item.
4. Click a single radio button to identify the Thread of an agent. (Each agent activity executes in a separate thread.)
5. Use the buttons at the top of the page to start the agent, stop the agent, or pause agent processing. You can affect only the selected activity (one row of the form) or all activities.

	agent, assignment
	Agents overview About Agent Schedule data instances Property references in expressions About the System Management application
	Atlas — Standard Agents rules

About Agents rules