Below are the steps you need to follow for pushing issues on your federated models from Asite to 3D repo:

1. Once logged in to Asite, go to 'Projects' tab.

2. Right click on a project, select 'Settings', then select 'Configurable Attributes'.

3. Follow the steps to create a new configurable attribute of 'Textbox' type.

4. Once the new attribute is created, create an attribute set by selecting the newly created attribute and apply it on one or more project folders (which contains the model files added to the federated model from which issues are to be pushed).

5. Configure a custom object system task for executing the groovy script in the relevant project. Here, use the groovy script to push issues on a federated model to 3D Repo as required.

If required, you can also include this system task while creating a new workflow for custom objects, so that the progress of workflow on selected issue can be tracked separately while viewing it.

6. Configure a custom object workflow trigger in the same project. This workflow trigger is meant to be configured in a way that the system task or the workflow created as per above step can be triggered upon 'Create Custom Object' event in 'Post' task mode.

7. Configure another custom object workflow trigger in the same project. This workflow trigger is meant to be configured in a way that the above system task or the workflow which includes the above system task can be triggered upon 'Update Custom Object' event in 'Post' task mode.

8. Open 3D Repo. Select existing federated model or create one as needed.

Once you open the model, there will be a model id in the URL.

Example: https://www.3drepo.io/v5/viewer/Asite_internal/2ba59ca8-5ee7-482f-9056-cae74630e70e/92a3fdc0-0ce4-4c83-86ca-e726ac9646e4

Copy and paste the model id you see for your model (“92a3fdc0-0ce4-4c83-86ca-e726ac9646e4” as per above example) in the highlighted portion of the groovy script as shown below.

String teamSpace="Asite_internal";

String apiURL="https://www.3drepo.io/api";

String apikey="Enter_API_Key_here";

String modelId="Enter_Model_ID_here";

For String apikey “”

Click your user icon in 3D Repo, edit your profile, then go to integration tab which contains the API key.

Copy and paste the API key you see for your 3D Repo account in the highlighted portion of the groovy script as shown below:

String teamSpace="Asite_internal";

String apiURL="https://www.3drepo.io/api";

String apikey="Enter_API_Key_here";

String modelId="Enter_Model_ID_here";

9. Once the groovy is updated and above steps are followed correctly, same model will then be available to you on both 3D Repo and Asite.

10. Open Model in Asite and Create an issue.
Once the issue is created, workflow will be triggered in background automatically as per configuration in step 6 above.
While viewing the issue, you can check the status of the workflow using the 'Workflows' menu in 'More Options'.

11. Open 3D Repo and open the federated model for which we copied the model id to Groovy script as per step 8 above.

12. Select issue ribbon. The issues created in model on Asite will be visible in 3D Repo issues.

Any issues created on models in Asite, will also be created on the models on 3D Repo based on the first workflow trigger configured as per step 6 above.

Any updates made to the model issues on Asite, like changing status or priority of the issue, will also be updated on the model on 3D Repo based on the second workflow trigger configured as per step 7 above.

Please note that only the issues created or updated in Asite are currently supported to reflect on 3D Repo, not vice versa.
​