Download Dependencies
  • 01 May 2024
  • 3 Minutes to read
  • PDF

Download Dependencies

  • PDF

You can define rules to download dependencies when working with files, managed folders and 12d Model projects. You can set rules such that when working with files of specified extensions, the related dependant files automatically get downloaded. For instance, when working with a .dwg file, you can set a rule that the necessary customisation files get downloaded.

Download dependencies is a way to automate performing a Get All function.

1.1. How to Set Up Download Dependencies

Your 12d Synergy Administrator will have to perform this setup to enable the Download Dependencies function. Let us look at the setup of this feature for .dwg files.  

  1. In the 12d Synergy Client application, navigate to the job for which you would like to create the rule in the Job Tree.
    If you want to create a download dependency rule for a managed folder or a 12d Model project, then just select the required managed folder or 12d Model project and follow the procedure mentioned below from points 10-12. 
  2. Right-click the job and select the Edit option.
    If the Edit option is not displayed, you will need to contact your 12d Synergy Administrator for the setup, or for providing you with the permissions to edit the job.

  3. Select the Rules tab > Download Dependency Rules tab.
  4. Click the button.
    The Add a Dependency Rule Set window is displayed.
  5. Enter a name for the new rule you are creating in the Rule Set Name box.
  6. In the Extensions tab, click the button.

    A New Extension placeholder box is displayed in the Extensions tab.
  7. Enter the extension of the files for which this rule has to apply. In this example, enter .dwg.

    For files that may have multiple extensions like Microsoft Word, ensure to enter both .doc and .docx as entries in the Extensions tab.

  8. Now that the trigger is set up, select the Rules tab to define the rule.
  9. Click the button.
    The Add Download Dependency Rule prompt is displayed.
  10. Enter a name for the Rule in the Rule Name box.
  11. In the Mode list, do one of the following:

    • Select the Download dependencies from a specific folder option and select a folder from the Select a folder window. The path to the selected folder is displayed in the Specific folder path: box. The files from this folder will be downloaded as dependencies to a selected trigger (.dwg file).
    • Select the Download dependencies from a folder via a relative path option and mention the relative path to the folder which contains the dependency data, in the Relative path to folder box. The path mentioned is relative to the folder from which data is being downloaded. (For example, if you mention a folder, ../Customisation, and try to download data (.dwg file) from a folder, say 04 CADD/ DWG, then the dependencies are downloaded from 04 CADD /Customisation folder.)
  12. Click the Add button.
  13. Click the Set button in the Add a Dependency Rule Set window.
    The rule is set. When you are working with a .dwg file, all files in the folder mentioned in the rule are downloaded as dependencies for the .dwg file.
    • In the 12d Synergy Administration application > System Settings tab > General tab, if the Download dependencies only once per session setting is set to Yes, then the dependencies are downloaded only when the trigger action occurs for the first time  in a session or until you restart the 12d Synergy Client application. In terms of the example we have seen in the above procedure, it means that the dependencies are downloaded only when a .dwg file is opened for the first time during a session. Subsequently, if you open any other .dwg files in that session, the dependencies are not downloaded as they are already downloaded onto the workspace before.   
    • In the 12d Synergy Administration application > System Settings tab > General tab, based on the value set for the Delete any file not found on the server or marked as deleted setting, files downloaded as dependencies and customization in the workspace but not on the server will be deleted from the workspace automatically.

Was this article helpful?

What's Next