Request Intake and Project Initiation
What the exam expects
Requests in Workfront are issues submitted through a request queue - a project with Publish as Help Request Queue enabled plus queue details (who can add requests, default duration, default approvers, default company). Queue topics give requesters a menu of intake paths; topic groups bundle topics; routing rules set defaults such as assignee, team, custom form, or status when a request arrives. A queue project missing queue details produces the classic "request queue not configured" failure.
Initiation usually means converting an issue to a project. The conversion dialog requires a template and offers to keep the original issue and tie its resolution to the new project. The template supplies tasks, assignments, durations, predecessors, custom forms, and sharing.
The business case is the justification artifact: expenses, risks, alignment score, ROI, and planned revenue versus planned cost. It can drive a business-case approval before a project moves from Planning to Current.
Traps
- Request queues are projects, not a separate object; a topic only appears when attached to a published queue.
- Template edits do not retrofit projects already created from that template.
- Queue defaults and routing-rule defaults can both apply - in scenarios, identify which object actually supplies the final assignee or form.
- Converting consumes the issue unless the keep-original option is used.
Rule of thumb
Trace one request end to end - queue project → topic → routing rule → custom form → approval → conversion template - and name the object that supplies each default.