Welcome Guest! Log in
×

Notice

The forum is in read only mode.
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Topic-icon Question File wait and directBind condition

More
08 Apr 2019 12:32 #1 by leo75
File wait and directBind condition was created by leo75
Hi,

I want to link a FileWait to an executeDelivery with a DirectBind with condition on the file name:


The condition in the DirectBind link is :
%b(rhino){":{FILE_NAME}:".substring(24,27) == "DPR"}b(rhino)%

Test 1 : It works when the input file name is containing "DPR" in the good place : the executeDelivery is executed.
Test 2 : BUT it's also working when I set the condition with "TOTO" which is not included in the file name :
%b(rhino){":{FILE_NAME}:".substring(24,27) == "TOTO"}b(rhino)%


It's like my condition lets all the values pass... What am I doing wrong?
Attachments:
More
08 Apr 2019 15:19 #2 by Thomas BLETON
Replied by Thomas BLETON on topic File wait and directBind condition
Hello,

I don't really understand what is not correct.
In the "TOTO" case, it looks like there is no child session under the main process, which is normal because there was no file with "TOTO" in the name, right ?

Can you provide more details on what you were expecting ?

Note if that helps : substring(24,27) looks like a 4 characters string, not 3.
More
08 Apr 2019 15:36 #3 by leo75
Replied by leo75 on topic File wait and directBind condition
Hi Thomas,

When I execute the process with the test condition "TOTO", the process goes to the next step :

However, it shouldn't because it does not pass the condition.
%b(rhino){":{FILE_NAME}:".substring(24,27) == "DPR"}b(rhino)%
Input File name : 20190315184517_S1141542_DPR_Exemple Injection DPR.csv

Maybe it's normal or just a graphic issue?

Leo
Attachments:
More
08 Apr 2019 15:48 #4 by Thomas BLETON
Replied by Thomas BLETON on topic File wait and directBind condition
This is normal when using a DirectBind link.
The target action of the DirectBind will be executed between 0 and N times, depending on the source data and on the Execution Condition.
You can check the variable CORE_BIND_ITERATIONS on the target execution, to see how many times it was executed.
Whatever the number of executions, the process will continue after the target action. This is why the target action is considered as "done".

Maybe we can improve the Diagram display to show the number of iterations, or a different color when there were 0 iterations. I'll submit the idea to our r&d team.

I hope this helps ?
More
08 Apr 2019 15:52 #5 by leo75
Replied by leo75 on topic File wait and directBind condition
Ok no probs.
I just wanted to be sure the rhino code was working well and it is the case :-)

Thanks

Leo