A persistent object is an object instance that was saved from a requestor's clipboard into the PegaRULES database. It can be accessed and used by others requestors and remains in the database after the requestor session ends.

The Obj-Save and the Commit methods store instances in the PegaRULES database. Generally, pages can become persistent when they belong to a concrete class, have a non-blank key defined, and have passed validation.

Through optional Initialization/PersistRequestor settings in the prconfig.xml file, you can cause all the pages in the User Pages group of the clipboard that have not yet been saved to the PegaRULES database to be saved by a background process known as the passivation daemon.

For example, if your session times out, your clipboard state — excluding system-maintained pages — can be saved for later reuse.

	passivation, PegaRULES database, user page, validation
	Obj-Save method Commit method Understanding passivation and timeouts

Definitions — P