Automation Failure and Trusted LISP Deployment
A 15-person MEP firm repeats a weekly task: clean consultant drawings, rename 30 layers, purge unused blocks, set viewport scales, and publish 18 PDFs. One drafter built an action macro that works on their PC but fails on others with an unknown command error at the layer rename step. Another created an AutoLISP routine that edits layers but is not signed and is blocked by SECURELOAD. The firm also has a CUIx partial customization file with a custom ribbon tab that disappears after a profile reset. They want a maintainable solution before a 200-sheet campus project starts in two weeks. IT policy allows scripts and trusted LISP but prohibits unsigned executables.
1. Compare action macro, script, AutoLISP, and sheet set publish for this workflow, and recommend an approach.
Read the worked answer
An action macro replays a recorded command sequence and is sensitive to command availability, prompts, and the current workspace; the unknown command error suggests the layer rename step depends on a partial CUIx or a command that is not loaded on other PCs. A script is more portable but has no conditional logic. AutoLISP can handle layer mapping, error checking, and missing layers, but must be deployed and trusted. For this workflow, use AutoLISP for the clean, rename, and purge logic, a sheet set publish operation for the 18 PDFs, and keep a script only as a fallback. Test on two machines with different profiles and document the command sequence.
2. Why does the CUIx ribbon tab disappear after a profile reset, and how should the firm deploy it?
Read the worked answer
The ribbon tab lives in a partial CUIx that is loaded into the user's main customization file and saved in a workspace. A profile reset reloads the default main CUIx and workspace, so the partial file is no longer loaded. Deploy the tab through an enterprise CUIx or load the partial CUIx from a controlled network path at startup, then save the workspace into the deployed profile. Do not rely on each user's CUILOAD. Verify by resetting a test profile and checking that the tab returns.
3. What security and testing practices should be applied to the AutoLISP routine under SECURELOAD and the two-week deadline?
Read the worked answer
Place the LISP file in a network folder listed in TRUSTEDPATHS and set SECURELOAD to 1 or 2 according to IT policy; unsigned code outside trusted paths will be blocked. Have IT review and hash the file, keep it version-controlled, and test it on copies of three project drawings before the campus project. Add error handling so a missing layer or locked viewport does not stop the batch. Document how to remove the routine, and avoid loading it through acaddoc.lsp for every drawing if it is only needed for the weekly cleanup.