Ingestion is the process of uploading data from ESM deployments to the M42Next cloud platform. M42Next uses Aurora Common Object Models (ACOMs) to store and process data.
ACOMs cannot be uploaded if they have fields marked as Required that are not present.
You can find all the data types that can be ingested in the lists below.
The unique UUIDs which identifies the source objects this KBA originated from, for example, one or more Service Desk Tickets
List<Reference>
No
Title
Article title
String
Yes
Description
Article description; this is only text but can include markdown notation. Attachment ACOM objects, such as images, should be included as a special notation as follows: ??attachmentId??, where attachmentId is the unique identifier of the attachment ACOM object referenced in the article. Attachments only need to be included if they cannot be referenced by a URL accessible by the consuming application.
String
Yes
Attachments
List of unique IDs of related attachments
List<Guid>
No
Url
Article url; this can be a link to a website or some other resource such as the DWP application link
String
No
Version
Gets or sets VarVersion
KbaVersion
No
Status
Article status
String
No
Categories
A list of references of categories that can be used to group articles together
List<Reference>
No
RelatedArticles
Unique UUIDs which identify related articles
List<Guid>
No
RelatedTickets
Unique UUIDs which identify related tickets
List<Guid>
No
Type
Type of the KB article (General, Known Error,...)
Type
No
Rating
Rating of the article; this can be a number between 0 and 5
Int [Range (0,5)]
No
Expiration
ISO-8601 format of the date and time when the article will expire
DateTimeOffset
No
Author
Unique Identifier or External Reference of the author of the KBA
Reference?
No
Visibility
Visibility setting for the KBA, indicating how its accessible
KbaVisibility
No
Comments
Chronologically ordered list of comments made on the article
Type of the ticket (e.g., Ticket, Incident, Service Request, Problem)
String
No
Priority
Priority level of the ticket (e.g., Low, Medium, High, Critical)
String
No
Status
Current status of the ticket (e.g., Open, In Progress, Resolved, Closed)
String
No
StatusHistory
List of status changes that have occurred for the ticket
List<ServiceDeskTicketStatusHistory>
No
CreatedBy
Identifier or a reference of the user who created the ticket
Reference
No
EntryBy
What channel was used to initiate this ticket (email, phone, portal, etc.)
String
No
CausedBy
Causes of the problem
List<Guid>
No
AssignedTo
Identifier or reference of the user to whom the ticket is assigned
Reference
No
AssignedToRole
Identifier or reference of the role to whom the ticket is assigned
Reference
No
AffectedUsers
Identifiers or References of the users who are affected by the issue
List<Reference>
No
AffectedAssets
List of assets affected by the change
List<Guid>
No
AffectedServices
List of services affected by the change
List<Guid>
No
Title
Short title of the ticket
String
Yes
Description
Detailed description of the issue or request. This can include markdown notation.
Attachment ACOM objects, such as images, should be included as a special notation as follows: ??attachmentId??, where attachmentId is the unique identifier of the attachment ACOM object referenced in the article. Attachments only need to be included if they cannot be referenced by a URL accessible by the consuming application.
String
Yes
Attachments
Gets or sets attachments
List<Guid>
No
Category
Category of the ticket (e.g., Hardware, Software, Network)
Reference
No
Subcategory
Subcategory for more specific classification (e.g., Printer, Email, Router)
Reference
No
Impact
Impact level of the ticket (e.g., Low, Medium, High)
String
No
Urgency
Impact level of the ticket (e.g., Low, Medium, High)
String
No
SLA
Service Level Agreement that applies to the ticket
Reference
No
Resolution
Resolution details if the ticket is resolved
String
No
ResolutionDate
ISO-8601 format of the date and time when the ticket was resolved
DateTimeOffset
No
RelatedTickets
List of related ticket IDs for tracking linked issues
List<Guid>
No
RelatedKBAs
List of related Knowledge Base Article IDs for tracking linked issues
Unique UUID identifying the subscriber this object belongs to
Guid
Yes
LastUpdatedAt
ISO-8601 format for the date and time when the object was last updated
DateTimeOffset
Yes
CreatedAt
ISO-8601 format for the date and time when the object was created
DateTimeOffset
Yes
KeyValues
Key value pairs associated to this object, and used to store additional metadata. Key value pairs are application-specific.
List<KeyValue>
No
Tags
List of tags used to label the object
List<String>
No
CloudResourceRelation
Field
Description
Data Type
Required
Relation
Relation type
RelationEnum
Yes
Id
The unique UUID for all referenceable objects
Guid
Yes
ContractRelation
Field
Description
Data Type
Required
relation
Relation type
RelationEnum
Yes
id
The unique UUID for all referenceable objects
Guid
Yes
Cost
Field
Description
Data Type
Required
Title
Title
String
Yes
Category
Cost's category (Hardware, Software, etc.)
Reference
No
Recurrency
Recurrency of the cost
Enum (Month, Quarter, Semester, Year)
No
Occurencies
Number of occurencies
Integer
No
First
ISO-8601 format of date of the first payment
DateTimeOffset
No
Last
ISO-8601 format of date of the last payment
DateTimeOffset
No
DeviceMemory
Field
Description
Data Type
Required
Type
Memory type (e.g., DDR4, DDR5)
String
Yes
Size
Memory size (in Mb)
Int
Yes
Modules
Memory modules
List<MemoryModule>
No
Display
Field
Description
Data Type
Required
Type
Display type (OLED, IPS, etc.)
String
No
Resolution
Display resolution
DisplayResolution
Yes
Size
Measured diagonally in inches
Decimal
No
Ratio
Aspect ratio of the screen (e.g., 16:9, 21:9)
String
No
RefreshRate
Screen refresh rate measured in Hertz (Hz)
Decimal
No
ResponseTime
Pixel response time measured in milliseconds (ms)
Decimal
No
DigitalCertificate
Field
Description
Data Type
Required
Id
The unique UUID which identifies this object
Guid
Yes
Issuer
Issuer of the certificate
String
Yes
SerialNumber
Serial number for the certificate
String
Yes
Subject
Subject of the certificate
String
Yes
ValidFromDate
Start date of the certificate's validity
DateTimeOffset
No
ValidUntilDate
End date of the certificate's validity
DateTimeOffset
No
Status
Status of the certificate (e.g., active, expired, revoked)
String
Yes
PublicKey
Public key of the certificate
String
No
Thumbprints
A list of thumbprints
List<Hash>
No
Algorithm
OID referencing algorithm
String
No
Usages
A list of OID referencing usages
List<String>
No
GraphicalUnit
Field
Description
Data Type
Required
Name
GPU name
String
Yes
BoardManufacturer
GPU manufacturer
String
No
Codename
GPU codename
String
No
Revision
GPU revision
String
No
Cores
Number of cores
Int
No
MemorySize
Memory size (in MB)
Int
Yes
PciDevice
Technical information about the PCI device
PCIDevice
No
KBaComment
Field
Description
Data Type
Required
Author
Author of the comment, Unique identifier or reference
Reference
No
CommentAt
ISO-8601 format of the date and time when the comment was made
DateTimeOffset
No
Content
Text content of the comment. This can include markdown notation and attachment references.
String
No
Visibility
Visibility setting for the comment
String
No
KeyValue
Field
Description
Data Type
Required
Key
The key
String
Yes
Value
The value for the key
String
Yes
LicenseAllOfCounters
Field
Description
Data Type
Required
Key
The key
String
Yes
Value
The value for the key
String
Yes
MemoryModule
Field
Description
Data Type
Required
Type
Memory type
String
Yes
Format
Memory module format
String
No
Size
Memory size (in MB)
Int
Yes
Bandwidth
Memory bandwidth (MB/s, e.g., 3200 for a DDR4-3200)
Int
No
Manufacturer
Module manufacturer
String
No
MemoryManufacturer
DRAM memory manufacturer
String
No
PartNumber
Number identifying the model of memory module
String
No
SerialNumber
Unique number identifying the memory module
String
No
Week
Week of production
Int
No
Year
Year of production
Int
No
Slot
Memory slot used by the module
Int
No
Metadata
Field
Description
Data Type
Required
Type
Type of the object (e.g., ServiceDeskTicket, ServiceDeskAnnouncement)
String
Yes
Version
Version of the object schema
String
Yes
Origin
Gets or sets the origin of the object
Origin (Enum)
No
NetworkInterface
Field
Description
Data Type
Required
Name
The name of the network interface
String
No
Description
The description of the network interface
String
No
MacAddress
The MAC address of the network interface
String
No
Ipv4Address
IPv4 address in CIDR notation
String
No
Ipv4Gateway
IPv4 gateway addresses
List<String>
No
Ipv4DnsServers
IPv4 DNS servers
List<String>
No
Ipv4FullyQualifiedDomainNames
IPv4 fully qualified domain names
List<String>
No
Ipv4Mtu
Maximum transmission unit for IPv4
Int
No
IsIpv4Primary
Indicates if IPv4 interface is primary
Bool
No
IsIpv4Virtual
Indicates if IPv4 interface is virtual
Bool
No
IsIpv4Wireless
Indicates if IPv4 interface is wireless
Bool
No
IsIpv4DhcpEnabled
Indicates if IPv4 DHCP is enabled
Bool
No
IsIpv4DnsEnabled
Indicates if IPv4 DNS is enabled
Bool
No
Ipv6Addresses
IPv6 addresses in CIDR notation
List<String>
No
Ipv6Gateway
IPv6 gateway addresses
List<String>
No
Ipv6DnsServers
IPv6 DNS servers
List<String>
No
Ipv6FullyQualifiedDomainNames
IPv6 fully qualified domain names
List<String>
No
Ipv6Mtu
Maximum transmission unit for IPv6
Long?
No
IsIpv6Primary
Indicates if IPv6 interface is primary
Bool
No
IsIpv6Virtual
Indicates if IPv6 interface is virtual
Bool
No
Ipv6Wireless
Indicates if IPv6 interface is wireless
Bool
No
IsIpv6AutoConfigEnabled
Indicates if IPv6 auto configuration is enabled
Bool
No
IsIpv6DnsEnabled
Indicates if IPv6 DNS is enabled
Bool
No
Ipv4SubNetMask
Subnet mask for the network interface
String
No
Payment
Field
Description
Data Type
Required
Title
Title for the payment
String
Yes
Category
Cost's category (Hardware, Software, etc.)
Reference
No
Status
Status of the payment (Pending, Paid, Overdue, etc.)
String
Yes
Due
ISO-8601 format of date of the first payment
DateTimeOffset
Yes
Value
The total price of the contract item
Currency
Yes
Conterparty
Counterparty of the payment
Reference
No
PCIDevice
Field
Description
Data Type
Required
VendorId
Vendor ID
String
Yes
ModelId
Model ID
String
Yes
SubSystem
SubSystem ID
String
No
Revision
Revision
String
Yes
UniqueId
Unique ID of the device
String
No
HardwareId
Device hardware ID
String
No
InstancePath
Device hardware ID
String
No
ProcessorUnit
Field
Description
Data Type
Required
Architecture
Architecture of the CPU
PlatformArchitecture
Yes
Name
Processor model name
String
No
Codename
Processor name or generation
String
No
Package
Processor package
String
No
Cores
Number of CPU cores
Int
No
Threads
Number of CPU threads
Int
No
Slot
Slot information when motherboard has multiple CPUs
Int
No
Reference
Field
Description
Data Type
Required
Id
The unique internal UUID which identifies this reference. Required if Origin is Internal or null.
Guid?
Conditional
Identifier
The unique identifier for the external object. Required if Origin is not Internal or null.
String?
Conditional
AliasIdentifier
Human readable identifier for the object
String?
No
Type
Type of the referenced object (e.g., User, UserGroup, Role)
String?
No
Origin
Specifies the origin of the reference. If Internal or null, Id is required; otherwise Identifier is required.
String?
No
DisplayValue
The display value or description of the object being referenced
String
Yes
RelationEnum
Value
Name
Description
Child
Child
Indicates a child relationship
DependsOn
DependsOn
Indicates this object depends on another
Dependent
Dependent
Indicates another object depends on this one
ServiceBookingComment
Field
Description
Data Type
Required
Author
Reference of the user who made the comment
Reference
No
CommentAt
ISO-8601 format of the date and time when the comment was made
DateTimeOffset
No
Content
Text content of the comment. This can include markdown notation. Attachment ACOM objects, such as images, should be included as a special notation as follows: ??attachmentId??, where attachmentId is the unique identifier of the attachment ACOM object referenced in the article. Attachments only need to be included if they cannot be referenced by a URL accessible by the consuming application.
String
No
Visibility
Visibility setting for the comment
String
No
ServiceDependencies
Field
Description
Data Type
Required
Id
The unique identifier for the service
Guid?
No
Bundling
Gets or Sets Bundling
ServiceBundling?
No
ServiceDeskTicketComment
Field
Description
Data Type
Required
Author
Reference of the user who made the comment
Reference
No
CommentAt
ISO-8601 format of the date and time when the comment was made
DateTimeOffset
No
Content
Text content of the comment. This can include markdown notation. Attachment ACOM objects, such as images, should be included as a special notation as follows: ??attachmentId??, where attachmentId is the unique identifier of the attachment ACOM object referenced in the article. Attachments only need to be included if they cannot be referenced by a URL accessible by the consuming application.
String
No
Visibility
Visibility setting for the comment
String
No
ServiceDeskTicketStatusHistory
Field
Description
Data Type
Required
Status
The status of the ticket
String
No
Date
ISO-8601 format of the date and time when the status change occurred
DateTimeOffset?
No
Description
A description of the status change
String?
No
ChangedBy
Identifier or reference of the user who changed the status
Reference?
No
ServiceOperationalPeriod
Field
Description
Data Type
Required
StartDate
ISO-8601 format of the start date of the operational period
DateTimeOffset?
No
EndDate
ISO-8601 format of the end date of the operational period