3.2.1.3.3.2 Non-Persisted File Screen Template Instance

A Non-Persisted File Screen Template Instance is a type of File Screen Template (section 3.2.1.3.3), which has all the properties of a file screen template. A Non-Persisted File Screen Template Instance is a copy, in memory, of an instance of a Persisted File Screen Template (section 3.2.1.3.3.1), and it is used by a client to make changes to that Persisted File Screen Template. Changes, including deletion, that are made to a Non-Persisted File Screen Template Instance are either discarded after use or applied to the associated persisted file screen. There can be zero or more Non-Persisted File Screen Template Instances for each Persisted File Screen Template.

A protocol client can perform the following management operations involving Non-Persisted File Screen Template Instances:

  • Create or change the configuration data for a Non-Persisted File Screen Template Instance. See CreateTemplate (Opnum 7) (section 3.2.4.2.32.1) and Commit (Opnum 11) (section 3.2.4.2.10.5) for details.

  • Commit changes, including deletion, from a Non-Persisted File Screen Template Instance into the associated Persisted File Screen Template. See Delete (Opnum 10) (section 3.2.4.2.10.4) and Commit (Opnum 11) (section 3.2.4.2.10.5) for details.

The following configuration data is maintained for each Non-Persisted File Screen Template on the system:

DerivedFileScreenObjects: A collection of derived objects that were updated as a result of the File Screen Template's call to CommitAndUpdateDerived.

DerivedFileScreenResults: A collection of HRESULTs for committing derived objects that were updated as a result of the File Screen Template's call to CommitAndUpdateDerived.