A hyper-automation demo: Demo 2: Oracle Change Request example: Auto-creating an Incident for automation failure

https://r-able.com : Now, for the demo. A hyper-automation demo: Demo 2: Change Request example: Auto-creating an Incident for automation failure. There are three short screen capture sessions (2-7 minutes each). Please watch them in their entirety. They are demo-ed from a user's perspective, not from an admins - because tere are no administrators exist in the hyper-automated world. They show how an end user performs a complex IT change without the help of an IT professional, just like ordering an item on Amazon or streaming a movie on Netflix without knowing all the complexities of what happens behind the scenes. In a hyper-automated implementation, there is no human intervention in the process at all (other than the initial design and maintenance of the automation logic). Here is what the unattended version of the same process looks like. This demo will show the most common DBA task - a script run. Normally, a DBA gets notified of the Change Request by email. He/she gets the details from a familiar ServiceNow (or another tool) interface. The administrator then runs the scripts in one or more databases, as requested in the change request. The hyper-automated Change Request execution process bypasses the administrator entirely. The ticketing system communicates with the automation control node in real time via the API. The approval and verification processes are also done in real time. The automation node then connects to the asset to be maintained (an Oracle database in our demo) via SSH, SQL*PLUS, or an API, and executes the Change Request.