Autodesk · Arazzo Workflow
Autodesk Run a Design Automation WorkItem
Version 1.0.0
Pick an engine, publish an AppBundle and Activity with aliases, then run and poll a WorkItem.
View Spec
View on GitHub
Fortune 10003D ModelingArchitectureBIMCADConstructionDesignDigital TwinsEngineeringManufacturingMedia and EntertainmentSustainabilityArazzoWorkflows
Provider
Workflows
run-design-automation-workitem
Publish an AppBundle and Activity, then execute a WorkItem against them.
Lists engines, creates and aliases an AppBundle, creates and aliases an Activity that loads it, submits a WorkItem with input and output arguments, and polls the WorkItem until it succeeds or fails. AppBundle binaries are uploaded to the returned uploadParameters endpoint out of band between the AppBundle and alias steps.
1
listEngines
getEngines
List the engines available to the caller so the Activity targets a version that actually exists rather than a guessed product string.
2
createBundle
createAppBundle
Create the AppBundle record. The response carries uploadParameters, the pre-signed form endpoint the packaged binary is POSTed to before the alias is created.
3
aliasBundle
createAppBundleAlias
Point a stable alias at the AppBundle version just created, so Activities can reference "name+alias" and never a moving version number.
4
createActivityDefinition
createActivity
Define the Activity: which engine runs, which AppBundle loads, what command line executes, and the input and output parameters the WorkItem will bind URLs to.
5
aliasActivity
createActivityAlias
Alias the Activity version so WorkItems submit against a stable id while new versions can be published behind it.
6
submitWorkItem
createWorkItem
Submit the WorkItem, binding the Activity's declared parameters to real URLs. The engine downloads inputFile, runs the command line, and uploads outputFile.
7
awaitWorkItem
getWorkItemStatus
Poll the WorkItem until it succeeds. The endpoint returns 200 throughout, so the terminal state is read from the body. On any failed state the workflow ends and the reportUrl carries the engine's log.