When a Dialog Appears

Sometimes a CAD command pops up a dialog box that waits for a button — a Vault prompt, an “update the assembly?” question, a check-out confirmation. CoPilot notices these, handles the ones it (or you) already know the answer to, and asks you about anything unfamiliar instead of freezing.

Why this matters

A modal dialog blocks the CAD application until a button is pressed. Without help, a command that raised one would simply hang. CoPilot watches for these dialogs while it works, so a request never silently stalls: it either deals with the dialog or comes back to you with exactly what it says and asks what to do.

What happens when one appears

  1. A rule you saved runs first. If you have told CoPilot how to answer a particular dialog before, it applies your choice immediately and notes what it clicked in its reply.

  2. A few well-known dialogs are handled automatically. For example, an SW PDM check-out confirmation is confirmed so the operation proceeds. These built-in defaults are always overridden by a rule you save.

  3. Anything else comes back to you. CoPilot reports the dialog’s title, message and buttons and asks which to click — it will not guess on an unfamiliar dialog. Once the dialog is closed it re-checks the model, because the interrupted command finished in the background and its outcome needs confirming.

Telling CoPilot what to do

You are always in charge. When CoPilot asks about a dialog, just answer:

Click No

And if it is a dialog you will see again, ask it to remember:

Always answer No to that Vault prompt from now on

Your standing rules are saved with your settings, take effect immediately, and always take priority over the built-in defaults. You can scope a rule to answer only a specific dialog, or tell CoPilot to never touch a particular one and always ask you.

CoPilot never enters passwords, license keys or credentials into a dialog, and it leaves error messages and login prompts for you. It only clicks ordinary confirmation buttons — and only the ones a rule covers or you have chosen.

Handy phrases

Is there a dialog open in the CAD right now?
Close the open dialog by clicking Cancel
Whenever the “update the assembly?” box appears, click Yes

Worked example: opening a file that pops several dialogs

Opening an assembly can raise a chain of prompts — a project-scope warning, a “files missing from workspace” Vault question, an “update the assembly?” box. Ask CoPilot to open the file and it will surface each one it does not already have an answer for. Tell it what to do (“cancel the project-scope prompt”, “yes to the update”), optionally add “and remember that,” and it works through the chain and confirms the assembly is open.

See also