When Hudu pulls in data from external platforms, it uses a concept called a card to allow you to easily store and move this information; "stacking" information from multiple sources under a single, readable asset. These are then stored within customizable asset layouts (categories), inside each of your client spaces.
Cards can contain data from numerous different sources; including manual input, import from .csv, or from external sources (API & integrations). But, a single card can only contain data from a single source (manually entered information and imported information are both treated as "custom").
Multiple cards, that match based on the company they belong to as well as by asset name, will again be "stacked" under a single asset. If perhaps, a mismatch occurs, however, you can always move an integration card to another asset.
Guides
Advantages of the Card
If you're coming from other documentation providers, you may be wondering what the benefits of cards are, and why we felt the need to create a new concept within our product.
Cards provide the following benefits:
- Consolidation of your documentation system.
- Information on a singular asset is no longer stored on different pages; requiring less manual creation of relationships within your documentation.
- Fewer clicks are performed, and your technicians are happier.
- Consolidation across multiple services.
- Information from multiple sites and services is merged into a singular asset page; allowing for better organization and simpler workflows.
- Custom documentation.
- Add missing information that your integrations may not collect.
- Create custom fields; add comments; passwords; attach photos and files, and more; all displayed on the same page as data from your integrations.
How are Cards added to Hudu?
Custom Cards
Information that gets added to assets - either via an import into a custom asset layout or via manual input into asset layout fields - will be placed into a custom card. The custom card will be found at the top of an asset page (it's always the first card under an asset) and will be the only card with editable details (from inside Hudu).
The fields created/added to a specific asset layout (Hudu admin >> asset layouts), will be the fields that get populated into your custom cards.
By adding or removing fields, you'll be adding/removing the ability for those fields to be populated with information, across all of your client spaces.
Visit our Asset Layouts article to learn more about custom fields and asset layouts!
Integration Cards
When you first set up an integration within Hudu, you will choose which asset layout to place information in.
- For example, you might designate Office 365 users to go into an asset layout named "People" or "Contacts".
Cards being pulled in will first look for a matching asset; Hudu utilizes a matching algorithm that uses a variety of different factors to place cards, but the company name and name of the asset are priority elements that it will look for.
If the matching algorithm finds a suitable asset, then it will place the card under that asset. If the algorithm did not find a matching asset, then one will be created.
Once an asset and card are paired, they will stay paired. As an admin or super-admin, you can rematch an integration card to a different asset by navigating to that card and hitting "Move".
Tools
The sections below introduce tools related to cards. Expand each section to learn more!
Re-Sync Card
Native integrations will automatically update and re-sync every 3 hours. This timeframe can be bypassed in numerous ways; one of which lives directly on each asset integration card.
Within an individual asset, by clicking the re-sync at the top of any integration card, you can kick-start a new sync for that particular card; no other cards being pulled in from the same integration will be affected.
Move Card
As mentioned previously, cards being pulled in are matched using a variety of different factors; with the company name and name of the asset being at the top of the list.
Ideally, every asset being brought in from your integrations will get matched and sorted into the correct and appropriate asset. If, however, a mismatch occurs, at the top of every integration card resides a Move button (right next to the re-sync card). This allows you to change the asset layout that an integration card belongs.
For example, "John's Desktop" (an asset that is being pulled in from Syncro) may have been placed inside of an asset layout named "Printers", and you would like to move it to "Workstations".
By clicking move you can select which asset layout you'd like to move it to (Workstations), and choose to either:
-
- Create a new workstation asset to place John's Desktop asset within; or
- Merge 'John's Desktop', with an already existing asset (i.e. "Johns_Desktop").