Galaxia routing issue
Hi all -
First off, we're working on deploying Tikiwiki as our enterprise wiki solution. I know it's a bit rough around the edges for this sort of thing, so we're working through some issues, but I thought you might want to know. We're fortune 500, with an annual revenue of about $5 billion US, so Tiki is definitely getting some use in larger companies.
If I had to make a general comment about what's the best and worst features of the program, I'd say that the thing that needs the most work is the documentation. I can figure most things out myself, but it's more painful than it needs to be. I'll contribute after I get the hang of more things, and I hope a lot of other people will too. On the bright side, I'd say the most useful thing about the wiki is its wiki-ness... we're using it for documentation that's too valuable to keep on small slips of paper, but not formal enough to stick in one of our enterprise-class CMS systems. Any new feature or bug fix that enhances the ability to format, create, or organize wiki pages will be great for us. Upcoming features we really want to get working are Oracle support and PDF generation.
My current problem:
I've worked out most of how to get Galaxia running by reading the intro and manual PDFs, and by reading the compiled code samples once smarty gets through with my form posts. I am having trouble with the auto-routing feature however.
I have defined a simple demo process for our group that allows signoff (review) on wiki pages. The idea is to have a page author sign off, then a peer reviewer, then a group lead, after which the documentation will become "blessed". This is a demo, mind you, not a formal process. I have a lot of it working, except for the auto-routing at a switch. I don't see an error except when I have another problem on the page like an SQL error, then I see both the SQL error and a note about "setNextActivity" not being able to find a matching next activity name. I have checked the activity names and the names in the appropriate switch activity, peer_review_choice. No luck.
I think Galaxia has a ton of potential for us, if I can just get it working. My export of the example workflow is attached. The steps after the peer_review_choice aren't yet complete, but I would think it would still auto-route to the next step...
Our host system:
Dual P4 1.4 Ghz
Red Hat Enterprise ES 3.0
Apache 1.3.29
PHP 4.3.6
Mysql 3.2
Tiki 1.8.1
Database table schema:
drop table if exists digitalsignoff;
create table digitalsignoff (
docid integer(12) not null auto_increment,
docname varchar(200),
author varchar(50),
owner varchar(50),
owner_sig varchar(50),
owner_date datetime,
peer varchar(50),
peer_sig varchar(50),
peer_date datetime,
grouplead varchar(50),
grouplead_sig varchar(50),
grouplead_date datetime,
primary key(docid)
);
Workflow export: