Dispatcher: Working in Active Workspace

Everything Dispatcher-related that used to require the rich client now has an Active Workspace surface. Two of them matter: the Dispatcher Console for requests, and Workflow Designer for the templates and handlers that create them.

Dispatcher Console — monitor and manage requests

Reached from Launcher → Dispatcher Console. If it is not on the Launcher, search for it and pin it from the search results.

Requests are listed in a table sorted by creation date, newest first.

To find	Do this
Failed requests	Filter by state = TERMINAL
Requests from a user	Filter by Owner
Requests for a service	Filter by Service Name
Requests for a provider	Filter or sort by Provider Name

Per-request actions:

• Information opens the request in the Information panel; Open opens it in its own view.
• Reload refreshes status, either for the whole table or for selected rows. The table does not live-update, so a stale state is expected, not a bug.
• Resubmit returns a terminal request to its initial state and reprocesses it with the original configuration. ⚠ If the underlying cause is still there it will simply fail again — and because it reuses the original config, a resubmit will not pick up a preference you just fixed unless the client has also reloaded it.
• Delete removes the request asynchronously; Delete without trace also removes its complete history from the database.
• Export to Excel for reporting, with column selection.
• Table Settings → Configure Table to add object types and properties.

This is the same information as queryDispatcherRequests over SOA, and it answers the one question getProperties cannot: the current state of a request. For scripted checks, keep using the SOA route documented in Submitting requests; for a human looking at a stuck queue, the console is faster.

Workflow Designer — authoring the trigger in AW

Workflow templates, tasks and handlers can all be authored in Active Workspace, which means the Dispatcher trigger described in Triggering translations from workflow can be built entirely in the browser. No rich client, no BMIDE, no iman_workflow export.

Create the template

More Commands → New → Create Workflow Template from the page-level toolbar. Choose Workflow as the template type, give it a unique name and description, and either base it on an existing template or select None. A new template contains only start and end tasks.

Add the tasks

Creating a template puts it in edit mode automatically; returning to it later requires Start Edit, which asks whether to keep the template online or offline during editing. Then Task Palette, and drag tasks onto the canvas. End Edit saves.

For a Dispatcher trigger you want a Do task — it is the one that ships with EPM-hold already on its Complete action, which is what lets the translator release the workflow when it finishes.

Add the handler

Start Edit → select the task → Handlers tab.

1. The left pane lists existing handlers grouped by trigger, in execution order. Expand a trigger group to see them.
2. Select the trigger group you want to add to (for a Dispatcher trigger: the task's Start action).
3. On the New Handler panel, choose Action or Rule.
4. Pick the handler from the drop-down. The list is not case-sensitive and includes custom handlers and handlers from other installed solutions — which is exactly how TSTK-CreateTranslationRequest shows up even though the Dispatcher book never mentions it.
5. Mandatory arguments appear automatically once a handler is selected. Help launches that handler's documentation.
6. Add Arguments for optional ones, pick the argument from the drop-down, fill in Value(s). Hints mark mandatory vs optional to head off runtime errors.
7. Add, then expand the trigger group to confirm it landed.

Handlers can be Cut / Copy / Deleted from the table, and copied across actions, across tasks in a template, and across templates (select the target template from the Process Template list; the target must be in Edit mode).

Who is allowed to do this

By default, template authoring is DBA-only. To open it up, an administrator modifies the BMIDE condition Awp0IsWorkflowTemplateAuthor to name a group, then creates or designates that group and adds users to it.

⚠ Non-DBA authors can attach an existing ACL to a task but cannot create new ACLs.

Applying changes to work already in flight

Editing a template does not retroactively change running processes. Apply template edits to active processes is a separate, deliberate action — worth knowing before you "fix" a template and wonder why in-flight jobs still behave the old way.

Doing the same thing over SOA

The AW Workflow Designer is a client over ordinary SOA operations, so anything above can be scripted. Routes and required members, from the offline WSDL index:

Operation	Route
List handlers registered on the tier	Workflow-2019-06-Workflow/getRegisteredHandlers
Valid arguments for a handler	Workflow-2020-01-Workflow/getSupportedHandlerArguments
Add/update a handler on a task template	Workflow-2019-06-Workflow/createOrUpdateHandler
Create/update a workflow template	Workflow-2019-06-Workflow/createOrUpdateTemplate
List templates	Workflow-2013-05-Workflow/getWorkflowTemplates
Push template edits into running processes	Workflow-2010-09-Workflow/applyTemplateToProcesses
Start a process	Workflow-2008-06-Workflow/createInstance

createOrUpdateHandler requires every one of clientID, handlerName, taskTemplate, businessRule, handlerType, handlerToUpdate, action, ruleQuorum, changeExecutionOrder — the usual Teamcenter full-struct rule. Omitting one is the standard cause of a 200 OK that changed nothing.

⚠ Workflow-2008-06-Workflow/getWorkflowTemplates is deprecated since 10.1 in favour of the 2013-05 namespace. A deprecated Teamcenter operation still accepts the call and returns 200 OK with an empty result, so "no templates found" from the 2008-06 route is a version problem, not an empty site.

getRegisteredHandlers is the one to reach for first: it is the authoritative answer to "is TSTK-CreateTranslationRequest actually installed on this tier?" — a question no amount of documentation can settle, because the handler ships with Process and Program Management rather than with Dispatcher.