Skip Headers

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

Previous | Next |

# 3 Setting and Editing Events

Events determine when content is transferred to a destination. These are handled from the Events node.

Events can be based either on a schedule or on an object's moving to a specified workflow status. For example, if you wanted to query for objects matching a specific definition every night at midnight, you would create a scheduled event. Or if you wanted to watch for all change orders moving to a Released status, you would create a workflow event.

## 3.1 Scheduled Events

Scheduled events are repeated after a specified period of time has elapsed, or at a specific time hourly, daily, or weekly. When a scheduled event is processed, all Agile PLM objects that meet the definition specified in the subscriber that have not been processed are extracted.

Agile PLM provides an example scheduled event that is set to trigger at midnight on Saturday and Sunday. This event can be used when creating a subscriber if the schedule properties meet your company's needs. (For information about subscribers, see Setting and Editing Subscribers on page 37.)

To create a scheduled event:

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

2. Click . The Create Event dialog box appears.

3. Type a name and a description of the event in the specified fields.

4. Select Scheduled from the Event Type list.

5. Click in the Frequency field to schedule the event.

6. Review the following schedule properties and change them, if necessary.

   The default setting is Every X hours Y Minutes. If you accept this default, you must select a time interval.

   Setting | Action
   --- | ---
   Once A Day | Automatically runs the extraction once a day at the designated start time.
   Every X Hours Y Minutes | Specifies the time interval between extractions, calculated from the Starting At time: If the previous extraction is not finished, the next extraction follows after the previous extraction is complete. The minimum time is 0 hours, 5 minutes: the maximum time for each field is 11 hours and 59 minutes.
   Starting At | Specifies an absolute time to start checking for subscriber criteria. If the starting time and ending time are the same, the subscriber criteria are checked for 24 hours.
   Ending At | Specifies an absolute time to stop checking for subscriber criteria.
   Days | Specifies the days to process extractions according to the hourly schedule.

7. Click OK.

## 3.2 Workflow Events

Workflow events enable subscribers to publish data based on a status change of an object. When the workflow status of an object changes and a subscriber is configured for that particular change, the data is published. A subscriber cannot act on the first status of a workflow, such as Pending.

Agile PLM provides an example workflow event that is set to trigger when change orders are released. This event can be used when you create a subscriber if the workflow properties meet your company's needs.

Note: Only the object controlled by the workflow is extracted. For example, the Example Workflow Event uses the Default Change Orders workflow and the Released status. The triggering event is when any routable object using the Default Change Orders workflow makes a status transition into the Released status. The routable object and its associated objects (for example, affected items) and attachments are extracted and published.

Any changes to an object after Agile Content Service is triggered to process it, but before the extraction process begins, are reflected in the extracted content. For example, if a subscriber is configured to publish an ECO at the Review status, but the ECO is immediately promoted to the Released status, then the extracted status for the ECO may be Released.

To create a workflow event:

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

2. Click . The Create Event dialog box appears.

3. Type a name and a description of the event in the specified fields.

4. Select Workflow from the Event Type list.

5. Select a workflow from the Workflow list.

6. In the Workflow Status field, select a status from the list of available values based on the selected workflow.

7. Click OK.

## 3.3 Editing Events

You cannot change the event Type after the event is created, but you can change the Frequency field in a scheduled event and the Type of workflow in a workflow event.

You cannot edit an event if it is referenced by an enabled subscriber. You must disable the subscriber before any changes can be made to the event. See Enabling and Disabling Subscribers on page 39 for more information.

To edit a scheduled event:

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

2. Double-click the scheduled event you want to edit.

3. Edit the General Information tab of the event.

4. Make changes to the Name and Description fields, if necessary.

5. Click the button next to the Frequency field.

6. Make the necessary changes to the schedule.

7. Click OK.

8. Click Save.

To edit a workflow event:

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

2. Double-click the workflow event you want to edit.

3. Edit the General Information tab of the event.

4. Make changes to the Name and Description fields, if necessary.

5. Select a different workflow from the Workflow list, if necessary.

6. In the Workflow Status field, select a different workflow status, if necessary.

7. Click Save.

## 3.4 Deleting Events

You can delete an event only if it is not assigned to a Subscriber.

To delete an event:

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

2. Select the event you want to delete.

3. Click .