Below are the steps you need to follow to push issues on your federated models from Asite to the 3D repo:
1. Once logged in to Asite, go to the '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 the 'Textbox' type.
4. Once the new attribute is created, create an attribute set by selecting it and applying it to one or more project folders (which contain 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 necessary, you can also include this system task when creating a new workflow for custom objects, so that the progress of workflow on selected issues can be tracked separately while viewing it.
6. Configure a custom object workflow trigger in the same project. This workflow trigger should be configured to initiate the above system task or the workflow created (stated in step 5) upon the 'Create Custom Object' event in the 'Post' task mode.
7. Configure another custom object workflow trigger in the same project. This workflow trigger should be configured to initiate the above system task or the workflow created (stated in step 5) upon the 'Update Custom Object' event in the 'Post' task mode.
8. Open 3D Repo. Select an existing federated model or create one as needed.
Once you open the model, a model ID will appear in the URL.
Copy and paste the model ID you see for your model (“92a3fdc0-0ce4-4c83-86ca-e726ac9646e4” as per the 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, and then go to the 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 the above steps are followed correctly, the same model will be available on 3D Repo and Asite.
10. Open the Model in Asite and Create an issue.
Once the issue is created, the workflow will be triggered automatically in the background according to the configuration in step 6 above.
While viewing the issue, you can check the workflow status using the 'Workflows' menu in 'More Options'.
11. Open 3D Repo and open the federated model for which we copied the model ID to the Groovy script as per step 8 above.
12. Select the issue ribbon. The issues created in the model on Asite will be visible in 3D Repo issues.
Any issues created on models in Asite will also be reflected on the models on 3D Repo based on the first workflow trigger configured according to step 6 above.
Any updates made to the model issues on Asite, such as changing their status or priority, will also be updated on the model on 3D Repo based on the second workflow trigger configured according to step 7 above.
Note: Only the issues created or updated in Asite are currently supported to reflect on 3D Repo, not vice versa.
Next Article: Groovy Script Objects and Functions