When I create a new activity and would like to write a text inside it
e.g. login to the system. I cannot change the size of that text box.
Cannot chage to make its alignment right or left. Any suggestions?
It is not possible to resize text box of the task. Instead of
resizing the text box you are always able to resize the task, so that
the text does fit into the text box.
I don’t think this (“resize the text box”) applies anymore, because on my Camuynda Modeler v0.34.3, running on Ubuntu 14.04, I get something like this:
Basically, when I edit text inside the Task box (shown on left), I do get a handle on the bottom right corner, which I can drag, and which apparently changes the size of the text box (not of the task box, whose borders are still somewhat visible in the back - and btw, this is in complete opposition of the advice given in the post at the link given above).
But then, when I press Enter so changes are accepted, and the Task box is redrawn in full (shown on right), I can see that the change of the text box size did not influence at all the size of the task box; and furthermore, there are not any handles that I could use for dragging to resize the task box - nor can I see any other method to resize the Task box.
So, is it possible to resize the Task box in Camunda - and if so, how?
The behavior you would like to see will apply for text annotations and external labels (on start events and gateways) with any of the next Camunda Modeler releases.
We will stick to tasks not being resizable for the reasons @thorben pointed you to.
That one decision not to allow resizing od task boxes must have lost many thousands of users for camunda. Its such a basic need for modelling. Crazy decision
The choice to prevent people from re-sizing their activities is to save you from yourself
Generally speaking if the name of your activity has gotten so big that it doesn’t fit in the box it’s a bad name. A core practice of using BPMN is to ensure that the model is easy to read and understand quickly. if activity names are succinct and the symbols are uniform the model is demonstrably easier and faster to comprehend.
If you need additional information on your task - BPMN has annotations and cawemo.com lets you add comments and documents to tasks.
I hope this helps you understand that our decision is the right one.
I’m actually bumping into this topic - I think that’s not a good decision, especially for languages like German where you have pretty long words. For example, I have a step “Entscheidung (Vorstellungsgespräch) treffen” - the problem is that the word “Vorstellungsgespräch” already breaks with the first s, which makes it look amateurish. And in the context of an application workflow… well, you just can’t use better describing word. Btw. the same applies for the noun “Einstellungsentscheidung” (which could be written as “Einstellung entscheiden”, but is rather … unusual).
While I agree, that it is not very good to define utterly long names for a task, I think this is a rather rash decision. Especially when thinking about areas where you just have stupid names. In Axon Ivy for example, you can resize them at free will. Another great example is when your customer wants two steps in one and still want the name to be describing. Or if you’re using a prefix, example “[#{Name}] Mittelung an Lohnbuchhaltung”… while I understand the reason why you did this, I find this kind of far away from actual needs.
Hi I have a Macbook Air. I Downloaded Camunda Modeler but I can’t find the Plug-in Director where to copy the “resize task” Plug In. Any suggestion for this problem?
Great! Now It is working good! For Mac OS you have to “Show content” by the Camunda App and create two directory: “Resouces” and “Plugin” as the screen that I attach here.
Thanks!
Wow, that’s a bad decision. Really worried about a user creating a big box and getting semantically confused? Add a warning. You cannot predict all cases and needs. It’s like the type of people who try to deter people in QA sites from doing what they ask, without knowing their use case; arguing about network security, where the asker’s application won’t be used in a network environment…
Currently, for the user, this is not a “protection”, but a technical limitation that needs to be overcome with a workaround in order to use the application for their requirements.