This chapter explains how to identify an execution point. Once identified, you can then associate execution points with an extension. See "Defining An Extension" for more information. Online Help for identifying execution points is available in the help topics listed below.
Open the online Help and type the following window or procedure names in the Search field:
Execution Point Search and Results window
Execution Points window
Searching for an Execution Point
Toggling between Execution Point Search and Results
Filtering the Execution Points list
An execution point is defined by a combination of three components: its building block, process point, and action type. Oracle Communications MetaSolv Solution predefines a number of options for each of these components, along with the combinations of options that represent valid execution points. This section describes the options that are available for each component.
Building blocks are grouped into building block types. Both building blocks and building block types are MetaSolv Solution defined data. The following table lists building block types that appear in the drop-down list on the Execution Point Search window.
Building block type options:
Task Type
Gateway Event
Connection
Network System
Address
Table 3-1 lists the building blocks defined by MetaSolv Solution that can be used with extensions. The building blocks available for selection depend on the building block type chosen. The building block ID, an Oracle generated number, is included in the information because it is part of the data that is passed from an execution point to an extension Java class.
Table 3-1 Building Block Options
Building block | Building block ID |
---|---|
All Task Types |
1001 |
All Gateway Events |
1002 |
[specific task type] |
[depends on task type] |
All Connections |
409 |
All Network Systems |
410 |
All End User Locations |
- |
Specific task types are user defined data stored on the TASK_TYPE table. To support the Complete Task execution point for individual task types, the building block id field (ms_bb_id) was added to the TASK_TYPE table. A row is inserted into the TASK_TYPE table when a new task type is created in Work Management. However, the ms_bb_id field is not populated with the row insertion, rather, it is populated when the task is selected from the Name list in the Execution Point Search window. The Name list displays all task types when you select Task Type in the Building Block Type list.
Note:
This document does not provide the building block ids for each task type because they are based on user data. Building block ids are not displayed in the application, therefore, they must be manually looked up on the TASK_TYPE table.Table 3-2 lists the process points defined by MetaSolv Solution that can be used with extensions. The process points available for selection depend on the building block chosen. The process point ID, an Oracle generated number, is included in the information because it is part of the data that is passed from an execution point to an extension Java class.
Table 3-3 lists the action types defined by MetaSolv Solution that can be used with extensions. The action types available for selection depend on the process point chosen.The action type ID, an Oracle generated number, is included in the information because it is part of the data that is passed from an execution point to an extension Java class.
Action type | Action type ID |
---|---|
Generate |
32 |
Assign Jeopardy |
41 |
Reject |
42 |
Assign Queues |
43 |
Change Completion Date |
44 |
System Task Failure |
45 |
Late |
46 |
Potentially Late |
47 |
GW Event Failure |
51 |
Provision Plan Default |
52 |
Complete |
53 |
Select Component or Element |
54 |
Select Port Address |
55 |
|
56 |
Select Network System |
60 |
Select Customer Edge Component |
61 |
Select End Component For Physical Connection |
62 |
Select Equipment For CE |
63 |
DS0/DS1 Automated Design |
70 |
Connection Id Automation |
71 |
Select Dedicated Plant |
- |
Update |
91 |
Create |
92 |
As explained in each of the previous component sections, there are dependencies between the components. Specifically, action types are dependent on process points, which are dependent on building blocks, which are dependent on building block types.
Table 3-4 shows the current valid combinations that result from these dependencies. For example, if you choose a building block type of Task Type, your only choice of building block is currently All Task Types. If you then choose the process point of Task Generation, your only action type choices are Generate or Provision Plan Default.
Building block type | Building block | Process point | Action type |
---|---|---|---|
Task Type |
All Task Types |
Task Generation |
|
Task Type |
All Task Types |
Task Maintenance |
|
Task Type |
[specific task type] |
Task Maintenance |
|
Gateway Event |
All Gateway Events |
GW Event Maintenance |
|
Connection |
All Connections |
|
|
Connection |
All Connections |
PCONDES Maintenance |
|
Connection |
All Connections |
VCONDES Maintenance |
|
Connection |
All Connections |
Connection Design |
|
Network System |
All Network Systems |
Network System Design |
|
Address |
All End User Locations |
PSR |
|
Address |
All End User Locations |
EUL Maintenance |
|