Share via

3.2.4.2.28.1 Commit (Opnum 11)

  • Article

The Commit method is implemented as one of the methods for the IFsrmObject interface (section 3.2.4.2.10). This method has the behavior specified in section 3.2.4.2.10.5 with the following additions:

  • If Allowed File groups is an empty list, the server MUST return FSRM_E_ALREADY_EXISTS.

  • If FSRM Base Object.Deleted is set to true for this Non-Persisted File Screen Exception Instance (section 3.2.1.3.2.2), the server MUST remove the Persisted File Screen Exception (section 3.2.1.3.2.1) from the List of Persisted File Screen Exceptions (3.2.1.3) that has the same File Screen Exception.Folder path as this Non-Persisted File Screen Exception Instance, if one exists. This removal MUST occur even if other changes were made to the configuration of the Non-Persisted File Screen Exception Instance. If there is no Persisted File Screen Exception in the List of Persisted File Screen Exceptions that has the same File Screen Exception.Folder path as this Persisted File Screen Exception being deleted, the server does not perform any action and MUST return zero. The server MUST return a nonzero error code if removal fails.

  • If FSRM Base Object.Deleted is set to false for this Non-Persisted File Screen Exception Instance, the server MUST update the configuration data of the Persisted File Screen Exception in the List of Persisted File Screen Exceptions that has the same File Screen Exception.Folder path as this Non-Persisted File Screen Exception Instance, if one exists, with the configuration data from this instance, or return a nonzero error code.

  • If a Persisted File Screen Exception does not exist with the same File Screen Exception.Folder path and with FSRM Base Object.Deleted is set to false, the server MUST create a new Persisted File Screen Exception, populate its configuration with the configuration from this Non-Persisted File Screen Exception Instance, and add the new Persisted File Screen Exception to the List of Persisted File Screen Exceptions.

To update or populate the configuration data from a Non-Persisted File Screen Exception Instance to a Persisted File Screen Exception, the server MUST assign the values of all the properties shown in the list that follows, of the Non-Persisted File Screen Exception Instance to the corresponding properties of the Persisted File Screen Exception.

  • FSRM Base Object.Description

  • Allowed file groups