Module 2: Understanding
Launch Points
THE 'WHEN' AND 'HOW' OF MAXIMO AUTOMATION
UDEMY MASTERCLASS: ZERO TO ENTERPRISE
What is a Launch Point?
Definition: A configuration that defines the Event and Object that triggers
a script.
The Switch: Acts as the bridge between a user action and your Jython
code.
Strategic Choice: Choosing the right Launch Point is critical for system
performance.
The Five Major Launch Points
Object Launch Point (OLP)
Attribute Launch Point (ALP)
Action Launch Point
Integration Launch Point
Custom Launch Point
Object Launch Points (OLP)
The Workhorse: Tied to the lifecycle of a record (Work Order, Asset, etc.).
Key Events: Initialize, Save, Approve, Delete.
Save Context: 'Before Save' for validation; 'After Save' for updating related
records.
Pro-Tip: Avoid heavy logic in 'Initialize' to keep the UI fast.
Attribute Launch Points (ALP)
Field-Level Control: Triggered by a specific field on an object.
Validation: Fires when a user 'tabs out' of a field.
Action: Fires to automatically calculate or update another field.
Use Case: Recalculating SLA dates immediately when 'Priority' changes.
Action Launch Points
On-Demand: These scripts wait for a specific command.
Triggers: Pushbuttons, Workflow Nodes, or Escalations.
Benefit: Does not run automatically; gives the user or process control.
Use Case: An 'Auto-Approve' button or a 'Recalculate Risk' background
task.
Integration & Custom Launch Points
External Gateways: Designed for the Maximo Integration Framework (MIF).
Integration LP: Intercepts data during XML/CSV imports/exports.
Custom LP: Exposes your script as a direct REST API endpoint.
Use Case: Updating Asset meters via an external IoT temperature sensor.
Decision Matrix: Which LP to use?
Block a save due to missing data? -> Object (Before Save)
Calculate a field value in real-time? -> Attribute
Trigger logic from a button or workflow? -> Action
Handle inbound IoT sensor data? -> Custom / Integration
Up Next: Module 3: Working with Implicit Variables