Category: ~Workflow engine (Galaxia)

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

{syntax type=tiki}
{syntax type="tiki" editor="plain"}
This is the ((Tracking system for Tiki issues)).
If this is your first time, please read: ((How to Submit a new item on the Wishlist))

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

There are no universal products....

I do think so, that each is specialized, even so open as tikiwiki, any user of products try will to connect with others specialized products.

In fact the connection between systems takes a long, long time because, a product uses an implicit meta-vue of real, so there is a core of meta-model of datas which is progressively developped and connection are more and more simple, they become an element of culture of a community more and more large. This take decennies. This begin to exists for
*text calendar and tasks with ics files structure (but there is a confusion betteween taskd and event which generates a lot of bugs),

*text with ldap models for address management etc...
*text various contexts

About this my proposal is about calendar, task, and workflow is to have a bi-directionnal connection of the calendar and tasks.

Why bi-directionnal, because tikiwiki is an information generator that can be hold with ics shared files, and these must be easily connected with coherent others tasks and events that can be managed by specialized tools.

The main tikiwiki purpose is production of text and documents, may be it can go to GED (management of electronics documents), but technical documents have too specialized tools for technical documetns production etc...

But I don't se any (many but that can be solved) reason not to link a tiki event linked with a date held by Gannttproject (xml clear structure) and/or ics.

You will find the same with links with thunderbird calendard (oriented mail communication), SUGARCMR (relation and commercial action) yet connected with thunderbird and tikiwiki.
The main tools are ics and xml (complex structures for ganttProject)

This is future, this must be well thought because in these domain an error can generate year of delays.

I hope to have launched some ideas able to identify axis.

These are ways of work

It appears that CGI parameters used by Galaxia activity code are getting flushed. Things are working fine in 1.8.1 but do not work in 1.9.0

I tested a demo in http://workflow.tikiwiki.org/ , as anonymous user, for the "university exam":
http://workflow.tikiwiki.org/tiki-g-user_activities.php?filter_process=6

Clicked on the arrow icon ({img src=http://workflow.tikiwiki.org/lib/Galaxia/img/icons/next.gif}; btw, too small to be intuitive, I was not sure if this was the way to start. Some more explicit info on top of the screen would be welcome for new users of workflow)

Typed the name of the activity: Called "trial1" (without quotes), and name of the user: "xavi" (without quotes)
http://workflow.tikiwiki.org/tiki-g-run_activity.php?activityId=70&name=trial1

Then I only see those fields:
|| Process | University Admission Exam 1.0
Activity | Start
Comment|
Subject: | ^bla^
^bla bla some text^||

Then I click on save, and I get this error message:

^
Error
A start activity requires a name for the instance
^

---
From kerrnel22: I can recreate this. This will eventually get fixed, but in the meantime, it is merely a nuisance. What you entered still got added to the database, you just have to go back and pull up open instances.

Currently, when you create a process and initiate an instance, the user is prompted to name the instance, presumably as some way they can remember it in their own jumble of process instances (or tickets, as I like to call them).

I would like the admin to have the ability of eliminating that need on a per-process basis, and instead automatically naming the instance with the instance ID. This should give people the flexibility, if they want, to allow the user to create a memorable moniker, or allow it to traditionally take on a "ticket number" type of designation.

It really depends on the environment that the workflow is being used in. In a high-volume workplace, it may be best to use a ticketing style of identification. In a smaller-volume workplace, I can definitely see how custom names would be beneficial.

If I get time, I'll work on this.

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

Galaxia supports assigning a name to a process instance, and stores this value in the galaxia_instances table in the name field. This can be assigned through the API using the setName() method of the Instance class. (It is also assigned from the Javascript popup window which opens when you select a Start activity from the User Activities page)

However, there are many places (for example, User Instances, and Monitor Workitems) where this value is not displayed, only a bare (and meaningless, from a user's perspective) process ID number.

This is a clear usability obstacle.

This tracker item could not be found

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

When you create a new activity with numbers in the name, the numbers get removed in the generated files. For example, if I create an activity called 1, and then
I look in the "code" and "compiled" directory of processed, the file name with just be ".php".

Under ''Admin Processes'', upon attempting to a process, a number of MySQL errors are returned. The problem has to do with the syntax of the DELETE statement. As stated on the [http://dev.mysql.com/doc/refman/5.0/en/delete.html|Mysql 5.0 reference manual] under the DELETE Syntax,
^If you provide an alias for a table, you must use the alias when referring to the table:^
However, in the DELETE queries, the first reference to the table is the table name itself, which causes the failure.

I recently wiped my 1.9.7 install of Galaxia and replaced it from today's BRANCH-1.9 distribution. I am noticing that when I create a new process in the Admin Processes screen, it will auto-create the __start__ and __end__ activities in the ''galaxia_activities'' table. This is fine and dandy.

When I go to the Admin Process Activities screen to manipulate and add more activities, the start and end activities do not show up in the Process Activities list. It does report at the top of the screen that there are errors (such as start being interactive but no role assigned, and must use a particular method), but they appear invisible.

I also added a unique activity via this screen that does show up in the database as well, but it isn't showing up on the activity list from the Admin screen.

Interestingly though, I can go to the Monitor Activities screen, and there they are.

This is a significant roadblock to usability. I'll see if I can find what's causing it, but I'm having trouble deciphering a lot of it. Each script farms out to three or four others, which I'm not used to, so by the time I find the statement I'm looking for, I'm 5 scripts deep, and have to go back to get context. Difficult to troubleshoot.

Trying workflow (I could never make it work as a reviewer of workflow.tw.o and potential user... snifff), I hit a db query error, as anoynous:


To reproduce, come here (as anonymous):
http://workflow.tikiwiki.org/tiki-g-user_instances.php

Select to run any instance of cd loans; this one, for instance:
http://workflow.tikiwiki.org/tiki-g-run_activity.php?iid=860&activityId=73

You'll get:
{CODE(wrap=>1)}
An error occured in a database query!

Context:
File tiki-g-run_activity.php
Url tiki-g-run_activity.php?iid=860&activityId=73
Query:
SELECT * FROM cdcollection WHERE cdId =
Values:
Message:
Error Message You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
{CODE}