Problem z AlineaSol WorkFlowManager

[Radek2212]

Hej,

Jestem nowy wiec nie bijcie. Mam problem z AlineaSol WorkFlowManager:



Jak widać TriggerModule jest całkowicie nieaktywny i to mi wyglada na buga. Czy ktoś miał styczność z tym modułem ?

[davidnewcomb]

There are bugs in this area of code.

If you create the objects in the correct order then the module will be populated.
An "activity" needs a "process" to be part of. If you try to create a new "activity" then the module is blank because there is no context for it to run inside.
If you try to create a new "event" then it doesn't let you specify a trigger module. This is a bug, you should be able to edit this (IMO).

You must create a "Process" first,
then create an "Event" from the "Process" screen.
When you have created an "Event" you can create an "Activity".
Next "View activities" -> select the "Activity" you want and create tasks.

I still haven't managed to get the beta to do anything yet!

Hej,

Jestem nowy wiec nie bijcie. Mam problem z AlineaSol WorkFlowManager:



Jak widać TriggerModule jest całkowicie nieaktywny i to mi wyglada na buga. Czy ktoś miał styczność z tym modułem ?

[alineasol]

Hi all,

The WFM is long out of Beta (although there is still a Quick Guide of an earlier version that says Beta). Let us know if you still experience issues. A version was published yesterday with some bug-fixes.

Also, there is an example process defined that should work fine.

In any case, I will pass this to dev guys and see if this is an issue resolved some time ago.

@AlineaSol

There are bugs in this area of code.

If you create the objects in the correct order then the module will be populated.
An "activity" needs a "process" to be part of. If you try to create a new "activity" then the module is blank because there is no context for it to run inside.
If you try to create a new "event" then it doesn't let you specify a trigger module. This is a bug, you should be able to edit this (IMO).

You must create a "Process" first,
then create an "Event" from the "Process" screen.
When you have created an "Event" you can create an "Activity".
Next "View activities" -> select the "Activity" you want and create tasks.

I still haven't managed to get the beta to do anything yet!

[alineasol]

Actually... It just triggered my mind:

What you are describing here is a conscious decision. The possibility for events to be triggered by different modules could result in chaos. Specifically, references to the module data that triggered the activity. If this could be any module, things could get quite complicated. Therefore all the activities inherit the module referenced to by the process.
Still, there is an option for modules to call subroutines. This would be the way to execute some common code.

Hope this helps.

@AlineaSol

There are bugs in this area of code.

If you create the objects in the correct order then the module will be populated.
An "activity" needs a "process" to be part of. If you try to create a new "activity" then the module is blank because there is no context for it to run inside.
If you try to create a new "event" then it doesn't let you specify a trigger module. This is a bug, you should be able to edit this (IMO).

You must create a "Process" first,
then create an "Event" from the "Process" screen.
When you have created an "Event" you can create an "Activity".
Next "View activities" -> select the "Activity" you want and create tasks.

I still haven't managed to get the beta to do anything yet!