Aspects of the present invention relate generally to the field of information systems and computer software and more specifically to process flow interfaces.
A business process that represents a process of an enterprise is typically a collection of related activities or tasks that result in a particular business outcome or goal. For example, an operational business process can illustrate the activities and tasks necessary to complete a purchasing, manufacturing, marketing, or sales goal. Other business processes can include document flows or approval flows and can describe an accounting, recruitment, or technical goal. Business processes or workflows are conventionally modeled as a flowcharts and are often complex, including details about each step in the process such as the entities involved, the creation and storage of business objects and other relevant information, or the location and transfer of materials.
However, with all the various types of information conventionally included in a business process flow, even when optimally displayed, a user still must sort through and evaluate multiple elements of each task in order to determine the status of the process flow. Accordingly, there is a need in the art for a method to provide a quick and simple understanding of the status of a process flow.
A process flow status header is displayed as part of the process flow control in a process flow control interface. The simple, quick, and easy visualization provided in the process flow status header offers the user information on the status of a business process flow at a glance by providing a visualization of the percentage of completed or created items compared to missing or incomplete items and a distribution representative of the status of each task of each step of the process flow.
The process flow status header can be used as a single control to access the process flow control from anywhere in the user interface (e.g., home and overview pages). The process flow status header can be provided throughout the various displays of the user interface to provide a single abbreviated control for complete access to the full process flow. For example, the process flow status header can be provided without showing the whole process flow itself or the associated detailed textual description.
Additionally, as shown in
According to an embodiment, the meter will include one or more colors that visually represent the status of the process flow item. For example, a portion of the meter in the process flow status indicator can be a neutral color, such as a gray color, for items in the process flow that are in progress; a negative color, such as a red color, for items in the process flow that have an issue; and a positive color, such as a green color, for items in the process flow that have been successfully completed. Additionally, for items that have not been started, have not been created, or otherwise are not yet in progress, the status indicator may be displayed as a neutral color, or have no color fill. Other colors additionally are contemplated and can form part of the visualization provided by the process flow status indicator.
According to an embodiment, the percentage of items in each category (not started, in progress, complete, or having an issue) will be presented as part of the process flow status indicator visualization. For example, if fifty percent of a process flow step is complete and the remaining fifty percent is in progress, the process flow status indicator will include an element or a meter that is filled half with a positive color and half with a neutral color as described above. Therefore, a user will be able to determine the status of the process flow with only a glance at the process flow status indicator.
For example, as illustrated, status indicator 310 is associated with a first process flow step. The status indicator 310 shows that all the items for this step are created and are in progress as the meter has been filled in a neutral color (e.g. gray). Status indicator 320 shows that all the items associated with this step are created and in progress as the meter has been completely filled in. However, an element or elements representing one third of the process step has an issue as one-third of the meter has been filled in a negative color (e.g., red) and elements representing two thirds of the process step are done as two-thirds of the meter have been filled in a positive color (e.g., green). Status indicator 330 shows that one half of the necessary elements for the associated process flow step are created and completed as one half of the meter has been filled in a positive color (e.g., green), however, the other half of the elements have not yet been initiated as one half of the meter has not yet been filled. Status indicator 340 shows that one third of the necessary elements for the associated process flow step are created and in progress as one third of the meter has been filled in a neutral color (e.g. gray), however, the other two thirds of the elements have not yet been initiated as two thirds of the meter has not yet been filled. Status indicator 350 shows that none of the elements of the associated process flow step have been initiated as the meter has not yet been filled.
According to an embodiment, if all elements or tasks of a step are completed the meter is filled completely in a positive color (e.g., green). Then, when all of the meters in the status indicator header are completely filled with a positive (e.g., green) color, then all the steps of the process flow have been completed and the process flow is finished.
According to an embodiment, and as shown in
A user may access a process flow display in a standalone client system, client-server environment, or a networked environment.
A user may access the plurality of business objects 525 stored in the storage device 520 from the client 510 via a user interface 511 capable of accessing the storage device 520 and displaying a process flow status header as described herein, the plurality of objects 525, and related metadata stored in the storage device 520. The user interface 511 may be a program or application or may comprise middleware that acts as a frontend to or otherwise facilitates access to the storage device 520. The user may interact with the user interface 511 through an input device, such as by inputting a selection as with a mouse or inputting a selection as with a keyboard. The user may observe the response to the selection on an output device or display. In accordance with an aspect of the invention, the user interface 511 may run in a browser window controlled by the user. In another aspect of the invention, the user interface 511 may run in an application window controlled by the user.
The server 640 may be a network server accessible to the client 610 via the network 630 that may manage access to storage device 620. The user interface 611 may receive instructions regarding the process flow from the user and, utilizing the objects stored in memory storage 620, facilitate a display of the simulation or the information gathered during the simulation. Multiple different clients (not shown) may access storage device 620 via the network 630 and request access to the objects stored therein.
In another networked environment, the process flow display may be executed on a network capable client and access the business other objects stored in one or more storage devices via a network and communications server.
In some applications, the modules described hereinabove may be provided as elements of an integrated software system, in which the blocks may be provided as separate elements of a computer program. Some embodiments may be implemented, for example, using a non-transitory computer-readable storage medium or article which may store an instruction or a set of instructions that, if executed by a processor, may cause the processor to perform a method in accordance with the embodiments. Other applications of the present invention may be embodied as a hybrid system of dedicated hardware and software components. Moreover, not all of the modules described herein need be provided or need be provided as separate units. Additionally, it is noted that the arrangement of the blocks in
The exemplary methods and computer program instructions may be embodied on a non-transitory computer readable storage medium that may include any medium that can store information. Examples of a computer readable storage medium include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy diskette, CD-ROM, optical disk, hard disk, fiber optic medium, or any electromagnetic or optical storage device. In addition, a server or database server may include computer readable media configured to store executable program instructions. The features of the embodiments of the present invention may be implemented in hardware, software, firmware, or a combination thereof and utilized in systems, subsystems, components or subcomponents thereof.
While the invention has been described in detail above with reference to some embodiments, variations within the scope and spirit of the invention will be apparent to those of ordinary skill in the art. Thus, the invention should be considered as limited only by the scope of the appended claims.