iLogic and Automation Flashcards
7 cards from real ACP practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 iLogic and Automation flashcards as text
Which event trigger is best for making sure iProperties are filled in every time a user saves a part?
Answer: Before Save Document
Before Save Document runs the rule just before the file is written, so the iProperties are saved with the file.
Which statement turns the user parameter Length into a multi-value list of 100, 200, and 300?
Answer: MultiValue.SetList("Length", 100, 200, 300)
MultiValue.SetList replaces the parameter's allowed-value list with the values you pass in.
What is iTrigger used for?
Answer: It adds a user parameter that, when changed, runs the rules that reference it
Clicking iTrigger creates or increments the iTrigger0 parameter, which runs any rule that references it.
In an assembly rule, which statement suppresses the occurrence Bolt:1?
Answer: Component.IsActive("Bolt:1") = False
Component.IsActive set to False suppresses the named occurrence, while Component.Visible only hides it.
Which method returns the current document's file name without its extension?
Answer: ThisDoc.FileName(False)
ThisDoc.FileName(False) leaves the extension off, and passing True keeps it.
Why do experienced users often rename assembly browser nodes before writing iLogic rules?
Answer: Stable, meaningful names stop rules from breaking when default names such as Part1:1 change
Rules refer to occurrences by browser name, so stable custom names keep references valid when parts are replaced or rearranged.
What does an iLogic global form do that an internal form does not?
Answer: It is saved outside the document and can be used with any open document
Global forms are saved as XML outside the model and are available in every document, while internal forms are stored inside a single document.