Project Verification Checklist

This article provides a check list of steps you might want to perform for your application designer project after you have finished your initial development and before migrating it to other environments for testing.

Yes, this takes a bit of work, but it will ensure the internal consistency of your project and save you a lot of time and effort after migration. Trying to figure what is missing from the migration of a large project can be very frustrating!

Internal Documentation

This refers to the description and comments for PeopleTools definitions that you can modify through application designer.

  • Have you included a description and comments in your project properties?
  • Go through all of the definitions in the development tab. If it is a new definition, check that it has a description and comment in the definition properties. If this is a modification to an existing definition, make sure you have added a comment in the comments.
  • Do your application engine sections and steps have appropriate labels and comments?

Project Validation

This is about ensuring that you don't have any invalid or stray definitions in your project and that the definitions in your project are valid.

  • Have you performed a Tools > Validate Project and deleted any invalid definitions? Make sure that your validate options include validating the component interface and project integrity (Tools > Options > Validate tab).
  • Did you delete any definitions during development? Are they still left in your project? If you deleted any tables, have you dropped them from the database as well? Use the queries here to check,
  • Scan through your definitions in the development and upgrade tabs. Is there anything missing? Is there anything that shouldn't be there? Did you actually modify every definition included in your project?
  • Open all PeopleCode in your project and perform a validation using the green tick in the toolbar (Tools > Validate Syntax). Pay attention to all messages in the validate window. If you have any auto-declared variables in your PeopleCode you have a bug. Declare these variables. You'll be glad you did later. Also check for any messages about deprecated code. If you can, fix these by using the appropriate (not deprecated) functions or methods.
  • Are you missing any definitions edited outside of PeopleSoft. Some common ones include message catalog entries, portal registry structures, permission lists, roles, process definitions, job definitions, integration broker components (service operations, routings, message nodes, queues) and XML publisher definitions.
  • Build your project and ensure that all tables, views, indexes and triggers build. Check the validate window for any errors.

Upgrade Options

You need to check your upgrade options to ensure all relevant definitions are migrated correctly to other environments (and that nothing has been missed).

  • Go through the definitions in the Upgrade tab. For each one, check the action and upgrade flags. Generally you will want the action to be Copy and the upgrade flag set. The only exceptions here are if you want to Delete a definition or you don't want it to be upgraded (migrated) in which case the upgrade flag is not set.
  • Did you perform compare report? Go back and check your upgrade flags as they will have changed. You may find that your upgrade action is set to CopyProp (copy properties). Is this appropriate? When it doubt, perform a Copy and set the upgrade flag.

Unlock Definitions

This is about ensuring that you don't leave any definitions unlocked. You can also perform a mass unlock of definitions if you find you have a lot of them locked and want to unlock them all at once.

  • Go through all definitions in the development tab. Is it appropriate to unlock any of them to indicate to other developers that you have finished with them?
  • Conversely, are there any definitions that should be left locked until your changes have been migrated to production to avoid conflicts with other developers?
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License