Skip Headers

Agile Product Lifecycle Management ACS User Guide Release 9.3.3 E39294-01 |
| Contents

Previous | Next |

# 5 Setting and Editing Subscribers

After you configure events, filters, destinations, roles, and criteria, you can create subscribers to publish data automatically when all of the subscriber requirements are met. A subscriber is associated with only one event and criteria, but can contain multiple destinations, filters, and roles. These are managed from the Subscribers node.

## 5.1 Creating Subscribers

Agile PLM provides an example scheduled subscriber and an example workflow subscriber. The example subscribers incorporate the other Agile Content Service example settings as a template you can use when creating a subscriber to match your company's requirements.

To create a subscriber:

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

2. Click . The Create Subscriber dialog box appears.

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

4. Select the subclass from the Subclass list.

   This is the ATO subclass Agile Content Service generates when an event occurs that matches all the properties of this subscriber.

5. Select the Default ATOs workflow from the Workflow list.

   For more information about workflows, see Getting Started with Agile PLM.

6. Select ATO Number from the AutoNumber list to select an autonumber source for the selected subclass.

   The default autonumber source is ATO Number. For more information about autonumbers, see the Agile PLM Administrator Guide. Because ATOs are processed automatically, an autonumber source is required.

7. Select the object that should be processed by selecting available criteria from the Criteria list. For more information about criteria and how to create new criteria, see the Agile PLM Administrator Guide.

   Note: If you are creating a scheduled event subscriber, be sure to define your criteria as specifically as possible, to avoid receiving unwanted data in your transfer order. For example, "All Change Orders released after 8/18/2008" returns a specific group of change orders, unlike "All Change Orders" which returns every change order in your system.

8. Select the event specific to this subscriber from the Event list.

9. Click OK. The window of the new subscriber appears.

10. Select Yes or No from the Include Modified Objects drop-down list. (Scheduled Subscribers only)

    If yes, new and modified objects since the last processing of the subscriber are published. If no, only objects that have been created since the initial processing of the subscriber and meet the Criteria specified by the subscriber are published.

    Note: ATOs created from scheduled events will be limited to 100 objects on the Selected Content tab. For example, if there are 500 objects that meet the given criteria, then five ATOs are created, which allows ACS to process transfer orders in manageable amounts while still achieving the desired results.

11. Click the Subscriber Details tab to add destinations, filters, and roles, and to select the transfer file format.

12. Click to display the Subscriber Detail dialog box.

13. Click to select values for the Destinations, Filters, and Roles fields from the lists of options available for this subscriber. Roles are applied to further fine-tune or define the data extraction. For more information about roles, see the Agile PLM Administrator Guide.

14. Select the file Type of the transfer file, PDX or aXML, from the Data Format drop-down list.

    Product Definition Exchange (PDX) packages contain product content, such as item or change details, plus BOM data, manufacturer information, drawings, and other attached files. PDX packages are based on an industry-standard format for encoding structured data in an XML format. This standard provides an application-independent way to describe product content. PDX does not support all the object types supported by Agile Content Service.

    The Agile Extensible Markup Language (aXML) format is an XML representation of Agile PLM's business schema. aXML contains all product content managed in Agile PLM including items, change details, manufacturer information, problem reports, cost, drawings, and other files. aXML does support all object types supported by Agile Content Service. An aXML file is a ZIP file, which includes the XML representation of the Agile PLM content and the associated attachments.

15. Select the language to use from the Language drop-down list.

    The language setting does not affect or translate data in the transfer file; it does determine which language is used to label object attributes, for example, field and column names.

16. Select a site to use from the Site drop-down list.

    The site setting further defines the data extraction. For example, if you select the Hong Kong site, only BOM information visible for the Hong Kong site will be extracted.

17. Click Save.

    The destination detail is displayed in a row on the Subscriber Details tab.

    For each detail row you want to add, click to display the Subscriber Detail dialog box. Follow the instructions in step 13 through step 17 above.

## 5.2 Validating Subscribers

After you have created your subscriber, you should review the settings to ensure a successful transfer. Review at least the following settings:

- Destination - Make sure this setting points to the correct location and the connection has been verified. Make sure that the appropriate personnel are designated for notification.

- Event - If it is a scheduled event, make sure the proper schedule is set. If it is a workflow event, make sure it is set to the proper workflow and status.

- Filter - Make sure there is a filter for each object you want to transfer.

- Roles - Make sure the correct fields are being extracted.

If the criteria, events, and filters are not well defined for a subscriber, Agile Content Service may not trigger the ATO or you may not receive the expected results in the ATO.

## 5.3 Enabling and Disabling Subscribers

When a subscriber is created, it is disabled by default. This allows all fields of the subscriber to be changed before it is used. You must enable a subscriber before it is recognized by the Agile Content Service.

When a subscriber is enabled, you cannot edit its subscriber details and you cannot edit any of its referenced destinations, events, or filters. If any of these settings require changes, you must disable the subscriber.

To enable or disable a Subscriber:

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

2. Select the subscriber you want to enable or disable.

3. Click Enable or Disable.

## 5.4 Deleting Subscribers

Subscribers can be deleted only if they are disabled and not currently assigned to any transfer order objects.

To delete a subscriber:

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

2. Select the subscriber you want to delete.

3. Click .