ARCHICAD 18 contains several developments that aim for a more robust and reliable Teamwork experience. For example, performance improvements with the embedded library. Some of these result in workflow changes, please find information about them here.
With ARCHICAD 18:
- You need to reserve Hotlinks and XREFs to update them, or when placing a new instance of an existing hotlink. The Hotlink Manager dialog now has the usual reservation interface.
- Breaking Hotlinks or binding XREFs is not possible in Teamwork anymore.
- There is a new command to “Explode” a Hotlink. It is similar to “Break”, but does not keep the associated dimensions and SEOs.
- In solo files it is still possible to break Hotlinks. For example when you are archiving a project with save as PLA, you have an extra option to break Hotlinks.
- You can now relink instances of Hotlinks. Previously only whole modules could be relinked.
- You can now save a file from a Hotlink instance from the “Module Settings” dialog.
These affect the previously common workflow to make small adjustments to placed hotlink modules. That was (ARCHICAD 17 and before):
- break the Hotlink,
- make the changes,
- select elements,
- “save selection as module”.
The recommended workflow in ARCHICAD 18 is to:
- select the hotlink instance and open module settings dialog,
- “save as file”,
- open file in separate ARCHICAD and make modifications,
- relink hotlink instance to modified file.
When a library part is being saved with a name that has already been used, it will be automatically renamed by ARCHICAD.
Previously teamwork users got a warning to select a different name, but this also meant that others could not send and receive until renaming of the elements has finished.
Furthermore it is not possible to submit the modification of a single library part in the embedded library without submitting other modified parts. All the modifications will be sent in one go.
View and Layout Reservation
In ARCHICAD 18 when arranging views and folders in the View Map both the source and target folder has to be reserved by the user.
Previously it was possible to move a folder into another without reserving the target folder. This could lead to logical anomalies, e.g. one user moving folder A into B and another user moving folder B into A at the same time.