Cloud Nester | AMFG Help Center

Introduction

The Auto-Nester is an existing capability in AMFG, which allows AMFG to:

Share the content of a build with a 3rd party application
Provide a unique, secure upload URL for the Build File for the 3rd-party application
Receive an itemized list of items in the build and what AMFG needs to remove

Prerequisites

Workflow Automation for Auto-Nester
- Define a Build status (Settings → Attributes & Status) to trigger the Cloud Nester
Workflow Automation for Build Status Update
- Define a Build Status (Settings → Attributes & Status) for when the Cloud Nester is complete
Configure Cloud Nester (Settings → Cloud Nester)
- Click Create Cloud Nester
- Apply name (any name)
- Define adapter type (here: Generic)
- Paste settings
  Note: The ‘URL’ is where the Build JSON is sent to - make sure you have access to this JSON (webhook.site is good for testing, but ultimately the cloud nester will need this)
```
{
  "endpoint": {
    "url": "https://webhook.site/f7e55a98-ed5e-41ab-b13e-d44d3252bed7",
    "headers": {
      "plain": "plain header"
    }
  },
  "nesterSettings": {
    "someSettings": {
      "a": 2,
      "b": 3
    }
  },
  "nestedBuildExtension": "3mf"
}
```

Flow for usage

Create a Build and assign parts
Select Build (Production → Create A Build page) and select Auto-Nester

Note: There will be a loading sign at the build to indicate the process is not complete (top right)
Update Build status to trigger Auto-Nesting

Generate file upload path: Send POST message to "nestedBuildUploadUrl"
--> This is unique for every JSON

You’ll receive a response looking like this;
Status: 200, “OK”

{
	"method": "POST",
	"url": "https://console.amfg.ai/storage-service/api/v1/node/7444144/upload?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiI5NDUwIiwiYXBwSWQiOiIxODQwIiwiaXNBZG1pbiI6MSwic2Vzc2lvbklkIjoidThwM2tscDU0cWVndmdna2kzbGtqZ2hqZjciLCJpbnRlcm5hbCI6dHJ1ZSwiaWF0IjoxNjc4MjY3MTc5LCJtZXRob2QiOiJwb3N0IiwidXJsUHJlZml4IjoiL3N0b3JhZ2Utc2VydmljZS9hcGkvdjEvbm9kZS83NDQ0MTQ0L3VwbG9hZCIsInF1ZXJ5UGFyYW1zIjp7fSwibGl2ZVRpbWUiOjMxNTM2MDAwMDAwfQ.03ayRmuTgs25wpR4RirHvkUKySIwsVZSxPBKNWDxYhE"
}

Copy “URL” from the server response
1. “URL” is valid for one minute
2. “URL” is unique for every response you get from #4

Send file to “url” from #4 server response

Setting (Postman, Insomnia): Binary file
In Insomnia, it looks like this:

You’ll receive a response looking like this;
Status: 200, “OK”

{
	"id": "7444144",
	"type": "FILE",
	"name": "temp_aYxp1rYgutWv452b.3mf",
	"active": true,
	"public": false,
	"meta": {
		"hash": "5bd2871ec21f47658788533497698a25",
		"size": 3126680,
		"buildId": "22417",
		"nestedBuild": true,
		"resourceNotFound": false
	},
	"notifications": {},
	"appId": "1840",
	"storageId": "89",
	"parentNodeId": "7444115",
	"expireAt": null,
	"createdAt": "2023-03-08T09:22:00.687Z",
	"updatedAt": "2023-03-08T09:22:25.541Z"
}

You’ll notice in AMFG (Create A Build → Select Build) that there is a temporary 3MF file
Do NOT modify this, it’ll be finalised in the next step!!!

The file extension - here: 3MF - is defined as the extension in the settings area for the Cloud Nester.

Send Postback to "responseUrl"
--> "responseUrl" is unique for every flow

Message example content:

{
    "id": "aYxp1rYgutWv452b",
    "status": "success",
    "error_message": null,
    "parts": [
        {
        "id": 644394,
      	"orderId": "199119",
      	"quantity": 1,
        "status": "success"
        }
      ]
}

For every message, you MUST update from the initial Build JSON.

POST to: response URL
id: "processingId"
parts information

Go back to AMFG and refresh the page
1. The build status should be updated (here: Scheduled)
2. The loading icon should have disappeared
3. The build file upload area should have a file called nested_build.3mf
  The file extension - here: 3MF - is defined as the extension in the settings area for the Cloud Nester.