Handling pop-up forms during a multirecord update

Your schema can display in the HCL Compass client pop-up forms that contain your own content or information. Examples of pop-up forms are forms that are opening a prepopulated, opening a browser to a URL, or opening a dialog box that contains a custom error message. If your schema uses pop-up forms, you might need to write your hooks so that they know when a multirecord update is in progress. The hooks can then avoid using pop-up forms during a multirecord update. This is the same behavior that a schema uses when the client program does not use pop-up forms.

The multirecord update operation clears GlobalScriptUtility package session variables to indicate that the Web client does not support pop-up forms. These session variables are clear only while multirecord update is directly operating on a record. If a pop-up form causes an error, an error dialog box is displayed, an error entry is logged on the Edits tab, and an error icon replaces the recording icon on the template record. You cannot save the changes that you made to the template record. You have to click Cancel on the template record.

A list of actions that you made remain on the Edits tab. You can copy the actions to the clipboard or a text editor and use them to record again.