Binary file added in a branch after flow edit
Hello,
I was fixing few bugs issued in an application that was recently upgraded from Pega 7.1.9 to Pega 8.5.3 when I noticed a weird occurence. It happened when modifying flow rules.
At start, the concerned flows had at the Case type property a blank value. That event was generating the following error: Case type can not be blank. I adressed the error setting the field with "Other". But, after saving and checking-in the rule, I noticed that a binary file that seems to correspond to the flow I just modified was appearing into the branch.
I attached the header details of an example of a flow I modified and the binary file that seems to corresponds to that flow in the branch.
Can someone please explain me this phenomenon?
Can I just deleted them?
Best regards,
Pegasystems Inc.
ES
@RusselK1this is an OOTB behaviour, every time a flow is changed the binary file associated to it is updated as well, and as you are modifying the flow in a branch, the binary file is associated to the branch as well.
You should keep as it is.
Hope this helps,
Iñigo.