Browse Prior Art Database

Method and System for Using XML for Hierarchical Workflow Assignments

IP.com Disclosure Number: IPCOM000238327D
Publication Date: 2014-Aug-18
Document File: 3 page(s) / 186K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system is disclosed for using Extensible Markup Language (XML) to integrate organization hierarchy in a Business Process Management (BPM) system for workflow assignments.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 66% of the total text.

Page 01 of 3

Method and System for Using XML for Hierarchical Workflow Assignments

In a typical Business Process Management (BPM) system, a Lightweight Directory

Access Protocol (LDAP) server is generally used as a place to define list of all team members to be used for workflow assignments. As a result, participating BPM products either have proprietary code or require custom code for accessing data in the LDAP server. Overall configuration inevitably becomes tedious and partially error-prone because creation of the list of team members is not tied to the creations of the

workflows. Also, in an enterprise, the information technology infrastructure is generally managed by teams other than the business teams. Lastly, the LDAP servers do not provide the mechanism to create more complex team lists such as organization charts thereby leading to inflexibility in a workflow design.

Disclosed is a method and system for using Extensible Markup Language (XML) to integrate organization hierarchy in a BPM system for workflow assignments. The method and system leverages actual organization charts for defining work assignments. The method and system separates creation of the organization charts from configuring the workflows and the BPM system. Therefore, system administrators need not recreate something as complex as the organization chart in components such as an LDAP server. The organization charts are created using tools and products that can export the information into XML.

Fig. 1 i...