A Task Is a Process Step
When we refer to a [Human Task], we mean a step shown in a workflow diagram. In this context, the term “Task” is best translated into Japanese as “process step.”
- [Script Task]
- [Receive Task (Form)]
- [Service Task (Start Subprocess)]
These are also types of process steps.
My Tasks Are Not Process Steps
However…
- [My Tasks]
- “A task came in.”
- “Process a task.”
In contexts like these, “Task” cannot naturally be translated as “process step.” In other words:
- You would not translate “A task came in” as “A process step came in.”
- [My Tasks] cannot be translated as “My Process Steps.”
- “Process a process step” is understandable, but it sounds somewhat unnatural.
Definition (Class) and Actual Occurrence (Instance)
In these examples, “Task” does not refer to a step in the workflow definition. Instead, it refers to an actual unit of work that has been created and must be processed.
– X. Task as a definition:
– A process step used to define the flow of work
– x. Task as an actual instance:
– Each individual unit of work generated at that process step
In conclusion, [X. a Task as part of a definition] can consistently be translated into Japanese as “process step.” However, [x. a Task as an actual instance] often sounds more natural in Japanese when translated according to its context, such as “work that has been generated,” “work to be processed,” or “work that has been completed.”
PS
If someone were to say, “Translate it using exactly two Japanese characters—or else” (?), I would translate it as “processing.”
– X. Task as part of a definition: Process step
– x. Task as an actual instance: Processing
That said, actual user interfaces commonly retain expressions such as “My Tasks” and “Task Processing History.”
