Required?: YES (Within a content-handler block)
Max Length: 512 characters (Well, actually probably shorter due to auto-added data - TODO Fill in based on testing + walking through code) XXX
Legal Characters: us-ascii only
Authenticated Request?: YES
Request Arguments: Generic Proxy Tool Request Arguments, course_id, content_id
Sample Implementation: ContentHandlerAction.java, modify.jsp, CreateContentAction.java
Legal Roles: COURSE:INSTRUCTOR, COURSE:COURSE_BUILDER

In the modify operation, the extra arguments passed in have this meaning:

• course_id: The course in which the content exists.
• content_id: The id of the CONTENT that is being modified. (note how it actually is the content here, unlike the create action where it was the folder/parent id)

Note here how a webservice session (ClientWrapper) is established before forwarding to the Modify page. This is due to the short lifetime of a ticket for login and the unpredictable amount of time the user may spend on the Modify page. In CreateContentAction, observe how it distinguishes between create and update based on the existence of a content-id in the post. It calls the same ContentWS.saveContent method as an insert/update routine. Make sure the original contentid is set on the ContentVO to perform an update.