A checklist is used to track the receipt of a requisite in Peoplesoft. Recording the outcome of a requirement request is called completing the checklist item. While there are a few steps in assigning a checklist, closing the checklist is a one step process.

NOTE: We are NOT deleting the checklist - that would cause the loss of the history that we requested the item. There is a way to delete checklists but that is based on thousands of miss-assigned checklists found immediately
When completing a checklist item, we describe the outcome of our request:

We requested something and now we have it, or we are giving up. Above you see the list of checklist item statuses. These statuses do not drive processes themselves, any meaning given to these values must be coded locally. i.e. WSU gives the values meaning. Suggested usage for non-financial checklist items:

Of course, the other values can be used, but they will need to be given meaning and business process built to enforce those meanings.

Individual completion of checklists

Now it is time to complete a checklist. We know what checklist the student has (AS001) in this case and we know the student did the task requested, now we want to mark the checklist item complete. Here is the standard path for this job:
 
Main Menu > Campus Community > Checklists > Person Checklists > Checklist Management - Person

Which presents you with this page:

Here you enter student information and checklist code information.

After choosing a particular student checklist you will be presented with this page:

This is the Checklist Management 1 page. A checklist is an amalgamation of 1 or more checklist items. This page is managed by the system based on the statuses of the checklist items on the Checklist Management 2 tab.

As you can see, the checklist can only be initiated or completed. The detail is at the checklist item level, so let's look at the checklist item tab:

Now you have the checklist item page. This is where you can mark it waived, or complete, or cancelled etc:

You do not need to add a row or do anything more than change the status and save.

Quick Step-by-step:

1. Go to Main Menu > Campus Community > Checklists > Person Checklists > Checklist Management - Person
2. Enter (or choose) Emplid and Checklist code.
3. Enter Checklist Management 2 if you are on Checklist Management 1.
4. Change the status of the Checklist item with which you are concerned.
5. Save.

NOTE: You can see that there is access to the statuses of both the Checklist and the Checklist item. Please, never "reopen" a 3c item. Sometimes there is code assigned to the initiation of a 3c item and by manipulating statuses any initiation processes may not happen. Also, you would only have history of one requested rather than the truth - two requests.

Bulk completion of checklists:

Method 1: Close multiple ITEMS on a SINGLE student.

For this we will change our path to:
Main Menu > Campus Community > Checklists > Person Checklists > Item Update – By person
We will be presented with this page:

The problem with this is that you are not able to see a list of all checklist items for the student so that you can update them. We can only see the initiated status on the items associated with one checklist at a time.
For Campus Solutions use checklists are best built on a one-to-one relationship with checklist items, hence this doesn't really save anything.
This page is best used by a person whose security is somewhat less than a person with access to checklist management page.

Method 2: Close the same ITEM on multiple STUDENTS:

For this we change our path to:
Main Menu > Campus Community > Checklists > Person Checklists > Item Update – By Item
Here we choose a checklist item:

And are then presented with this "blank" page:

Here the user may key-in Emplids and then when the batch process to mark checklist items complete runs (nightly), all listed students will be marked as "Completed". As of 2021/04/12 this functionality is not being used yet at WSU when use is desired a ticket will need to be filed to schedule the batch process.
Note: This cannot be used to batch waive or cancel checklists only complete them.

Method 3: Use the 3c Engine:

Not a user task, but everyone should know that by using the 3c engine very complicated rules and batch processes to deal with 3c's can be built. If the methods of completing checklists mentioned above do not suffice, the help desk can work to create a 3c engine for user requirements.