BPM Correlation from Dynamic Configuration not being filled

Question

Hey guys,
I'm having the following problem with BPM correlation.
In my correlation definition, I have 2 fields: one which is filled with information from the message payload, and another one which is filled with a context object (which was created with adapter metadata and filled with dynamic configuration, as refered here: /people/michal.krawczyk2/blog/2006/10/09/xi-dynamic-configuration-in-adapter-modules--one-step-further).
All instances of BPM are with error status. And when I go into the workflow log for these processes, if I check the correlation object, it is like this:
<?xml version="1.0" encoding="utf-8" ?>
<CorrelationKey Version="001">
<Field1 />
<Field2>123456789</Field2>
</CorrelationKey>
Field1 is the one read from context object, and is not being filled (thus I think the error comes from here). Field2 is from payload and is being normally filled.
Any ideas on this matter?
Maybe the problem is not from the correlation. If not, what else could be the case? The BPM crashes on the very first step (one more reason to think that the correlation is the issue).
Thanks in advance,
Henrique.

Answer 1

HI,
In general Correlation , concept, whatever we configured in Correlation editor , i mean in runtime which xml element should filled with which element of which interface ..as you said you have configured the local correlation to block, in block it is the first receive step, while receiving the first message which is relevent to first recieve step , i mean if it receives the one message which is related to first receive step inteface .. the respective element data will be filled in correlation id and it will assign on giud for processing , so while assign the runtime data to correlation element ( imean filling stage) check you said two elements in correlation does the first message contains these two elements ??
if so ok , no then check , and try to use the IM before calling the IP to fill the payload.
Regards
Chilla
Oh closed!!
Message was edited by:
        Chandra Sekhar Chilla
Message was edited by:
        Chandra Sekhar Chilla