Loading...
 
Galaxia Workflow Engine

Galaxia Workflow Engine


i'm confused. some newbie questions

Hi, i'm a newbie with this workflow engine.
I'm using tikiwiku and i read all galaxia documentation. I was trying the example of "CD loans" on Galaxia manual.
I have correctly create roles for the process (admin) and correctly mapped admin role to admin user on tikiwiki.

but for some strange reasons, i can't see nothing under User process. The user admin as i said i correct mapped to the role "admin"

help please redface

Brazil

Is the process valid (no errors) and active (enabled)?

Georger

> Is the process valid (no errors) and active (enabled)?
>
> Georger

thanks. i'm stupid, i didn't see the process was correct but not enable :P

few questions:

I know that an instance is an example of a process that "flow", pass from one activity to another. If you have an activity (start) named A and one named B, in sequence, an instance created by the start activity A go to the activity B. right?

Image that an instance named "first" is passed to activity B. In the activity B, you abort instance "first".
Using API ($GUI->gui_list_user_instances), i see (in the activity B-) that instance "first" has INSTANCE STATUS = aborted (of course) and ACTIVITY STATUS = running.

The same appens with excpetion. Image that you have an instance named "second" passed to activity B. In the activity B, you exection the instance.
In the activity B, I see that instance "second" has INSTANCE STATUS = exception and ACTIVITY STATUS = running.

with $GUI->gui_list_user_instances you has for each instance some proprieties like instance status and activity status. what means activity status? i'm confused. why the activity status is still running for an instance aborted?

thank you in advance. i'm a student and i'm doing a thesis on workflow and galaxia using API for monitor and execute workflow (not for design it)

Brazil

> thanks. i'm stupid, i didn't see the process was correct but not enable :P

I don't think you're stupid. I myself fell for this several times, as well as one of my team members.

> few questions:
>
> I know that an instance is an example of a process that "flow", pass from one activity to another. If you have an activity (start) named A and one named B, in sequence, an instance created by the start activity A go to the activity B. right?

Wrong. If A is a start activity, it only means it does not have a predecessor. You have to run it and complete it. It has code for logic, a template for layout, and has to call the $instance->complete() method in order for the instance to advance to activity B - and it will only advance to activity B if A is auto-routed (which is recommended).

> Image that an instance named "first" is passed to activity B. In the activity B, you abort instance "first".
> Using API ($GUI->gui_list_user_instances), i see (in the activity B-) that instance "first" has INSTANCE STATUS = aborted (of course) and ACTIVITY STATUS = running.

Right.

>
> The same appens with excpetion. Image that you have an instance named "second" passed to activity B. In the activity B, you exection the instance.
> In the activity B, I see that instance "second" has INSTANCE STATUS = exception and ACTIVITY STATUS = running.
>
> with $GUI->gui_list_user_instances you has for each instance some proprieties like instance status and activity status. what means activity status? i'm confused. why the activity status is still running for an instance aborted?

You're right. It really could be clearer. The difference is that an aborted instance can't be resumed. An "exceptioned" one can.
Instance status is important because you can have running, aborted, "exceptioned" and completed instances. How else would you figure out how your instances are doing?
Activity status is also important because you can have running and completed activities. This way you can track how far into the process an instance is.

> thank you in advance. i'm a student and i'm doing a thesis on workflow and galaxia using API for monitor and execute workflow (not for design it)

Great! What tool are you using for design? JaWE?
I have made some fixes to Galaxia. If you're interested in them, just write me on georger_br ar yahoo dot com dot br.
You may want to take a look at my University Admission Exam sample process. Its XML and MySQL script are available at http://sourceforge.net/tracker/index.php?func=detail&aid=1210071&group_id=64258&atid=506846

Regards,

Georger

thank you a lot. I'm using tiki for workflow design (that is, to create ONLY database entries). After, i have to integrate the workflow in http://www.phprojekt.com/ as a module. I have to list and run activities for users (also monitoring workitems), and re-design it. I have also to using soap and webservice to support mobile/home working, but no idea for now.
Now i'm using galaxia API taken from tiki in order to list activities for an user logged into phpproject.

> You're right. It really could be clearer. The difference is that an aborted instance can't be resumed. An "exceptioned" one can.
> Instance status is important because you can have running, aborted, "exceptioned" and completed instances. How else would you figure out how your instances are doing?
> Activity status is also important because you can have running and completed activities. This way you can track how far into the process an instance is.

i'have made a schema. it is right? i'll try to explain, despite of my bad english:
for one activity, using gui->list_user_instances you has:

