Projects

This wiki page is about Application Designer Projects. Specifically topics such as how to copy them between database, copy them to a file and then copy back into a database from a file. These options are available through application designer using Tools -> Copy Project.

Copy Project to File

Before copying any project to file, make sure you have verified the following:

  1. Navigate to the Upgrade tab in Application Designer (normally this is on the Development Tab)
  2. Go through each definition (Component Interface, Component, Page, Record, Field etc) and verify that they all have an action fo Copy (where appropriate) and that the Upgrade flag is ticked. Any definitions where this is not the case WILL NOT be copied to file.

You can also use the following SQL to check your project. Verify that UPGRADEACTION is set to 0 for Copy and TAKEACTION is set to 1 for Upgrade.

select
    OBJECTTYPE,
    OBJECTVALUE1,
    OBJECTVALUE2,
    OBJECTVALUE3,
    OBJECTVALUE4,
    UPGRADEACTION,
    TAKEACTION
from PSPROJECTITEM 
where PROJECTNAME = 'YOUR_PROJECT_NAME';

Once you have verified these setting you can then copy your project to a file. Note that there are some PeopleSoft definitions that will NOT copy to a file. These are:

  • Message Catalog Entries
  • Roles

Copy Project from File

This means importing a project from a file. There are two files associated with all exported projects:

  • PROJECT_NAME.ini
  • PROJECT_NAME.xml

The .ini file contains meta-data about the project while the .xml file contains the actual project definitions, so it can be quite large. There are some catches when copying a project from a file to watch out for:

  1. The .ini and .xml files need to be inside a folder with same name as the project.
  2. The .ini and .xml files cannot be read only. Check the file attributes.

The above situations will cause the copy from project dialog to not show the project in the list box.

Validate Project

The validate project command in Application Designer is very important for ensuring that your project is correct before migration. It checks that your objects are valid (especially components and component interfaces) and finds any invalid definitions that you should remove or fix before migration. The command is located in Application Designer under:

Tools Menu > Validate Project

When you have a project open. An important tip is to perform validate project on a project after it has been migrated to the target environment. This provides signs of any migration issues. Migration issues found through validate project are typically the result of objects missing in the target environment.

You should ensure that you have the appropriate validate options selected:

Tools Menu > Options > Validate (tab)

At least the following should be enabled:

  • Validate PeopleSoft Internet Architecture Execution
  • Validate Component Interface
  • Validate project integrity
  • Validate spelling

Troubleshooting

If you are migrating projects between environments and you have modified the project in the target environment, copied the project from the source, then tried to save the project in the target environment without reloading it first, you will get an error along the lines:

PROJECT - ENG has been updated by another user. (3,2)

This is PeopleSoft telling you that there are synchronisation (version) issues between the project in the database and the one you are trying to save. I'm not sure what they mean here by reboot, I think what is meant is that you need to close and reopen application designer. However this isn't necessary - you can simply reload the project using these steps in Application Designer:

  • File > New Project [OK]
  • File > Open > [Your Project]

Note if you get nastier errors like this:

Illegal uncommitted SQL cursor detected. Close down all windows and reboot. (22,3)

Then it really is time to close and restart Application Designer! Don't keep working with such errors, you'll pay for it as Application Designer will most likely crash soon!

(Note this post was written using PeopleTools 8.48.15 - things might be better/different in different Tools versions)

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License