33
ESKOARTWORK WEBCENTER RELEASE NOTES
In many cases the task will be specifically intended just for one assignment so
there will only be one specification for this task type. However this is not
necessary. You can for example ask a marketing manager to fill out some
information (goals/ta rgets, terms to be used, …) and assign the agency, all in
one task. It’s just a matter of adding task specifications.
Step 4: C reate tasks of the just c reated ta sk type
In a project or more typically in a template, add a task of the just created
task type. Assign this task to the person who needs to take the decision and
put the task where it logically is needed in the task sequence.
In our example where a marketing manager needs to decide the agency, assign
the task to the marketing manager.
Step 5: Execute
Run the project as normally. When the task is started, the assignee will get it
in his/her to-do list and might be e-mail notified. He/she opens the task and
d
gets a user interface as below:
He/she selects the right agency or person at the agency and completes the
task.
Behind the scenes following happens:
The system sees that the task type asks for placeholder replacements. It
sees a specification named Agency and goes looking for a placeholder group
named Agency. If it finds nothing, nothing more happens. If it finds such a
placeholder group, it looks for the selected value and tries matching it to a
group (first) or user (if no matching group is found). If a match is found, the
replacement is done in exactly the same way as if the project manager would
have used the replace placeholder group functionality.
The typical consequence in our example will be:
• Agency 1 is invited to the project
• A number of tasks are re-assigned from Agency to Agency1
• (less typical) A number of approvals might be re-assigned from Agency
cy
to Agency1
