ONVIF:...Payload(3pm)

💖 ONVIF:...Payload — the manual page, but make it make sense 💖

okay bestie, so this is ONVIF:...Payload(3pm), a User Contributed Perl Documentation page, and honestly? it's giving "niche but iconic." it lives in the ONVIF::Analytics::Types family and it's here to explain one very specific little data type. let's get into it 🫶

---

✨ NAME ✨

ONVIF::Analytics::Types::ActionEngineEventPayload — that's the whole name, that's the whole vibe. she's long, she's specific, she ate 💅

---

🌸 DESCRIPTION 🌸

so. this is a Perl data type class for the XML Schema defined complexType ActionEngineEventPayload, and it comes from the namespace http://www.onvif.org/ver10/schema. periodt.

and what does that data structure actually do, you ask? okay so — the Action Engine Event Payload data structure contains the information about the ONVIF command invocations. the way that it works is: since this event could be generated by other or proprietary actions, the command invocation specific fields are defined as optional, and an additional extension mechanism is provided for future or additional action definitions. so she's flexible, she's forward-thinking, she's planning ahead. main character energy fr fr ✨

🎀 PROPERTIES 🎀

these are the properties you can access using the get_PROPERTY / set_PROPERTY methods. like, that's the whole access strategy, no cap:

• RequestInfo
• ResponseInfo
• Fault
• Extension

four of them. little squad. 💜

---

🔥 METHODS 🔥

💫 new

Constructor!! the classic. you call new(), you pass her a data structure, and the following data structure may be passed to new():

 { # ONVIF::Analytics::Types::ActionEngineEventPayload
   RequestInfo =>  { # ONVIF::Analytics::Types::Envelope
     Header =>  { # ONVIF::Analytics::Types::Header
     },
     Body =>  { # ONVIF::Analytics::Types::Body
     },
   },
   ResponseInfo =>  { # ONVIF::Analytics::Types::Envelope
     Header =>  { # ONVIF::Analytics::Types::Header
     },
     Body =>  { # ONVIF::Analytics::Types::Body
     },
   },
   Fault =>  { # ONVIF::Analytics::Types::Fault
     faultcode =>  $some_value, # QName
     faultstring =>  $some_value, # string
     faultactor =>  $some_value, # anyURI
     detail =>  { # ONVIF::Analytics::Types::detail
     },
   },
   Extension =>  { # ONVIF::Analytics::Types::ActionEngineEventPayloadExtension
   },
 },

look at her. nested hashes all the way down. RequestInfo and ResponseInfo both carry a Header and a Body (Envelope things, yk), Fault brings faultcode as a QName, faultstring as a string, faultactor as an anyURI, and a detail, and then Extension is just sitting there ready for whatever future definitions show up. iconic structure honestly 🧚

---

👑 AUTHOR 👑

Generated by SOAP::WSDL. yeah, a machine did this. she's auto-generated and still serving. respect. 💀✨

---

and that's the whole page bestie!! 💖 this was documented as ONVIF:...Payload(3pm) under perl v5.40.1, dated 2026-02-01 — so yeah, timestamped, versioned, and officially in the User Contributed Perl Documentation. slay, go call new() on something 🦋🌸