MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information.

{
    "batchcomplete": "",
    "continue": {
        "lecontinue": "20240418221322|30337",
        "continue": "-||"
    },
    "query": {
        "logevents": [
            {
                "logid": 30347,
                "ns": 14,
                "title": "Category:Employee Portal",
                "pageid": 3908,
                "logpage": 3908,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Jamesa",
                "timestamp": "2024-06-10T18:47:20Z",
                "comment": "Created page with \"Employee Portal and self service\""
            },
            {
                "logid": 30346,
                "ns": 14,
                "title": "Category:Enterprise",
                "pageid": 3907,
                "logpage": 3907,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Jamesa",
                "timestamp": "2024-06-05T20:31:05Z",
                "comment": "Created page with \"Enterprise Features\""
            },
            {
                "logid": 30345,
                "ns": 14,
                "title": "Category:Service Manager",
                "pageid": 0,
                "logpage": 409,
                "params": {},
                "type": "delete",
                "action": "delete",
                "user": "Jamesa",
                "timestamp": "2024-05-23T17:17:26Z",
                "comment": "content was: \"{|style=\"width: 100%\" |- valign=\"top\" |style=\"width:73%\"| Service Manager is a powerful next generation IT Service Management application that enables IT teams to collaborate, share ideas, and manage common ITIL disciplines including Incident Management, Problem Management, Change Management, and Service Level Management. |style=\"width:5%\"| | |style=\"width:22%; border-style: soli...\", and the only contributor was \"[[Special:Contributions/Jamesa|Jamesa]]\" ([[User talk:Jamesa|talk]])"
            },
            {
                "logid": 30344,
                "ns": 0,
                "title": "Workarounds and Known Errors",
                "pageid": 0,
                "logpage": 821,
                "params": {},
                "type": "delete",
                "action": "delete",
                "user": "Jamesa",
                "timestamp": "2024-04-19T19:47:59Z",
                "comment": "content was: \"__NOTOC__[[Main Page|Home]] > [[Service Manager]] > Workarounds and Known Errors  ==Introduction==  During of following the Investigation stage it maybe determined that a permanent fix is not currently available. This is a valid outcome and could be caused by a number of reasons including - Legacy Software, Costs to upgrade, Unable to schedule downtime to apply fixes to business critical applications.     In these circumstances a '''Workaround''' maybe identified and this will...\""
            },
            {
                "logid": 30343,
                "ns": 0,
                "title": "Linking Service Level Agreements to Services",
                "pageid": 0,
                "logpage": 1242,
                "params": {},
                "type": "delete",
                "action": "delete",
                "user": "Jamesa",
                "timestamp": "2024-04-19T19:46:35Z",
                "comment": "content was: \"__NOTOC__[[Main Page|Home]] > [[Service Manager]] > [[Service Portfolio]] > [[Service Level Agreements]] > Linking Service Level Agreements to Services [[File:LinkingSLA.png|right|400px]] ==Introduction==  From the Services record and the SLA tab, you are able to:  * Link Global Service Level Agreements to a Service * Configure Service Level Agreements which are specific and only available to be used against a Service.  * Manage rules for deciding which SLA will be invoked if t...\""
            },
            {
                "logid": 30342,
                "ns": 0,
                "title": "Request and Closure Categories",
                "pageid": 0,
                "logpage": 383,
                "params": {},
                "type": "delete",
                "action": "delete",
                "user": "Jamesa",
                "timestamp": "2024-04-19T19:40:56Z",
                "comment": "content was: \"__NOTOC__[[Main Page|Home]] > [[Service Manager]] > Request and Closure Categories ==Introduction== This page describes the administration and configuration of the Request and Closure Categories which are used within the different call types.   When using ''Service Manager'' in order to retrieve accurate reports and to standardise data recorded against a call, Profiles can be implemented.  There are two sets of classifications you can use : :* '''Request categories''' - Can be...\""
            },
            {
                "logid": 30341,
                "ns": 0,
                "title": "Investigating Problems",
                "pageid": 0,
                "logpage": 818,
                "params": {},
                "type": "delete",
                "action": "delete",
                "user": "Jamesa",
                "timestamp": "2024-04-19T19:37:49Z",
                "comment": "content was: \"__NOTOC__[[Main Page|Home]] > [[Service Manager]] > Investigating Problems  ==Introduction==  Hornbill provides a sample Problem Business Process which can be used to govern Problem life cycle's.  Customers can edit or create their own Problem processes through the administration console and '''[[Business Process Designer|Business Processes]]'''.  Customers are able to define...\", and the only contributor was \"[[Special:Contributions/Stevenb|Stevenb]]\" ([[User talk:Stevenb|talk]])"
            },
            {
                "logid": 30340,
                "ns": 0,
                "title": "Incident Diagnosis & Investigation",
                "pageid": 0,
                "logpage": 675,
                "params": {},
                "type": "delete",
                "action": "delete",
                "user": "Jamesa",
                "timestamp": "2024-04-19T19:37:27Z",
                "comment": "content was: \"__NOTOC__[[Main Page|Home]] > [[Service Manager]] > Incident Diagnosis & Investigation ==Introduction==  Service Manager is a highly configurable, flexible solution which is not prescriptive in how you  manage your Incident Process. Incident Management processes can be automated, or entirely manual depending on your requirements.   ===Incident Categorization & Prioritization===  It is possible to allow both analysts and supported customers to categorise their Incidents during e...\""
            },
            {
                "logid": 30339,
                "ns": 0,
                "title": "Escalation, Resolution & Closure",
                "pageid": 0,
                "logpage": 678,
                "params": {},
                "type": "delete",
                "action": "delete",
                "user": "Jamesa",
                "timestamp": "2024-04-19T19:36:35Z",
                "comment": "content was: \"__NOTOC__[[Main Page|Home]] > [[Service Manager]] > Escalation, Resolution & Closure ==Introduction==  ===Escalation Engine===  The Hornbill platform is provided with an escalation engine, which can help ensure Incidents are managed and Service Level Targets are adhered too.  Service Levels can be created to support the differing Response and Resolution targets you wish to use...\", and the only contributor was \"[[Special:Contributions/Stevenb|Stevenb]]\" ([[User talk:Stevenb|talk]])"
            },
            {
                "logid": 30338,
                "ns": 0,
                "title": "Logging Incidents",
                "pageid": 0,
                "logpage": 671,
                "params": {},
                "type": "delete",
                "action": "delete",
                "user": "Jamesa",
                "timestamp": "2024-04-19T19:34:52Z",
                "comment": "content was: \"__NOTOC__[[Main Page|Home]] > [[Service Manager]] > Logging Incidents ==Introduction== Service Manager provides a number of different ways in which an Incident can be created and logged.   ===Logging an Incident as an Analyst===  Service Manager has been developed to provide a consumer level experience for logging Incidents (and other Request Types) by following a process of [...\", and the only contributor was \"[[Special:Contributions/Stevenb|Stevenb]]\" ([[User talk:Stevenb|talk]])"
            }
        ]
    }
}