Alternate presentation types for human workflow activities

1. A method comprising:

receiving, using one or more processors, a business process model for an application, the business process model including a human workstep, wherein input is received from a user to complete the human workstep;

receiving, using the one or more processors, a plurality of presentation type-metadatum pairs for association with the human workstep including a first presentation type-metadatum pair, having a first presentation type and a first metadatum, and a second presentation type-metadatum pair, having a second presentation type and a second metadatum, wherein the type of the first metadatum and the type of the second metadatum are selected from a set of metadata types including a tag, a Uniform Resource Identifier (URI), a Uniform Resource Locator (URL), and a file location path, and wherein the second metadatum is a different metadata type from the first metadatum;

receiving, using the one or more processors, associated user interface (UI) metadata for the plurality of presentation type-metadatum pairs; and

associating, using the one or more processors, the human workstep with the plurality of presentation type-metadatum pairs.

2. The method of claim 1 comprising:

receiving a request associated with the human workstep, the request including a requested presentation type, and

responsive to receiving the request including a requested presentation type, sending UI metadata associated with the requested presentation type to a requesting device.

3. The method of claim 2 , wherein responsive to receiving the UI metadata the requesting device renders a user interface.

4. The method of claim 1 , wherein the business process model is that of a deployed existing application.

5. The method of claim 1 , wherein the received business process model includes another human workstep, the method further comprising:

receiving, using the one or more processors, another plurality of presentation type-metadatum pairs for association with the another human workstep;

receiving, using the one or more processors, associated user interface (UI) metadata for the another plurality of presentation type-metadatum pairs; and

associating, using the one or more processors, the another human workstep with the another plurality of presentation type-metadatum pairs and associated UI metadata.

6. The method of claim 5 , further comprising:

associating the human workstep with a first group of one or more users; and

associating the another human workstep with a second group of one or more users.

7. The method of claim 6 , wherein the first group and second group include at least one common user.

8. The method of claim 6 , wherein the first group and second group include no common user.

9. The method of claim 1 , wherein the UI metadata includes one or more of a uniform resource identifier, a uniform resource locator, a tag and a file location.

10. The method of claim 1 , wherein a presentation type is one or more of a tablet and a smartphone.

11. A system comprising:

a processor; and

a memory, the memory storing instructions that when executed by the processor cause the system to:

receive a business process model for an application, the business process model including a human workstep, wherein input is received from a user to complete the human workstep;

receive a plurality of presentation type-metadatum pairs for association with the human workstep including a first presentation type-metadatum pair, having a first presentation type and a first metadatum, and a second presentation type-metadatum pair, having a second presentation type and a second metadatum, wherein the type of the first metadatum and the type of the second metadatum are selected from a set of metadata types including a tag, a Uniform Resource Identifier (URI), a Uniform Resource Locator (URL), and a file location path, and wherein the second metadatum is a different metadata type from the first metadatum;

receive associated user interface (UI) metadata for the plurality of presentation type-metadatum pairs; and

associate the human workstep with the plurality of presentation type-metadatum pairs.

12. The system of claim 11 comprising instructions that when executed by the processor cause the system to:

receive a request associated with the human workstep, the request including a requested presentation type, and

responsive to receiving the request including a requested presentation type, send UI metadata associated with the requested presentation type to a requesting device.

13. The system of claim 12 , wherein responsive to receiving the UI metadata the requesting device renders a user interface.

14. The system of claim 11 , wherein the business process model is that of a deployed existing application.

15. The system of claim 11 , wherein the received business process model includes another human workstep, the system comprising instructions that when executed by the processor cause the system to:

receive another plurality of presentation type-metadatum pairs for association with the another human workstep;

receive associated user interface (UI) metadata for the another plurality of presentation type-metadatum pairs; and

associate the another human workstep with the another plurality of presentation type-metadatum pairs and associated UI metadata.

16. The system of claim 15 comprising instructions that when executed by the processor cause the system to:

associate the human workstep with a first group of one or more users; and

associate the another human workstep with a second group of one or more users.

17. The system of claim 16 , wherein the first group and second group include at least one common user.

18. The system of claim 16 , wherein the first group and second group include no common user.

19. The system of claim 11 , wherein the UI metadata includes one or more of a uniform resource identifier, a uniform resource locator, a tag and a file location.

20. The system of claim 11 , wherein a presentation type is one or more of a tablet and a smartphone.