Abstract: A design-time status schema model is defined at design-time and includes a core status schema group and an. a status schema model. The status schema model includes a core status schema group and an extended status schema group. The status schema model also includes a precondition included in one of the status schema groups. The precondition identifies how a status affects whether an action included in the other of the status schema groups is to be allowed to be performed at runtime by a data object node instance having the status. Based on a status schema instance, the status of a data object node instance is monitored to determine whether the action is allowed to be performed by the data object node instance. In response to a determination that the action is allowed, enabling the action to be executed.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Abstract: Data changes during transaction processing by a computer system are constrained. An outbound processing sub-component of a first processing component is enabled to change a value of a status variable relating to processing performed on a data object instance by the first processing component. The data object instance includes values for variables and methods capable of being performed by the data object instance. The outbound processing sub-component is configured to trigger subsequent processing steps in a second processing component. The outbound processing sub-component is permitted to change only the status variable and is not permitted to change any other variable.

Abstract: A computer-implemented method of evaluating interactions between processes. The method includes storing a message choreography meta-model that includes an interaction meta class and a constraint meta-class. A user creates a message choreography model between a first process and a second process. The method further includes executing a verification computer program that performs a verification of the message choreography model. The verification includes verifying absence of an inconsumable message.

Abstract: A computer system, in which cancellation status models are used. The computer system receives a request to cancel a parent data object node instance and accesses a first cancellation building block that models a first cancellation subprocess for the first type of data object node and that is integrated in a first status schema defined for the first type of data object node. The computer system executes cancellation of the parent data object node instance by accessing data that indicates whether or not a child data object node instance is able to be cancelled and conditioning cancellation of the parent data object node instance on the accessed data indicating that the child data object node instance is able to be cancelled.

Abstract: Techniques are described for using a design-time status schema model to describe the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also includes preconditions for performing actions and a modeling element where the modeling element indicates a process step for a business process where the process step can be switched on and off at runtime. A precondition belonging to the process step identifies how a status affects whether an action is to be allowed to be performed at runtime by a data object node instance having the status. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model. The precondition is evaluated at runtime only if the process step is switched on.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Abstract: Actions are controlled actions in a computer-based process by a status schema model defined at design-time, stored in a computer-readable medium and including a precondition identifying how a status affects whether an action is to be allowed to be performed at runtime by a data object node instance having the status. A status schema instance is created for a particular data object node instance being used in a computer-based process. The status schema instance corresponds to the status schema model and includes a status variable having an inhibiting status value. Conditioned upon a determination that the data object node instance includes a value for a status variable that corresponds to the inhibiting status value of the status variable of the status schema model, actions are prohibited to be performed by the data object node instance other than an action with an explicit precondition from the inhibiting status value.

Abstract: In one embodiment the present invention includes a computer-implemented method of evaluating interactions between processes. The method includes storing a message choreography meta-model that includes an interaction meta class and a constraint meta-class. The interaction meta-class relates to an exchange of a message between a sender and a receiver, and the constraint meta-class relates to an input to the interaction meta-class. The method further includes executing a user interface computer program with which a user creates a message choreography model between a first process and a second process. The message choreography model is based on the message choreography meta-model. The message choreography model includes interactions that conform to the interaction meta class, and includes constraints that conform to the constraint meta class. The method further includes executing a verification computer program that performs a verification of the message choreography model.

Abstract: Actions are controlled actions in a computer-based process by a status schema model defined at design-time, stored in a computer-readable medium and including a precondition identifying how a status affects whether an action is to be allowed to be performed at runtime by a data object node instance having the status. A status schema instance is created for a particular data object node instance being used in a computer-based process. The status schema instance corresponds to the status schema model and includes a status variable having an inhibiting status value. Conditioned upon a determination that the data object node instance includes a value for a status variable that corresponds to the inhibiting status value of the status variable of the status schema model, actions are prohibited to be performed by the data object node instance other than an action with an explicit precondition from the inhibiting status value.

Abstract: Techniques are provided for updating a locally stored version of a data set in a multi-system environment where each system maintains a separate stored version of the data set and is capable of modifying an attribute of the data set. An attribute of a data set stored locally in a first application system is modified and a message is generated containing the data set. The message is sent to a second application system that also maintains a version of the data set. The second application system receives the data set, and the attribute is compared to the attribute stored locally by the second application system. If the comparison indicates that the version of the attribute stored locally in the second application system is less recent than the version of the attribute in the received data set, the second application system's version of the attribute is replaced with the attribute in the message.

Abstract: Techniques are provided for updating a local cache database of an application system in a multi-system environment having a central system that maintains central data objects that are shared by the multiple systems. A first application system executes an application and processes a document using a data object having a version identifier. A message is sent to a second application system including the data object used to process the document and a corresponding version identifier for the data object. The second application system receives the message, and the version identifier in the message is compared to a version identifier of a corresponding data object stored in the second application system. If the version identifier of the data object stored in the second application system indicates that a more recent version of the data object exists, the more recent version of the data object is requested from a central system that maintains the data objects and the second system is updated.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Abstract: A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.