It is impossible to achieve what you are aiming for based on the description provided. The second form and its content do not exist in the client context when attempting to validate data from the first form. There are three potential approaches to addressing this issue, but only two of them are practical.
Firstly, the impractical method involves having the pop-up form communicate back to its parent window using JavaScript variables, DOM elements, or cookies. Establishing a reliable relationship between the pop-up and opener can be challenging across different browsers. Additionally, there is no guarantee that the required data will be available when needed, especially if the parent document is edited. This approach risks inconveniencing users by prompting them to re-enter previously submitted information.
The second method entails querying the server to check if the pop-up form has been successfully submitted and stored as a Notes document. However, this solution lacks scalability and introduces delays, potentially resulting in user frustration from repeated validation requests.
Alternatively, the third method suggests consolidating all necessary actions onto a single form, with CSS utilized to create a visually distinct "pop-up" effect if desired. Despite requiring additional development effort, this approach ensures reliability and user satisfaction. Leveraging WQO and WQS agents allows for seamless integration of document components before presentation and storage, enabling efficient web functionality.