-ACTIVITY STATUS= running/INSTANCE STATUS= active -> the user have to run the instance in THIS activity.
-ACTIVITY STATUS= running/INSTANCE STATUS= aborted/exception -> the instance was aborted/exception in THIS activity.

-ACTIVITY STATUS= completed/INSTANCE STATUS= active -> the instance has already been executed for this activity. now this instance is somewhere in the workflow and it is active, that is another activity can run it.
-ACTIVITY STATUS= completed/INSTANCE STATUS= aborted/exception -> the instance has been already executed for this activity. But somewhere in the workflow, it has been aborted/exception.
-ACTIVITY STATUS= completed/INSTANCE STATUS= completed -> the instance is completed, that is has reach the end of the workflow.

hope this is right. when you use tiki, under "user activities" you will see each activity with the number of instances that it has. clicking on the activities, you can see the instances in detail. tiki shows instances that have ACTIVITY STATUS = running ad INSTANCES STATUS = active/aborted/exception.
however, using gui->list_user_instances, you are able to see all the instances, also that with activity status=completed.

> Great! What tool are you using for design? JaWE?
> I have made some fixes to Galaxia. If you're interested in them, just write me on georger_br ar yahoo dot com dot br.
> You may want to take a look at my University Admission Exam sample process. Its XML and MySQL script are available at http://sourceforge.net/tracker/index.php?func=detail&aid=1210071&group_id=64258&atid=506846

i have seen. seems that there are some problems with join activities (3) as you say. fortunately, for now i have no join activities :-)


please be patient with a newbie student redface

Brazil

> thank you a lot. I'm using tiki for workflow design (that is, to create ONLY database entries). After, i have to integrate the workflow in http://www.phprojekt.com/ as a module. I have to list and run activities for users (also monitoring workitems), and re-design it. I have also to using soap and webservice to support mobile/home working, but no idea for now.
> Now i'm using galaxia API taken from tiki in order to list activities for an user logged into phpproject.

Hmm, that will be quite a bit of work. IIRC, pemen has done this with XOOPS. The Xaraya team integrated Galaxia to their CMS as well.
Before you understand the inner workings of Galaxia, you must gain a deep functional understanding of it. I suggest thoroughly reading the documentation available at http://sourceforge.net/project/showfiles.php?group_id=64258&package_id=88508&release_id=171108 and designing a process or two yourself.

> i'have made a schema. it is right? i'll try to explain, despite of my bad english:
> for one activity, using gui->list_user_instances you has:
>
> -ACTIVITY STATUS= running/INSTANCE STATUS= active -> the user have to run the instance in THIS activity.
> -ACTIVITY STATUS= running/INSTANCE STATUS= aborted/exception -> the instance was aborted/exception in THIS activity.
>
> -ACTIVITY STATUS= completed/INSTANCE STATUS= active -> the instance has already been executed for this activity. now this instance is somewhere in the workflow and it is active, that is another activity can run it.
> -ACTIVITY STATUS= completed/INSTANCE STATUS= aborted/exception -> the instance has been already executed for this activity. But somewhere in the workflow, it has been aborted/exception.
> -ACTIVITY STATUS= completed/INSTANCE STATUS= completed -> the instance is completed, that is has reach the end of the workflow.

Right.

> hope this is right. when you use tiki, under "user activities" you will see each activity with the number of instances that it has. clicking on the activities, you can see the instances in detail. tiki shows instances that have ACTIVITY STATUS = running ad INSTANCES STATUS = active/aborted/exception.

Hmm, no. When you click "User activities", all activities for which you have permission are listed.
When you click "User Processes", TW shows the processes for which you have permission and the total number of instances it has. If you click the process name, it takes you to the "User activities" screen for the given process.
To see the instances in detail, log in as admin and click "Monitor Instances". The "User instances" screen only lists the instances whose activities the user has permission for, and doesn't show details.

> however, using gui->list_user_instances, you are able to see all the instances, also that with activity status=completed.

Right.

> i have seen. seems that there are some problems with join activities (3) as you say. fortunately, for now i have no join activities :-)

You're bound to need them someday...

>
> please be patient with a newbie student redface

You're welcome. Regards,

Georger


Upcoming Events

1)  18 Apr 2024 14:00 GMT-0000
Tiki Roundtable Meeting
2)  16 May 2024 14:00 GMT-0000
Tiki Roundtable Meeting
3)  20 Jun 2024 14:00 GMT-0000
Tiki Roundtable Meeting
4)  18 Jul 2024 14:00 GMT-0000
Tiki Roundtable Meeting
5)  15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting
6)  19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting
7) 
Tiki birthday
8)  17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting
9)  21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting
10)  19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting