Browse Prior Art Database

Method for providing for processing form submittion by using an address book storing history data on electoric form system

IP.com Disclosure Number: IPCOM000015706D
Original Publication Date: 2002-Jul-01
Included in the Prior Art Database: 2003-Jun-21
Document File: 8 page(s) / 140K

Publishing Venue

IBM

Abstract

Method for providing for processing form submittion by using an address book storing history data on electoric form system 1. Introduction On electoric form system when a form is being processed, personnel address books get searched to determine a next approver on the flow, and then the form is sent to him/her. Generally a manager of the form submitter is regarded as a next approver. So far electric form system could not work adequately if personnel change has happened while a form is still on the flow and is not completed yet. It means that a next approver may often be unexpected person at the time of submitting the form, since it's determined by searching a personnel addressbook which has been already changed.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 26% of the total text.

Page 1 of 8

  Method for providing for processing form submittion by using an address book storing history data on electoric form system

Method for providing for processing
form submittion by using an address
book storing history data on
electoric form system

1. Introduction

  On electoric form system when a form is being
processed, personnel address books get searched to
determine a next approver on the flow, and then
the form is sent to him/her. Generally a manager of
the form submitter is regarded as a next approver.

  So far electric form system could not work
adequately if personnel change has happened while a
form is still on the flow and is not completed yet.
It means that a next approver may often be
unexpected person at the time of submitting the
form, since it's determined by searching a
personnel addressbook which has been already
changed.

For example, at the following figure :
(1) The form which A had submitted was sent to B
who had been a boss of A at the time of submitting
the form.
(2) Before B approved the form, a personnel change
was occurred and B got promoted and moved to the
different division.(His division code has been
changed.) Then the personnel address book was
changed as human resource changed.
(3) The things which supposed to happen is, the
form should be sent to C who used to be a boss of B
before the personnel change instead of D.
(4) But actually after B approved the form, the
form was sent to D, since D is a current boss of B.

1

Page 2 of 8

 Thus many customers have demanded a new workflow
system that can prevent unexpended flows of a form
which may be caused by updating a personnel address
book in the personnel change.

2. How to resolve the problems

 To resolve problems like the example above, this
new method has adopted the following new features :

     (a) In Personnel Address Book, a history of a
division code which a submitter has belonged to

     (b) In Division Address Book, a history of a
staff name who was a manager of the division

     (c) In the form definition, an evaluation
date which represents a point when "a boss of a
submitter" is a user who was a boss of the
submitter at that point

 Generally in the case that a next approver is a
current "boss" of a submitter, the boss's user ID
can be got from the "Boss Name"colum in the
submitter record which has been searched with an
user id of the submitter as a search key in the
personnel address book.

 On the other hand, this new method uses a
different way to search the boss's user ID of the
submitter so that the problems like the example
above should be resolved.

 The following figure describes how to work with
this new method in the previous example :

 ( (a), (b), (c) written in red represent new items
which has been mentioned above.)

2

[This page contains 1 picture or other non-text object]

Page 3 of 8

Different points between an old method and new one
are like this :
(1) When the form was sent from A to B, the
received date, 8/31, is stored as "the evaluation
date" in the form.
(2) In changing human address books, it's necessa...