.png?sv=2022-11-02&ss=b&srt=o&spr=https&st=2024-05-17T02%3A22%3A08Z&se=2024-05-17T02%3A32%3A08Z&sp=r&sig=VlzoEQDMVeFZ80Uwzowyp8Y5cIslBXSqUPzlUUoBZto%3D){kind=logo}
Using Pre-Builts in IAP
- 02 Apr 2024
-
DarkLight
-
PDF
Using Pre-Builts in IAP
- Updated on 02 Apr 2024
-
DarkLight
-
PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Components
Prebuilts allow developers to accelerate execution of network automation use cases within IAP (Itential Automation Platform). More specifically, pre-builts combine the abilities of multiple components that live within IAP. As such, a pre-built can be comprised of the following component types:
- Automations (Operations Manager)
- Form
- JSON Forms
- Integrations
- Integration Models
- Command Template (MOP)
- Analytic Template (MOP)
- Service Catalog
- Template
- Transformation
- Triggers (Operations Manager)
- Workflow
Each of these components serves a specific role to help various network use cases. You can read more about each component in their respective product documentation guides on docs.itential.com.
Terminology
The following terms apply to the use of pre-builts in Admin Essentials.
| Term | Description |
|---|---|
| Prebuilt | A prebuilt automation uses other IAP components to execute a certain network use case. |
| Component | A component is a building block of a prebuilt. Each component helps serve as a tool in a network automation use case. |
| IAP Dependency | An IAP dependency is an application or adapter that is required by the pre-built to be in the current IAP environment for the pre-built to function properly. |
Was this article helpful?
