FU

Monday, July 19th, 2021 9:21 PM

Classes not showing up in Flowable

Hello,
I’ve been trying to develop a workflow following the Collibra university course and am stuck where you are supposed to choose a class in the main config of a task. I’ve installed java/flowable per the instructions but when I search no collibra specific classes show up. Is there a component I’m missing? I switched over to using flowable since that seems newer than activiti and have tried multiple versions of Java.

Also, I tried the ‘Hello World’ walkthrough but the bpmn file won’t upload, is there an easy way to pull logs? I was able to install the CLI client but haven’t been able to find resources on pulling logs.

Any help is appreciated, thanks!!

1.2K Messages

3 years ago

Boot amps and coaching are great ways to get started with workflows.
In addition to flowable, you also need to load the collibra Java api jar into eclipse:
https://productresources.collibra.com/downloads/2021-07/

Bear in mind that many variables are magically instantiated in Collibra, so you will have to define you own “item”, “users”, etc variables.

Logs: everything happens in the collibra console but bear in mind most logs are useless (stack traces account for 95% of all workflow error management).

I already discussed much of this in previous posts.

Good luck on your journey! :sweat_smile:

262 Messages

Sorry to hijack this topic -

Where can I see the logs of why a .bpmn file that I export from eclipse cannot be uploaded into the Collibra UI?

I am developing a workflow in phases. The first phase bpmn file upload was successful & I could even run.

Now, I added some more code to it in Eclipse, and exported. Trying to upload the file but get “Unexpected Error Occured”, and the file is not uploaded at all.

157 Messages

I know you’ve since fixed your issue but for other citizens, reiterating & adding to what @arthur.burkhardt said, the console logs are where you can debug your workflow issues including BPMN errors that get thrown when uploading your workflow.

Yes and it’s why adding the jar file as depency in Eclipse is not really usefull.

I’m writting groovy script in a separate groovy file, then copy/paste the code into my script tasks into my flowable diagram. Even like this, there is no completion as these variable not exists into our local code, eclipse do not compile the groovy code, etc etc etc So I’m wondering why to add the jar file into dependencies?

1.2K Messages

Because it allows to get lots of informations on data structures, methods, etc as you are chaining transformations.
I personally created a python wrapper to manage workflow deployments and it’s a pretty good and efficient way to manage complex workflows, in my opinion.
I explained it in previous posts, but happy to share that in an upcoming use meetup.

Which ones? I can’t retrieve your previous posts about this.
I’m curious to see the explanation, and how it can enhance workflow dev and deployement.
It can be really helpfull.

3 years ago

Hi Arthur,

You really like Collibra to check the Datacitizen community during your holidays :wink:

Just read yours posts. Seems a really interesting tool !

If you have several Script Task into your workflow diagram, you have only 1 groovy file?
Then your python tool update the diagram XML code by replacing the code inside each node <scriptTask id='xxx' ...></scriptTask>

How do you identify block of code / script task into your grooy file, you put some XXX tag? Or maybe you have one groovy file per script task, with XXX into the filename?

Are you able to auto deploy a workflow in you Collibra instance from your workstation? We can use the importAPI for that?

Regards,

Alex

1.2K Messages

You guessed that right!
Every workflow has a folder (name = processId) containing a bpmn file (<processId>.bpmn) and one groovy file per script task (name = <processId>-<scriptTaskId>.groovy).
The script indeed opens each file and sets their content into the bpmn/xml file (+ perform some magic).

image

Finally, the script saves a copy of the compiled bpmn file and uploads it to collibra.
This automation saves me the few seconds to copy/paste, save, drag and drop, etc. which quickly amounts to a ton of time saved + a much more comfortable experience.

Look great.

The real benefit it will provide for me is that some time I just forgot to copy/paste the codre from my .groovy file to my .bpm (script task); and just upload the same diagram without modifcation into Collibra, and test… and do not understand why my update does nothing!

I will check to develop my own tools.

Thanks

Loading...