Can you please suggest for below questions regarding Standard Agent.
1. Does the method “Queue-For-Agent” stores snapshot of step page (ex: pyWorkPage ) in “pr_sys_queue” table? if yes please help with table column name.
If not, then please suggest, how primary page contents are available in agent activity during processing.
2. As per PDM regarding AQM “When AQM is enabled, then when a queue entry is retrieved for processing by the agent activity, the system locks that entry until a commit or rollback occurs at the end of processing.“
Do we need to perform commit or rollback explicitly in agent activity (even if it is not required by business logic ) or it will be handled by system internally if no exception occurred during processing in agent activity.?
Thanks in Advance.
***Edited by Moderator: Pooja Gadige to add platform capability tag***
The Queue-For-Agent step will store the page name and handle of the step page. For example, if my step page is pyWorkPage and this page contains my work object R-79, I will see this work object handle stored in the queue item XML when I call Queue-For-Agent.
When the standard agent runs, the System-Queue-DefaultEntry.EstablishContext activity will run first and use the pyPageNames and pyInsHandles properties to open the item. Then my agent activity will run to perform the processing I configure.
You do not need to issue an explicit commit. You should see that handled by the standard agent processing. If you are updating any data on the item, make sure to issue an Obj-Save so it will be included in the commit. You can trace your agent with the DB Query event type selected to see the item being opened from the database and the commit occur at the end.