IP Library Granted Patent US 11,855,833
Granted Patent B2
US 11,855,833 · App. 17/225,216 · Granted Dec 26, 2023

Device-driven management workflow status and impact

Inventors: Rahul Parwani (Atlanta, GA); Brian Link (Atlanta, GA); Satish Venkatakrishnan (Bangalore, IN); Mohan Guttikonda (Bangalore, IN); Amogh Datar (Bangalore, IN)
Assignee: VMWARE, INC.
H04L41/065H04L41/12H04L41/22H04L63/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,855,833
App. No.
17/225,216
Granted
Dec 26, 2023
Kind
B2
Abstract

Examples of device-driven management are described. A management service can transmit a device-driven management workflow to a number of client devices. The device-driven management workflow can include workflow objects that define a branching sequence of instructions. The client devices can provide a corresponding plurality of completion statuses for a step of the device-driven management workflow. The management service can identify a failure of the step according to a set of failure rules, and visually emphasize the failure within a representation of the device-driven management workflow.

Claims (57)

1. A method, comprising:

transmitting, by a management service, a device-driven management workflow to a plurality of client devices, wherein the device-driven management workflow comprises a plurality of workflow objects that define a branching sequence of instructions that branches according to at least one conditional workflow object that provides a branching point that causes a respective client device to evaluate a device condition to select a device-specific path through the branching sequence of instructions;

receiving, by the management service from the plurality of client devices, workflow status data comprising a plurality of completion statuses for a step of the device-driven management workflow, the step comprising at least one workflow object including a conditional workflow object;

generating, by the management service, a user interface comprising: a device information area that includes a listing of the plurality of client devices as a list or a table, and a workflow area that includes a representation of the device-driven management workflow comprising a representation of the conditional workflow object;

identifying, by the management service, a failure of the conditional workflow object of the step based on an analysis of the plurality of completion statuses according to a set of failure rules;

updating, by the management service, the device information area to visually emphasize a subset of the client devices that experience the failure of the conditional workflow object, wherein a respective client device that experiences the failure is listed in association with a device type identifier, a user identifier, and a status that indicates the failure of the conditional workflow object;

updating, by the management service, at least one of a border, background, or fill of the representation of the conditional workflow object in the user interface to visually emphasize the failure within the representation of the device-driven management workflow; and

generating, by the management service, the user interface to show a recommendation to correct the failure, the recommendation comprising: a corrective measure to correct the failure, and a user interface element that when selected replaces or modifies at least a portion of the device-driven management workflow to correct the failure.

2. The method of claim 1 , wherein the respective client device performs the device-specific path through the branching sequence of instructions based on at least one client-device-evaluated state that is specified by the device condition of the respective client device.

3. The method of claim 1 , wherein the workflow status data provides an indication of at least one device-state-specific branch taken by the respective client device through the branching sequence of instructions of the device-driven management workflow.

4. The method of claim 1 , wherein the failure is correlated with a failed workflow object of the at least one workflow object of the step, and the user interface is updated to visually emphasize the failed workflow object in order to visually emphasize the failure.

5. The method of claim 1 , further comprising:

generating, by the management service, the user interface to include a list of the plurality of client devices;

identifying, by the management service, a subset of the plurality of client devices that are associated with a failed completion status; and

visually emphasizing the subset of the plurality of client devices that are associated with the failed completion status.

6. The method of claim 1 , further comprising:

identifying, by the management service, at least one corrective measure to correct the step of the device-driven management workflow.

7. The method of claim 6 , further comprising:

modifying, by the management service, the device-driven management workflow based on the corrective measure.

8. A non-transitory computer-readable medium embodying instructions executable by at least one computing device, the instructions, when executed, causing the at least one computing device to at least:

transmit, by a management service, a device-driven management workflow to a plurality of client devices, wherein the device-driven management workflow comprises a plurality of workflow objects that define a branching sequence of instructions that branches according to at least one conditional workflow object that provides a branching point that causes a respective client device to evaluate a device condition to select a device-specific path through the branching sequence of instructions;

receive, by the management service from the plurality of client devices, workflow status data comprising a plurality of completion statuses for a step of the device-driven management workflow, the step comprising at least one workflow object including a conditional workflow object;

generate, by the management service, a user interface comprising: a device information area that includes a listing of the plurality of client devices as a list or a table, and a workflow area that includes a representation of the device-driven management workflow comprising a representation of the conditional workflow object;

identify, by the management service, a failure of the conditional workflow object of the step based on an analysis of the plurality of completion statuses according to a set of failure rules;

update, by the management service, the device information area to visually emphasize a subset of the client devices that experience the failure of the conditional workflow object, wherein a respective client device that experiences the failure is listed in association with a device type identifier, a user identifier, and a status that indicates the failure of the conditional workflow object;

