Loading...
 
Galaxia Workflow Engine

Galaxia Workflow Engine


Re: Let's talk about Galaxia

Spain

Why Galaxia should be ripped off TikiWiki as a mod? I know you can install it later, but IMHO is step backwards.

Galaxia is the most powerful tool in TikiWiki!!!

We could live without Maps. But if someone couldn't, he still could code Maps using Galaxia (Yes, you can)

I'm not saying "don't do mods", I'm just saying: "Galaxia is not a mod"

And I guess I deserve more than an award for using it biggrin

Just a brief list of current processes we deployed/coded/studied using Galaxia:

- Managing employees as users in Tiki (adding a file gallery for each one, a CV, etc.)
- Filling a weekly worksheet with the time expended in each project.
- Requesting holidays and tracking of holidays left per year.
- Managing a whole project: creating the project, categorizing it, and gathering all the related info in the Intranet, add its documentation templates...

and I can think so many more...

I will make sure the mod system allows me to carry all this work to the next version before moving to 1.9 sad

Marc, in tiki-devel list you talked about this, but you didn't say something about Galaxia precisely. What do you think?

I'd really like to hear about your experience using Galaxia and your stategy for developing workflow content.

I have got the lame CD library example workflow running. It obviously demonstrates the enormous potential of Galaxia/Tiki, which you evidently have succeeded in harnessing for the workflows you mentioned.

What I am missing as a next step is how to move beyond "activity complete" (instead of "thank you for your order" or whatever) and the list of potential activities might be completed.

I need pages that show the requests I can make (e.g. time off), pages of requests to process for various roles (e.g requests for time off a manager need to approve/reject), reports pages (e.g. time out chart).

Just a high level view of how you did time off tracking or the weekly worksheet would be very helpful to me and others.

Spain

I'm actually not a Galaxia-god redface, since I still have some problems to make my processes have any workflow at all, that's why I code every activity as 'standalone'. Well, is a different way of doing the same thing. I also don't want my users to mess with 'processes', 'activities' and 'instances', so I use a menu entry for every activity they can run, and using no instances makes that easier (don't need the instance id at the menu)

About the processes I have done, I would love to share them with the community, and see what the community has to offer razz

As per the 'high level view', right now my users can see their entry/exit times that get updated from the door-entry system. Admins can view anyone's entries. This is just a database view of the table, with a filter by date. I would like to code some statistics when I have some time.
They can also (since today smile) request one or several holidays. That request generates an internal message for the employee's boss with the link to the 'Review holidays' activity, which he can accept or reject. These two options generate a message to the user with the result, and maybe some comment. At any moment the user can see the approved holidays. They also have a number of holidays left that gets updated with each request accepted.

About the weekly activity timesheet, I opted for not using the data coming from the door-system, and I will let the users select a project and the number of hours working on that project. Since we can have people working on two or more projects the same day, my greatest concern is having to write to the database between selections. I'm not a php-god either! frown

They can run more activities, p.e. for viewing their personal data, and I have some more administrative activities to maintain the data in the tables I created.

I would like to discuss this more with every one that wants to.

Cheers,

Miguel