Abstract: Methods, systems, apparatuses, and computer program products are provided for developing, debugging, and growing workflows. Embodiments enable the developer to test the workflow in place in a workflow designer that displays input/output parameter values for each workflow step during the test run. The developer is enabled to toggle the workflow step(s) between a development mode, where the developer may edit input parameter values, and a test mode, where the developer is displayed (but cannot edit) the input parameter values and is displayed the output parameter values at each workflow step. A record of workflow runs of a workflow is also maintained. The developer is also enabled to transition a workflow from being a business application to a robust software application having additional functionality. The workflow logic generated is transported between a visual workflow designer and a full-blown code editor.

Abstract: Methods, systems, apparatuses, and computer program products are provided for developing workflows. An input control may be rendered in association with the rendered representation of a workflow step corresponding to an input parameter. A developer is enabled to interact with the input control to select a parameter value for the input parameter. A workflow is enabled to be developed that includes a push notification workflow step configured to issue a push notification when encountered in the work flow and to wait for a response before enabling the workflow to continue. A workflow saved in a user folder is enabled to be selected for insertion into further workflows. A subscription workflow step may be selected for inclusion in a second workflow that is configured to wait for output information from a subscribed-to workflow before enabling the second workflow to continue.

Abstract: Optimized execution order results (e.g., from a Rete algorithm graph) are correlated with a production ordering selected by a user, thereby more accurately modeling the user's understanding of how productions relate to one another during execution in a rule system. An execution report shows in the user-selected order for each of the rules, whether the rule was executed, the inputs matched to partial conditions of the rule, and partial condition evaluation results. User rule management experience is also enhanced in other ways. For example, a graphical user interface permits user selection of a schema xpath, bulk selection of XML schema nodes to define vocabulary used in rules, if-then-else rules, rules with embedded SQL, marking rules as active or not, receiving multiple kinds of input from a single text input box, locally executing rules, importing rules authored elsewhere, iterating over a collection of objects, and validating rules against vocabulary data types.

Abstract: A workflow development system is described that provides a developer with a search utility for finding steps for inclusion in a workflow. The system also automatically generates a meaningful name and/or graphical representation for a workflow. The system also provides a graphical user interface that represents output parameters of a first workflow step as user-interactive objects. These objects can be interacted with to cause the objects to be inserted into a data entry element that is used to specify a value for an input parameter of a second workflow step. When executable logic representing the first and second workflow steps is generated, the insertion of the objects into the data entry element has the effect of causing the value of the input parameter of the second workflow step to be defined to include the values of the output parameters that correspond to the inserted objects.

Abstract: A workflow development system is described herein that includes a graphical user interface (GUI) that is configured to selectively and dynamically allocate relatively more of a display area to a particular one of a plurality of different, simultaneously-displayed workflow step representations than is allocated to the other workflow step representation(s) to facilitate user interaction the particular workflow step representation. Such allocation may be carried out in response to user interaction with the particular workflow step representation or in response to a determination that a user is otherwise focused on the particular workflow step representation. In embodiments, the workflow step representations represent different workflow steps in a series of workflow steps. In further embodiments, the workflow step representations represent different workflow steps that may be performed depending upon the evaluation of a condition.

Abstract: Methods, systems, apparatuses, and computer program products are provided for developing user applications that include workflows, and in particular, for developing the user applications and workflows in parallel. A first user interface is provided on a display screen that enables a graphical user interface (GUI) of a user application to be configured. Controls are enabled to be selected for inclusion in the GUI of the user application. Workflow logic is enabled to be associated with a control included in the GUI. A second user interface is provided on the display screen concurrent with the first user interface. The second user interface enables the workflow logic to be generated. Steps are enabled to be selected for inclusion in the workflow logic. Each step is configured to operate on data entered via the GUI and/or data of another step of the workflow logic.

Abstract: A data preservation device includes a circuit board configured to be positioned within a memory module slot of a computing device and releasably engage a memory bus of the computing device. A non-volatile memory storage device is electrically coupled to the circuit board. A control circuit is electrically coupled to the circuit board and is configured to read a data portion from the computing device and write the data portion to the non-volatile memory storage device during the occurrence of a power failure event on the computing device. An independent power supply is configured to power the data preservation device during the power failure event.

Abstract: A distributed order orchestration system for orchestrating a business process of an order fulfillment system receives from an interface a definition of the business process and generates metadata from the definition. The system then generates an abstract syntax tree from the metadata. The tree includes a plurality of nodes and one or more of the nodes correspond to a predefined template. The system then generates executable orchestration code based on the abstract syntax tree and the predefined template.

Abstract: A system for powering on downstream devices includes a master device; a first slave device; and a first communication link connecting the master device to the slave device for enabling the master device to transmit data signals to the slave device. The master device includes a power-on signal generator for injecting a power-on signal onto the communication link and the first slave device includes a power-on signal receiver for detecting the power-on signal injected on the communication link by the power-on signal generator and powering on the first slave device.

Abstract: A distributed order orchestration system for orchestrating a business process of an order fulfillment system receives from an interface a definition of the business process and generates metadata from the definition. The system then generates an abstract syntax tree from the metadata. The tree includes a plurality of nodes and one or more of the nodes correspond to a predefined template. The system then generates executable orchestration code based on the abstract syntax tree and the predefined template.

Abstract: Described is an electronics system having an individually replaceable electronics module installed therein. The individually replaceable electronics module includes a component, a light-emitting device (LED) disposed near the component, a processor module for performing diagnostics on the component and producing a message based on results of the diagnostics, and a microcontroller in communication with the processor module to receive the message produced by the processor module. The microcontroller determines whether the component is faulting based on the message. A DC power source is coupled to supply power to the microcontroller after the individually replaceable electronics module is electrically disconnected from the electronics system so that the microcontroller can illuminate the LED if the received message indicates that the component is faulting.

Abstract: A method is provided that finds the largest ‘k’ difference values in decreasing order from a list of ‘n’ arbitrary numbers. The method uses the property of sorted numbers to organize the list of all the differences in a way that reduces the size of the solution space. The time complexity of the solution space using the method is O(k2), as compared to O(n2) in the conventional exhaustive method. The overall time complexity of the method is bound by the complexity of the algorithm used to sort the input list of numbers. The memory complexity of the method is less than the exhaustive method when k<<n.

Abstract: A structured method of matching schemas that uses multiple levels of ontologies is disclosed. The method maps functions of a target system to a process ontology and maps functions of a source system to the process ontology to produce a first mapping of target functions and source functions using the process ontology. The method identifies target function parameters upon which the target functions operate and identifies source function parameters upon which the source functions operate. Then, the method maps the target function parameters to a concept ontology and maps the source function parameters to the concept ontology to produce a second mapping of the target function parameters and the source function parameters using the concept ontology. This second mapping is enhanced by mapping the target function parameters to a data-type ontology and mapping the source function parameters to the data-type ontology.

Abstract: The quality assurance of all released runset files should ideally be 100% complete to ensure the best quality of the runsets. This means that the designs used for testing should be sufficient to test all of the design rules with the appropriate data in the runset to reach 100% coverage, which is not easy to ensure. The present invention provides a methodology that addresses this problem by quantitatively measuring the test coverage of backend verification runsets. The methodology not only reports the uncovered rules, but also assists the quality assurance engineers in locating reasons as to why those rules are not covered and how coverage can be improved by designing appropriate test cases.