6 Setting and Editing Package Services

This chapter includes the following:

• Overview

• Editing Package Service

• Deleting Package Services

Note: For Agile-to-Agile publishing, you must create package services on the target Agile PLM system. You do not need package services on the source Agile PLM system. For a summary of the Agile-to-Agile communication configuration tasks required on both, the source Agile PLM system and the target Agile PLM system, see Chapter 9, "Settings Required for Agile-To-Agile Publishing."

6.1 Overview

Package services are used to define what Package subclass, autonumber source, and workflow are used when content is received from a remote system through an Agile destination. When you enable Agile-to-Agile communication, you must configure the target Agile PLM system to properly create the package object using the correct autonumber source and route it to the correct program manager. You can configure multiple package services on a target Agile PLM system if you wish to treat data from each source in a specific manner. However, it is not necessary to create a package service for each source; several sources can use the same package service.

The following modifications or settings are also required for you to successfully define and use package services:

• The following package object fields must be visible on the Cover Page tab of the Package object class:

  • Response Expected

  • Source GUID

  • XFER Order Locator

• Create or identify a user who has a role that provides the ability to create, modify, and delete package objects and the ability to change the status of the package object to the required workflow status. You must provide this user's username and password to the administrator of the source Agile PLM system. This is used to define a destination on the source Agile PLM system (see Chapter 2, "Setting and Editing Destinations." If the package service moves the package object to the Submit status, then the privilege masks in the default Partner role are sufficient if you modify the Modify Pending Package privilege mask by adding the following fields to the Selected list in the Applied To property:

  • Packages.Cover Page.Program Manager

  • Packages.Cover Page.Response Expected

  • Packages.Cover Page.Source GUID

  • Packages.Cover Page.XFER Order Locator

If you do not want to modify this privilege mask, use the Partner role and privilege masks as a guide to create the necessary role.

Note: Verify that the package service will work successfully with the package object configuration, package workflow settings, and login user role. For information, see "Verifying Agile-to-Agile Publishing."

To create a package service:

1. Under System Settings > Agile Content Service, double-click Package Services. The Package Services window appears.

2. Click the New button. The Create Package Service dialog box appears.

3. Type a name and a description of the subscriber in the Name and Description fields.

4. Select Package from the Subclass list.

   
   

   Note: If you have defined a specific package subclass for use in package services, select that subclass from the list.

   
   

5. Select Package Number as the autonumber from the Number Source list.

6. Select Default Packages from the Workflow list.

   
   

   Note: If you have defined a specific package workflow for use in package services, select that workflow from the list.

   
   

7. Select a workflow status from the Workflow Status drop-down list.

   Agile recommends using the Submitted workflow status to ensure that the receiving program manager is notified about the package.

   When an Agile-to-Agile transfer occurs, the package object is created on the target Agile PLM system and the package workflow status is set to the status specified in the Workflow Status field of the package service.

   
   

   Note: When creating a package service with a target package workflow status other than Pending, make sure the target workflow allows changes directly from the Pending status to the status to be used (determined by the Manual Valid Next Status property for the Pending status if the status to be used is not the next status after Pending in the workflow). Also make sure that the logged-in user specified in the target Agile PLM system destination has the privilege to make the change (Change Status (CS) privileges for packages) in the target Agile PLM system.

   
   

8. Click OK.

6.2 Editing Package Services

You can edit all of the parameters of the package service except the Subclass field.

To edit a package service:

1. Under System Settings > Agile Content Service, double-click Package Services. The Package Services window appears.

2. Double-click the package service you want to edit.

3. Edit the General Information tab of the service to make the necessary changes.

4. Click Save and Close.

6.3 Deleting Package Services

You can delete a package service at any time. Because a package service does not restrict or define other ACS settings and does not have relationships with database objects, your ability to delete it is not restricted.

Note: If a source Agile PLM system attempts to deliver content to a deleted package service, the content transfer will fail.

To delete a package service:

1. Under System Settings > Agile Content Service, double-click Package Services. The Package Services window appears.

2. Select the package service you want to delete.

3. Click the Delete button.