DrH Autodesk engineering tools

DrH/Request

Tell us what you keep doing by hand.

This one form covers all of it — a new tool, a trial key, an invoice, a Team quote or a bug in something that will not load. Pick the type, describe the situation in plain words, and you will get a real answer rather than a ticket number.

Enter an address we can reply to.
A sentence or two is enough, but we need something to go on. Roughly how often you do this task is the single most useful detail you can include.
See what already exists

Your message is sent directly through the DrH contact service. The form does not open Outlook or any other email application.

  1. step 01

    You send it. No account, no sign-up.

  2. step 02

    You get a straight reply — building it, need more detail, or out of scope with the reason.

  3. step 03

    Accepted tools are built against the host years you actually run.

  4. step 04

    Press Update in the DrH panel and the command is there.

What makes a request easy to say yes to.

None of this is required. It just moves things along faster.

How often you do it

Twice a day and twice a year lead to very different tools. Frequency is the strongest argument a request can carry.

What you do now

The manual steps, in order, even if they are clumsy. That sequence is usually the specification.

What "done" looks like

A file, a table, a set of updated objects. Naming the output prevents a tool that technically works and practically does not.

Whether it can be shared

Say so if the workflow is confidential. It can be published to a private feed instead of the public library.