So - custom data is something that doesn't require LDDA. You can use LDDA (the normalisation rules for instance) which all create "new custom data" in a way .
Custom data can be as simple as "pick up a registry key value, and add it to my device at Inventory location X.Y", which you can read up on here for instance:
- How to add custom data to device inventory?
- Custom Data: Registry Search
- Custom Data Registry Scan Not Working: How To Pull Registry Information Using The Manage Software List
Be aware that you'll need to be mindful of this -- Custom Data is not Entered - Using the Unknown Items Inventory Tool -- since you won't have modelled tables (yet). That's something that I should hopefully address with a rather large doc for Interchange 2018 in Dallas.
{You can search for "custom data" under the INVENTORY branch of the EPM community & find lots of useful links }
... but there's a bunch of ways that Custom Data can be added:
- Pulled from Registry (direct)
- Pulled via script & added to registry
- Pulled via script & added to a file (more advanced & slight hackery involved)
- "Normalised" / introduced via LDDA rules (these are usually VB-based rules
- Pulled from 3rd party databases
- ... and many more (ranging from "varying degrees of hackery" to "easy peasy").
- Note that MAC & Linux function differently (and have separate / dedicated articles for custom data collection/creation).
To give you an idea how the LDDA rules work, examine existing things, such as the CALCULATIONS (those use existing data & create new data from it). For instance, the CALCULATION for "free disk space in %" is a great example (and most of those function as VB-scripts).
... and then you 2x-click a rule & can either VIEW or COPY AND EDIT the rules (we won't let you edit existing ones, but you can make a copy & then tear it to pieces).
... and this is what you get with the VIEW ONLY option for instance -- a DESTiNATION (where you want the data to go) along with "how the data is calculated", which is a VB script. Easy
That should give you a starting point from which to go from.
That way, you can for instance check "Hey, if string X is in my LDAP information, I can figure out the owner department" for instance.
The limits are kind of set by your imagination & some time obviously .