You are here:
Customize Field Mappings for Jamf Discovery
Customize the Jamf field mappings to capture Jamf data that isn't mapped by default. Map additional Jamf attributes to CMDB fields to keep discovered device data aligned with your organization's needs.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with Agentforce IT Service that have Discovery enabled. |
| User Permissions Needed | |
|---|---|
| To edit and activate the integration flow: | Manage Flow |
| To create custom fields on a configuration item type: | Customize Application |
- Create a Jamf Pro discovery target. See Create a Discovery Target for Jamf Pro.
- To capture a Jamf attribute that isn't mapped by default, create a custom field on the CI type, and note its API name. For more information, see Create a Configuration Item Type.
Jamf field mappings are defined in the transform elements of the integration flow, not on the Field Mapping page in the target setup flow. Each Jamf target has two flows: a Compute flow and a Mobile flow. For more information, see Create or Modify a Flow.
Note
- Custom mappings that you add in a flow don't appear on the Field Mapping page. The page always shows the default mappings.
- Custom mappings apply only to the target whose flow you edit. If you create another target, recreate the mappings in its flows.
-
Open the Jamf discovery flow for the device category that you want to change.
Flow Device Category Compute flow Mac computers and their installed software. Mobile flow Mobile devices and their installed software. -
In the flow, select the transform element for the data that you want to map.
To change software mappings, select the transform element for installed software. For more information, see Transform Element.
-
Map the Jamf attribute to the CMDB field.
To capture an attribute that isn't mapped by default, map the attribute to the custom field that you created.
- Save the flow as a new version, and then activate the new version.
After you activate a new flow version, the next run syncs all devices instead of only the devices that changed. If you turn the target off and on, the next run also syncs all devices.
Did this article solve your issue?
Let us know so we can improve!
