Hudu Integration: Asset Sync

Once a customer's company link is accepted, the integration brings that company's Hudu assets into Rev.io as assets on the customer. Only assets in the layouts you selected and gave a Rev.io asset type during setup are synced. Assets in other layouts and archived assets are not brought over. Assets that exist only in Rev.io are left alone, and the integration never creates assets in Hudu.

Before creating an asset, the integration checks whether the device already exists on that customer in Rev.io, so assets you already entered aren't duplicated.

ResultDefinition
Same serial numberThe Hudu asset's Primary Serial matches an existing Rev.io asset. The assets are linked automatically, and no new asset is created.
Same MAC addressThe MAC address matches an existing Rev.io asset. This only applies when a MAC Address field is mapped for the layout. The assets are linked automatically.
Close name matchThe names are a close match, with no serial number or MAC address match. The pairing is suggested for your review on the Assets tab of the Data Sync & Mapping page. Nothing is linked or created until you decide.
No matchA new asset is created in Rev.io with the asset type chosen for the layout, filled in with the name, serial number, and mapped fields from Hudu. It is linked right away.

A name match always waits for you, because devices are often named in sequence, such as office-laptop-01 and office-laptop-02. Only a serial number or MAC address is treated as proof that two records are the same device. To get the best results, fill in Primary Serial on your Hudu assets and map a MAC Address field if your layouts have one.

The following actions are available on the Assets tab of the Data Sync & Mapping page. Each row shows the Hudu asset's name, serial number, and the asset type of the Rev.io asset it was matched to, so you can spot a pairing between two different kinds of device.

  • Accept a suggestion to confirm the two records are the same device. The asset is marked as managed by Hudu and kept in sync from then on.
  • Reject a suggestion if the records are different devices. Your Rev.io asset is left exactly as it is.

Every linked asset is marked as managed in Rev.io, so your team can see that the device is maintained in Hudu. Edit the device in Hudu, and Rev.io follows.

On every run, the integration compares each linked asset and keeps the name and serial number in sync, along with the fields you mapped during setup: Description, Operating System, IP Address, MAC Address, and Install Date. Fields you didn't map are never changed. Which system wins depends on the Asset Conflict Policy setting.

OptionDefinition
Hudu is the source of truthHudu values are written to Rev.io. A change made in Rev.io is replaced with the Hudu value on the next run.
Most recent change winsThe system that was edited since the last sync updates the other. If both were edited, the later edit wins.
Rev.io is the source of truthRev.io values are written to Hudu, including the asset name and serial number.
Don't overwriteNeither system changes the other after the asset is linked.

Only real changes are written, and formatting differences, such as a date with or without a time, don't count as changes. When an existing Rev.io asset is first linked, the policy decides what happens to any differences. Hudu is the source of truth suits most teams, because Hudu is where your documentation lives. Choose a different policy only if your team maintains asset details in Rev.io.

The following table shows what happens in Rev.io when devices are archived or removed. The integration never deletes assets in either system.

EventResult in Rev.io
Asset archived in HuduThe Rev.io asset is set to Inactive under every conflict policy. It is kept, so its history stays intact.
Asset unarchived in HuduThe Rev.io asset stays Inactive. Set it back to active in Rev.io if needed.
Asset deleted in HuduThe Rev.io asset is left as it is. Set it to inactive or retire it in Rev.io yourself.
Asset deleted in Rev.ioThe asset isn't recreated, and the Hudu asset stays as it is.

For more information about the Hudu integration, see the following articles.

Hudu Integration: Overview
Hudu Integration: Password Access
Hudu Integration: Configuration