|
One of the great new features of Metastorm BPM is looping.
There is also the ability to process lists, although the current
implementation only manages Business Objects. The reasons
seems to be that the code must be bound at design time.
Why do we want to do this? There is a lack of list processing
functions that we used to have in previous versions. Some of our
systems have code that relies upon those list processing
functions. Without them the functionality will have to be re-
engineered. What can we do about it?
We have added our list processing functions to our library, but is
there a simpler way that is more generally useful? Yes there is.
Metastorm will happily process lists, and has an internal type
called ‘List’. All we really need is a way to convert tab and other
separated strings into Metastorm lists. These are converted to
Text and Memo fields when assigned, so we can store them as
this and recreate our List object when we need to use it later.
What we are actually missing here is a 'List' type variable to
store the Lists we create. That would make this redundant. Until
we do, we have to implement our own.
|
|
|
|
|
|
Creating our List
