However, because the status history was only available in a text array, there was a problem. The Lotus Notes documents could spend an undetermined amount of time in any status more than one time. The variety and number of status stages precluded the use of multiple-type double variables. The status stages also held time values.
This addition of new status stages meant that I would also need to rewrite the LotusScript code. Because most documents used just five or six of the 16+ available statuses, that would waste too much time and the code would be extremely complicated.
Here is a sample of the text array:
The solution was to extract the data into a list using the status as the list tag:
This method did everything the client wanted -- quickly and accurately. Additionally, because I only used 22 lines of code, it's easy to understand and debug.
Do you have comments on this tip? Let us know.
This tip was submitted to the SearchDomino.com tip library by member Jack Swalwell. Please let others know how useful it is via the rating scale below. Do you have a useful Lotus Notes/Domino technical tip or code snippet to share? Submit it to our monthly tip contest and you could win a prize.
This was first published in March 2009