Workflow project design systems, apparatuses, and methods

1. A workflow project design apparatus comprising:

at least a memory configured to store an executable version of an object-oriented process having attributes and properties;

a model processing server comprising at least one processor and configured to compile and execute a workflow project based on the attributes and properties of the executable version of the object-oriented process;

an abstraction interface comprised by the model processing server and configured to define a mapping between the executable version of the object-orientated process and an un-executable version of the object-orientated process including related attributes and properties, wherein the un-executable version of the object-orientated process is compatible to be displayed in a web browser; and

an intermediary processing engine associated with the at least memory and configured to:

transmit the un-executable version of the object-orientated process to a client device for display in the web browser of the client device,

transmit a toolset file to the client device, the toolset file specifying a user interface to enable modification of the un-executable version of the object-orientated process,

receive, from the client device, a modify instruction to modify at least one of the attributes or properties of the un-executable version of the object-orientated process, and

store at the at least memory the modify instruction in conjunction with the un-executable version of the object-orientated process, wherein the model processing server is configured to:

update the executable version of the object-orientated process based on the modify instruction,

receive an execution instruction to execute the workflow project,

execute the updated executable version of the object-orientated process to generate a result of the workflow project, and

transmit the result to the client device for display within the user interface.

2. The apparatus of claim 1 , wherein the modify instruction includes a JSON JavaScript Object Notation (“JSON”) payload.

3. The apparatus of claim 1 , wherein the intermediary processing engine is configured to store the modify instruction in conjunction with the un-executable version of the object-orientated process.

4. The apparatus of claim 1 , wherein the modification of at least one of the attributes or properties of the un-executable version of the object-orientated process includes at least one of a property to enable, a property to disable, a value of a property, a value of an attribute, a field to be added, an activity to be added, an activity to be edited, a creation of a link to another object-orientated process, and a modification of a link to another object-orientated process.

5. The apparatus of claim 1 , wherein the toolset file specifies options of modifying the object-orientated process and options for creating additional object-orientated process within the workflow project.

6. The apparatus of claim 1 , wherein the toolset file specifies plug-in operations for the web browser of the client device.

7. The apparatus of claim 1 , wherein the object-orientated process includes at least one of a business object, a business process, a rule, a form, and a workflow.

8. The apparatus of claim 1 , wherein the un-executable version of the object-orientated process is provided in at least one of TypeScript, eXtensible Markup Language (“XML”), HyperText Markup Language (“HTML”), JavaScript, or a Cascading Style Sheet (“CSS”).

9. The apparatus of claim 1 , wherein the result is displayed in conjunction with the un-executable version of the object-orientated process.

10. The apparatus of claim 1 , wherein the result includes at least one of data from one or more databases, an outcome from an action performed on data, a generation of new data, or a generation of a form.

11. A workflow project design method comprising:

compiling, via a server, a workflow project based on attributes and properties of an executable version of an object-orientated process;

creating, via the server, a mapping between the executable version of the object-orientated process and an un-executable version of the object-orientated process including related attributes and properties, wherein the un-executable version of the object-orientated process is compatible to be displayed in a web browser;

transmitting, from the server, the un-executable version of the object-orientated process to a client device for display in the web browser of the client device;

transmitting, from the server, a toolset file to the client device, the toolset file specifying a user interface to enable modification of the un-executable version of the object-orientated process;

receiving, in the server from the client device, a modify instruction to modify at least one of the attributes or properties of the un-executable version of the object-orientated process;

updating, via the server, the executable version of the object-orientated process based on the modify instruction;

receiving, in the server, an execution instruction to execute the workflow project;

executing, in the server, the updated executable version of the object-orientated process to generate a result of the workflow project; and

transmitting, for the server to the client device, the result for display within the user interface.

12. The method of claim 11 , further comprising, storing, in a persistent memory, the executable version of the object-orientated process including the attributes and properties.

13. The method of claim 11 , further comprising, storing, via the server, the modify instruction in conjunction with the un-executable version of the object-orientated process.

14. The method of claim 11 , wherein the execution instruction is received from the client device or a different client device.

15. The method of claim 11 , wherein the result is displayed in conjunction with the un-executable version of the object-orientated process.

16. The method of claim 11 , wherein the result includes at least one of data from one or more databases, an outcome from an action performed on data, a generation of new data, or a generation of a form.

17. The method of claim 11 , wherein the modification of at least one of the attributes or properties of the un-executable version of the object-orientated process includes at least one of a property to enable, a property to disable, a value of a property, a value of an attribute, a field to be added, an activity to be added, an activity to be edited, a creation of a link to another object-orientated process, and a modification of a link to another object-orientated process.

18. The method of claim 11 , wherein the toolset file specifies options of modifying the object-orientated process and options for creating additional object-orientated process within the workflow project.

19. The method of claim 11 , wherein the toolset file specifies plug-in operations for the web browser of the client device.

20. The method of claim 11 , wherein the un-executable version of the object-orientated process is provided in at least one of TypeScript, eXtensible Markup Language (“XML”), HyperText Markup Language (“HTML”), JavaScript, or a Cascading Style Sheet (“CSS”).