OT Device Creation

[David Casper]

When manually creating an OT Device there are two UI Actions. 'Save' and 'Create OT Device'

When you select save the device shows under the cmdb_ci_hardware table, but NOT under the Operational Technology app modules.  If you select 'Create OT Device' then it shows under both. 

Can anyone explain the difference? Reasoning behind it? Best practice? 
The other part of this is discovering OT devices. I'm using a SNOW SG from a third party, which works great, but it's not utilizing whatever process is behind the 'Create OT Device' UI Action.

Thanks

[Satishkumar B]

@David Casper The 'Save' UI action saves the OT device under the cmdb_ci_hardware table without additional categorization, while the 'Create OT Device' UI action also registers the device under the Operational Technology app modules, likely due to custom logic. The difference ensures that only devices explicitly marked as OT appear in the relevant modules, maintaining data integrity.

…………………………………………........................................................................................
Mark it helpful 👍and Accept Solution ✅!! If this helps you to understand.

…………………………………………........................................................................................

[David Casper]

Makes sense and appreciate the response. Any thoughts on how to ensure devices under the OT tables, when brought in through imports, are created using the same logic as the create OT device ui action? 

[David Casper]

@doug_schulzewould you be able to provide any insight on this? Thanks!