Hi,
I’m tryinig Bonita 6.5.2 Community, and I’m trying to show a different logo in all pages possible (process, portal) instead the Bonita Logo.
I’ve just read in the Bonita documentation that, this is not allowed in Community version, but I’m able to change some minor features like the mainColor (I’ve changed it to blue) in the skin.config.less file or similar. I’ve got to change the logo too in the portal page, however, if I execute a process, I see the page with Bonita logo, and with the mainColor as red.
Is it possible to make this change? In that case, What is the path to the files I need to edit?
thanks in advance and regards.
P.S: I have some other problems, and I would thank some kind of help about them:
Help creating a spreadsheet connector
Help trying to integrate Google Maps
Help Trying to include theGoogle calendar Connector
Help trying to use the File Widget
Community? But what community? Studio or portal? You also say logo, which logo? There are several in use.
There seems to be an issue with studio, but portal should be fine. Did you see my other post on this?
Hi,
Community? But what community? Studio or portal?
I think I don’t understand clearly the difeernece between Studio and Portal… I thought Portal was referring only to the view which allow to manage the tasks, cases, process, etc.
I’m using this version exactly for design: BonitaBPMCommunity-6.5.2-x86_64.exe
You also say logo, which logo? There are several in use.
I have only seen two differents Bonita logos: ‘logo.png’ and ‘login-logo.png’. I want to change all the views whichever the form or process I launchn and regardless if I’m administrator or not. I want to replace the BonitaSoft Logo with my company logo, trying to get something similar to this example
I’ve got this, but I need to get the same when I execute a process, and that’s what I’m not getting. In these cases I see the default Bonita styles.
Besides:
There seems to be an issue with studio, but portal should be fine. Did you see my other post on this?
No, I don’t know the post you are referring to. And What issue are you talking about?
Thanks and regards.
OK,
Community is the free to use version of the software, of which there are TWO flavors. One is Studio for development and testing, the other Portal for Production use.
Subscription is the paid for version of which there is Teamwork, Performance and Enterprise editions, these offer more sophisticated services for enterprises that need them.
The Portal for Studio only refers to the web page views when clicking run from Studio, it is a Real “Test” portal for the Bonita software. it is effectively destroyed when you close the Studio and recreated again when you restart it. This behavior can be modified under Tools->Preferences->Database. Clean destroys all processes in the Runtime so you start with a clean database the next time.
Portal (for Production use) is a standalone Tomcat or JBoss server which can be used to run production 24x7x365 processes on a continual basis (though not recommended for Community, search for terms like infrastructure under answers (there is something I wrote a while back about this somewhere)).
You would develop under Studio and then build a BAR export which you then import into Portal, the production area, for everyone else to use…
Hence it is better to refer to the two products as Studio and Portal, we then know where we are as regards to assistance.
Hope that clarifies what the two Studio and Portal are. If not please ask.
OK if using Studio and wanting to change the logos, this is problematic as the basic CSS seems to be regenerated each and everytime you click run to test a process. This has been gone through in this post .
For Portal, the bit the End User will use changing colours, logos etc is described in this post here.
Hope they help, regards
Seán
Hi,
I’m not sure, I’ve understood too well… In summary, Can I say that the difference between Studio or Portal are the views? I mean a Community has always Studio and Portal, right? Studio is for designing process an Portal is for managing, aren’t they? Maybe, They are two sides of the same money…¿?
Well, after reading the posts you link, I have that exact behavior you refer here:
Right, I tested this and I can get Studio to work just fine, EXCEPT when hitting the run button for a process.
Let me explain…
I have created my bonita.css and it works in Portal. This is what I believe you have also done and this works fine.
I have copied the new bonita.css to the following directories in the STUDIO
workspace\tomcat\bonita\client\tenants\1\work\theme\portal and
workspace\tomcat\bonita\client\platform\tenant-template\work\theme\portal
Make sure you restart Studio,
goto Server → Open Portal This will (should) open the portal in the browser with your new colours
go back to Studio and click the RUN button for a process. This will open the portal with the Original red colour.
This is what I think you are seeing, and saying it’s not working. Which, to a point is correct, when hitting RUN it regenerates the default bonita.css and doesn’t use the new one we’ve asked it too. But when going to the portal first - it works.
I tried to figure it out yesterday to no avail, will have another look later,
regards
so I guess that’s not an error, only an unexpected behavior, right?
Anyway, I would like to give you my opinion about that. I think the mechanism to change styles is too complicated. It needs too work for little changes.
Thanks and regards.
You’ve got it almost right,
Community has always Studio and Portal, right?
No, is the real answer, though it could also be yes…
As I said…
Community is the free to use version of the software.
There are TWO flavors.
One is Studio for development and testing, which has an inbuilt testing Portal.
And the the other is Portal for Production use.
tghe easy way to show this is go to the downloads page…Design “Bonita BPM All in One/for Windows” is the STUDIO which has the inbuilt Test Portal.
And the Bundle Downloads - Production - are only the Portal. But all four downloads are Community. That’s what I mean by two flavors.
Studio is not portal, though it contains a portal. Hope that makes sense.
Right - back to the colors, yes you know see what I mean about Studio rebuilding itself all the time. Which means it is difficult to test colours in the Studio. You really have to do this in a “Test” version of the production environment to do it quick and easy. Change the CSS, start, stop, view, repeat until happy.
Changing Studio Portal colours is too much work for little success, but the Production version of the Portal - well you’ve done that and it looks good…
regards
