What are some possible configurations for user tasks created in ? Note: There are 3 correct answers to this question.

Question

Options

• AAssign it to a specific user.
• BSet a due date.
• CAssign it to dictionary categories.
• DStore attributes.
• EDefine specific access rights.

• A
  92% (23)
• D
  4% (1)
• E
  4% (1)

Explanation

The question appears to be incomplete - the system name is missing from "created in ?" - and there's a contradiction: it states 3 correct answers exist, but only A is listed as correct. This makes it impossible to give a fully accurate explanation of all three correct choices.

What can be said about the options:

• A (Assign to a specific user) is almost universally a core feature of user task configuration in workflow/BPM systems - tasks need an owner to act on them.
• B (Set a due date) is also a standard task configuration in most workflow tools, making it a likely correct answer for the missing two.
• D (Store attributes) is plausible in systems like SAP BPM or similar, where tasks can carry custom data fields.
• C (Assign to dictionary categories) is atypical for task configuration - categories/dictionaries are usually a classification feature, not a task property.
• E (Define specific access rights) is typically handled at the role or system level, not per individual task.

Memory tip: Think of a task as a to-do item - it needs a person (A), a deadline (B), and sometimes extra data (D). Rights and categories belong to the system structure, not the task itself.

Recommendation: Verify the source material to confirm which system this refers to and retrieve the full list of correct answers, since the question as provided is missing critical context.

No community discussion yet for this question.