Can the combined brains on this superb Forum help me with some ideas please?
I have 1200 users each updating case records.
There are 18 separate process within each case record which have to be completed in a specific order before a case is complete. The full case completion can take 12 months.
At the end of each of the 18 processes a record is posted to a table in the format:
Unique ID, Date, Time, Confirm. So each case record has up to 18 posted records. Some will be new, but others will be corrections or updates, so process 8 may be submitted 20 times.
The Problem.
The data has to be extracted from the post table and, according to certain rules, inserted into a different table. (The �insert� is through the host application UI to avoid licensing issues using keystroke macros into an Oracle database table. Can�t use ODBC).
The rules dictate that the order in which the data is inserted into the different table (hence the date and time), is the same order it was received.
I realise that a reverse index using the fields would present the data in the correct order however due to data volumes there will be 10 sessions running against the table and attempting to pick up data from the posted table and applying it to the Oracle table.
So, Unique ID A1B23 might have processes 1,2,3,4,5 queued.
Session 1 picks up process 1 and starts to update Oracle
Session 2 picks up process 2 and tries to insert the data but the record is locked.
Question 1. How could I handle multiple sessions picking up the correct piece of data and not trying to insert that data until the previous insert is complete and Committed.
Question 2. Has anyone done any Robotics/ Screen Scraping with Alpha?
I have 1200 users each updating case records.
There are 18 separate process within each case record which have to be completed in a specific order before a case is complete. The full case completion can take 12 months.
At the end of each of the 18 processes a record is posted to a table in the format:
Unique ID, Date, Time, Confirm. So each case record has up to 18 posted records. Some will be new, but others will be corrections or updates, so process 8 may be submitted 20 times.
The Problem.
The data has to be extracted from the post table and, according to certain rules, inserted into a different table. (The �insert� is through the host application UI to avoid licensing issues using keystroke macros into an Oracle database table. Can�t use ODBC).
The rules dictate that the order in which the data is inserted into the different table (hence the date and time), is the same order it was received.
I realise that a reverse index using the fields would present the data in the correct order however due to data volumes there will be 10 sessions running against the table and attempting to pick up data from the posted table and applying it to the Oracle table.
So, Unique ID A1B23 might have processes 1,2,3,4,5 queued.
Session 1 picks up process 1 and starts to update Oracle
Session 2 picks up process 2 and tries to insert the data but the record is locked.
Question 1. How could I handle multiple sessions picking up the correct piece of data and not trying to insert that data until the previous insert is complete and Committed.
Question 2. Has anyone done any Robotics/ Screen Scraping with Alpha?
Comment