update, by the management service, at least one of a border, background, or fill of the representation of the conditional workflow object in the user interface to visually emphasize the failure within the representation of the device-driven management workflow; and

generate, by the management service, the user interface to include: a corrective measure to correct the failure, and a user interface element that when selected replaces or modifies at least a portion of the device-driven management workflow to correct the failure.

9. The non-transitory computer-readable medium of claim 8 , wherein the respective client device performs the device-specific path through the branching sequence of instructions based on at least one client-device-evaluated state that is specified by the device condition of the respective client device.

10. The non-transitory computer-readable medium of claim 8 , wherein the workflow status data provides an indication of at least one device-state-specific branch taken by the respective client device through the branching sequence of instructions of the device-driven management workflow.

11. The non-transitory computer-readable medium of claim 8 , wherein the failure is correlated with a failed workflow object of the at least one workflow object of the step, and the user interface is updated to visually emphasize the failed workflow object in order to visually emphasize the failure.

12. The non-transitory computer-readable medium of claim 8 , wherein the instructions, when executed, cause the at least one computing device to at least:

generate, by the management service, the user interface to include a list of the plurality of client devices;

identify, by the management service, a subset of the plurality of client devices that are associated with a failed completion status; and

visually emphasize, by the management service, the subset of the plurality of client devices that are associated with the failed completion status.

13. The non-transitory computer-readable medium of claim 8 , wherein the instructions, when executed, cause the at least one computing device to at least:

identify, by the management service, at least one corrective measure to correct the step of the device-driven management workflow.

14. The non-transitory computer-readable medium of claim 13 , wherein the instructions, when executed, cause the at least one computing device to at least:

modify, by the management service, the device-driven management workflow based on the corrective measure.

15. A system, comprising:

at least one computing device; and

instructions accessible by the at least one computing device, wherein the instructions are executed causing the at least one computing device to at least:

transmit, by a management service, a device-driven management workflow to a plurality of client devices, wherein the device-driven management workflow comprises a plurality of workflow objects that define a branching sequence of instructions that branches according to at least one conditional workflow object that provides a branching point that causes a respective client device to evaluate a device condition to select a device-specific path through the branching sequence of instructions;

receive, by the management service from the plurality of client devices, workflow status data comprising a plurality of completion statuses for a step of the device-driven management workflow, the step comprising at least one workflow object including a conditional workflow object;

generate, by the management service, a user interface comprising: a device information area that includes a listing of the plurality of client devices as a list or a table, and a workflow area that includes a representation of the device-driven management workflow comprising a representation of the conditional workflow object;

identify, by the management service, a failure of the conditional workflow object of the step based on an analysis of the plurality of completion statuses according to a set of failure rules;

update, by the management service, the device information area to visually emphasize a subset of the client devices that experience the failure of the conditional workflow object, wherein a respective client device that experiences the failure is listed in association with a device type identifier, a user identifier, and a status that indicates the failure of the conditional workflow object;

update, by the management service, at least one of a border, background, or fill of the representation of the conditional workflow object in the user interface to visually emphasize the failure within the representation of the device-driven management workflow; and

generate, by the management service, the user interface to include a user interface element that when selected replaces or modifies at least a portion of the device-driven management workflow to correct the failure.

16. The system of claim 15 , wherein the respective client device performs the device-specific path through the branching sequence of instructions based on at least one client-device-evaluated state that is specified by the device condition of the respective client device.

17. The system of claim 15 , wherein the workflow status data provides an indication of at least one device-state-specific branch taken by the respective client device through the branching sequence of instructions of the device-driven management workflow.

18. The system of claim 15 , wherein the failure is correlated with a failed workflow object of the at least one workflow object of the step, and the user interface is updated to visually emphasize the failed workflow object in order to visually emphasize the failure.

19. The system of claim 15 , wherein the instructions, when executed, cause the at least one computing device to at least:

generate, by the management service, the user interface to include a list of the plurality of client devices;

identify, by the management service, a subset of the plurality of client devices that are associated with a failed completion status; and

visually emphasize, by the management service, the subset of the plurality of client devices that are associated with the failed completion status.

20. The system of claim 15 , wherein the instructions, when executed, cause the at least one computing device to at least:

identify, by the management service, at least one corrective measure to correct the step of the device-driven management workflow.

Assignments (4)
PATENT ASSIGNMENT Recorded Aug 5, 2024
From: VMWARE LLC
To: OMNISSA, LLC
Reel/Frame 068327/0365 →
SECURITY INTEREST Recorded Jul 3, 2024
From: OMNISSA, LLC
To: UBS AG, STAMFORD BRANCH
Reel/Frame 068118/0004 →
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 8, 2021
From: PARWANI, RAHUL; LINK, BRIAN; VENKATAKRISHNAN, SATISH; GUTTIKONDA, MOHAN; DATAR, AMOGH
To: VMWARE, INC.
Reel/Frame 055862/0118 →