Work Product represents the artifact, outcome or a deliverable created or consumed during the process. In the overall context of a process, a work product progresses through various states due to increased maturity or added content. This change in state can happen within a workflow or through the course of different workflows during the product or program lifecyle. For example, a work product like 'Software Project Plan' would typically go through change in states like 'draft', 'under review', 'approved', and 'released' in a software engineering process.

Similar to other modeled process elements, work products can also be modeled and then reused across processes.

The reporting API has been extended to access the work product states via new entities:

• workProduct.getEntities(“hierarchy::HIERARCHIC,targetrole=dependentElements”) returns the list of states for a work product element
• state.getEntities(“hierarchy::HIERARCHIC,targetrole=containerElement”) returns a single element list with the work product for a specific state element
• activitiy.getEntities(“input”) and activity.getEntries(“output”) now return a list of either work products or states
• getProperty(“Dependent”) can be used to determine if an element is a normal element (= false) or state element (= true)