We just upgraded our server to 6.5.3. There is a scheduled agent that creates documents in the database. One of the fields on the document takes the @Username to do a lookup to another database. It appears that prior to the 6.5.3 upgrade, the @Username was not the signer of the agent; it appears after the 6.5.3 upgrade, the @Username is the signer of the agent. Can anyone confirm that this is new behavior for Release 6.x.