Viewing the Bundle Tasks
A Bundle Task is created when a Documentation Bundle is submitted for Screening.
When the Documentation Screener completes the Pre-Screening process and clicks the
button, a Bundle Task is created.![]() |
Bundle Tasks contain the list of Impacts that can be Screened. For the generation of a Bundle Task, the Impacts in the Documentation Bundles are logically organized. For example, Impacts associated with each ATA chapters can be grouped into different Bundle Tasks. The Routing table contains the logic that allows users with different roles to view different Bundle Tasks.
The Template Screeners with the appropriate Roles can view the Bundle Tasks. In the below example, the Bundle Task created for the Aircraft Maintenance Manual is available for Screening.
![]() |
On the left pane of the Bundle Tasks tab, you can view the list of Bundle Tasks with the following details.
![]() |
![]() |
The current stage of the Lifecycle of the Bundle Task defined in the Routing Table.
In the above example, the current stage of the Lifecycle is Screening.
The Creation date and time.
The Due date to complete the Screening of the Bundle Task.
The number of Hits generated and the number of impacted Templates.
You can use the following filters to narrow down your search:
Filter by Name: To narrow down your search result based on the Bundle Task name, type the name of the Bundle Task in the search box as shown below.
Filter by Documentation Type: To narrow down your search result based on Documentation Type, expand the dropdown to select the required Documentation Type as shown below.
Filter by Publication Role: To narrow down the search result based on the Publication Roles, select the required Role from the dropdown.
Note
When a user is associated with multiple Roles, this filter helps them in viewing the Bundle Tasks specific to a Publication Role.
Use the Sort options: Expand the dropdown to use the available sort options shown below.
Note
The following filter and sort options applied are retained across browser sessions:
Filter by Documentation Type
Filter by Publication Role
Use the Sort options
When the Template Screener selects a Bundle Task, the Hits can be viewed in the OEM Hits and Template sections.
![]() |
To start the Screening process, the Template Screener should pick up the Bundle Task. The Screening actions are enabled only when the Bundle Task is picked up by clicking the
button.![]() |
If the Bundle Task is not picked up, a message is displayed while hovering over the Screening action buttons as shown below.
![]() |
In addition, there can be two other buttons,
and .![]() |
![]() |
If the Bundle Task is picked up by another user, the
button appears. When is clicked, the Bundle Task is available for pick up.If the Bundle Task is picked up by you, the
button appears. This allows other users to pickup the Bundle Task.When the Bundle Task is picked up, the label Picked up by me is displayed on the Task as shown below.
![]() |
Every Impact is manually Screened by the Template Screener. In the example below, the Bundle Task contains 15 Hits - 2 impacted Templates.
![]() |
The Template Screener has access to both Template and OEM Hits sections. By clicking , you can view the sections in full screen view.
![]() |
![]() |
Under OEM Hits, the Template Screener can view the modifications made to the Tasks and Subtasks and perform the Screening actions.
![]() |
There are also few other options available for the users to sort the Hits based on the requirements.
In the Template Hits section, new versions can be initiated for the Impacted Templates. This ensures that the Templates are updated with the current changes in the OEM Manual. These Templates go through Edition and new versions are published.
![]() |
For minor Impacts that do not require a new version of the Template, the Template Screener can leave a comment and mark the Impacts as Screened.
The Template Screener can also select multiple Template Hits or OEM Hits by selecting the check boxes. They can perform mass commenting and/or Screen multiple Hits.
![]() |
When the required actions are taken and the Impacts are marked as Screened, the Bundle Task is submitted.
![]() |
The Screening of the Hits is complete and the Bundle Task is removed from the list on the left pane.