- Blog
- YouTube
p: 888.662.7238
Ideate, Inc. is a California-registered company
- Careers
- Support
- Site Map
- Privacy Policy
- Terms of Use
- ©2021 Ideate Software
Support
- Ideate BIMLink
- Getting Started
- Using Ideate BIMLink
- Working in Excel
- How to...
- Create NEW Elements
- Create NEW Types
- Use Ideate BIMLink for Quality Control
- Manage Key Schedule Data
- Manage Sheet-based Revisions
- Manage Project Standards
- Set Up Projects
- Utilize Type Swapping
- Manage Calculated Values within Tags
- Leverage Linked File Data
- Assign Space Types
- Construction Tasks
- Use Ideate Sticky with Ideate BIMLink
- Video Examples
- Customization
- Troubleshooting
- Ideate Explorer
- Getting Started
- Explore Revit Warnings
- Ideate Explorer Basics
- Ideate Query
- BIM Managers
- How to...
- How Do I Delete a Hidden DWG?
- How Do I Purge Imports?
- How Do I Export to Excel?
- How Do I Use Explorer to Swap Types?
- How Do I Manage Worksets?
- How Can I Create a Custom Filter?
- How Can I Use Ideate Query for Quality Assurance?
- How Do I Delete ALL Identical Instances?
- How Do I Search by a Parameter Revit Value with Ideate Explorer?
- Video Examples
- Customization
- Troubleshooting
- Ideate Sticky
- IdeateApps
- Ideate StyleManager
- Ideate Automation
- Ideate Software Platform
- Licensing
- Download Latest
Configure Ideate Automation
The settings cog, which is found to the left of the help menu under the titlebar, opens the Options dialog which controls two key aspects of how Ideate Automation works. The values saved within this dialog are saved in a text file called: C:\Users\[username]\AppData\Local\Ideate\Settings\AutomationQueue.settings.
Library Paths
This setting determines what task scripts to show be default when creating a task. This setting supports multiple values, seen in the setting file as listing the setting multiple times. The contents of a setting file are loaded as a set. If no setting exists, the next file is read. If one exists the next file is not read.
Publish
This setting sets the location where the logs for completed tasks are stored, preserving them beyond the execution of the next task.
