This topic covers how to relocate Ideate Automation content to a shared network location and how to deploy the new location to all end-users. When content is shared you can easily benefit from any customization done to that content. Additionally, this method can be used to provide greater focus by eliminating any discipline-specific content that may not apply to your work.
Ideate Automation ships with a library containing more than 30 script samples that can be used ‘out-of-the-box’ or as a starting point for automating a variety of Revit tasks. These samples are stored as small XML files with a .def extension and are stored by default at C:\Program Files\Ideate\Ideate Automation\en-US\Samples. You can learn about the purpose of each of these samples in the help topic called Sample Content.
In addition to the sample link content noted above, the home page content, which is stored at C:\ProgramData\Ideate\Ideate Automation can also be customized.
Both the library and home page content can be relocated to a network location to ensure tighter standards and ease of use within larger companies. If you copy this content to a shared network location, the next step is to set the content pathing so that Ideate Automation knows where to look for it.
The file pathing information for both the library and the home page content can be set from Settings dialog within Ideate Automation.
The Library Paths option allows for multiple paths, if so desired. This would allow for the original out-of-the-box content to be shown side-by-side with your custom content, for example. After the values have been changed to point to the new shared network locations, the last step is to push this change out as a standard for all users.
The values saved within this dialog are stored by default at %UserProfile%\AppData\Local\Ideate\Settings in a file called AutomationQueue.settings. This file can be pushed via group policy to the local user location or, if preferred, can be pushed to C:\ProgramData\Ideate\Ideate Automation. When the file is located within ProgramData it will be treated as a read-only location.
Thank you for taking time to inform us about a bug or feature request.