Where is the image of Process into Bonita BPM 7.8 ?



I'm trying the new version of Bonita BPM 7.8 and when I create the bar file, the image of Process is not into de /resources folder.
In olders version (7.4.3) when you create a Project, the image is automatically added into de bar file, and when deployed/published in the Portal, the server insert a resource into de Data Base with the image. With this new version not.

Anyone has saw this problem ?
Is it a mistake ?

Best regards


1 answer


I try to reproduce the issue and I can see that it was already done in Bonita 7.7.

I think (it need to be confirmed) that the change was made on purpose. The aim of this change is to make the bar file lighter (for performance purpose) and to deploy only content required for process execution.

Sadly this change is no listed in any of the release notes ( 7.5, 7.6, 7.7).

Maybe you can add (as a comment on my answer) the use case that makes this file useful for you? I can then try to see how we can maybe integrate that (again) in a future version or provides alternative solutions.



Submitted by jordicato on Wed, 12/19/2018 - 08:33

Hi Antoine,

Thanks for your reply.

About your suggestion, It should be a decision of the developer that included or not the image when build the bar file. I explain why.
We have an application with Bonita embedded, and we have an option that showed the image of BPM with comments at user: when task is done, pending, error, etc. Without image it's impossible to do that.

Manually it's possible to include the image, but I understand that it is a waste of time.
Do not think the same, Antoine ?

Thanks a lot.
Best regards


Submitted by antoine.mottier on Fri, 01/11/2019 - 17:18

I think that would be nice if we should have avoid such change.

But note that the bar file and the structure of the Bonita Engine database are not part of what is defined as stable extension points. You can find the list of stable extensions point in the document.

I can confirm that the change happen between Bonita 7.6.3 and 7.7.0. I report internally the issue but I cannot confirm yet if it will be considered.