The following link types are currently supported:

The following link types are NOT supported: communication, cs_action, cs_tool, cs_modify_file, cs_modify_folder, cs_manage_portfolio, cs_my_portfolios.

communication

Request Arguments: Generic Proxy Tool Request Arguments, course_id
Sample Implementation: ToolAction.java, tool.jsp (?type=communication)
Legal Roles: COURSE:*
Placement: This link displays on the Tools page in a course.
Name: Displays as the name of the link.
Description: Displays as the long description on the tools page under the linked Name.
Icon Size: 50 x 50 pixels
Icon Placement: Beside the name on the Tools page.

The communication link provides a Course-level single-instance tool entry point for a communicationstyle tool. Store the data keyed on guid+course_id.

course_tool

Request Arguments: Generic Proxy Tool Request Arguments + course_id
Sample Implementation: CourseToolAction.java, courseTool.jsp
Legal Roles: COURSE:INSTRUCTOR, COURSE:COURSE_BUILDER
Placement: This link shows in the Course Tools part of the Control Panel in a course.
Name: Shows as the name of the link in the control panel.
Description: N/A
Icon Size: N/A
Icon Placement: N/A

The course_tool provides a control panel entry point into a single-instance of the tool per course.
Store the data keyed on guid+course_id. This page is used by an Instructor to configure their course-level tool. The tool link type is used to display the tool to students.

group_tool

Request Arguments: Generic Proxy Tool Request Arguments, course_id, group_id
Sample Implementation: ToolAction.java, tool.jsp (?type=group)
Legal Roles: COURSE:*
Placement: This link shows on the Groups pages in a course.
Name: Shows as the name of the link.
Description: Shows as the long description on the group page under the linked Name.
Icon Size: TBD
Icon Placement: TBD

The group_tool link provides a Group-level single-instance (per group) tool entry point. Store the data keyed on guidcourse_idgroup_id.

system_tool

Request Arguments: Generic Proxy Tool Request Arguments
Sample Implementation: SystemToolAction.java, systemTool.jsp
Legal Roles: SYSTEM:ADMIN
Placement: This link shows in the Tools and Utilites module on the System Admin tab.
Name: Shows as the name of the link
Description: N/A
Icon Size: N/A
Icon Placement: N/A

The system_tool link is designed for global per-academic-suite-instance configuration. Store any data here keyed on guid.

tool

Request Arguments: Generic Proxy Tool Request Arguments, course_id
Sample Implementation: ToolAction.java, tool.jsp
Legal Roles: COURSE:*
Placement: This link shows on the Tools page in a course.
Name: Shows as the name of the link.
Description: Shows as the long description on the tools page under the linked Name.
Icon Size: 50 x 50 pixels
Icon Placement: Beside the name on the Tools page.

The tool link provides a Course-level single-instance tool entry point. Store the data keyed on guid+course_id.

user_tool

Request Arguments: Generic Proxy Tool Request Arguments
Sample Implementation: UserToolAction.java, userTool.jsp
Legal Roles: SYSTEM:NONE
Placement: This link is used in the Tools module on your My Institution module. It must be manually added there by the Blackboard Learn System Administrator on *System Admin/Community System-Management/
Tabs* and Modules/Tool Panel.
Name: Shown in drop list of tools on the Add Tool page.
Description: N/A
Icon Size: 12x12 pixels
Icon Placement: Beside the clickable name on the tools module.

The user_tool link is designed for a global per-user tool. You would store your data keyed on guid+userid. The return_url here is not valid for a direct return. As it stands today you need to specify a target="_top" for the return to work properly here (See userTool.jsp)