Hi Regis,
For us, the most important items, at this moment, are first and second (maybe to
other workflow developers too, I don’t know). In our case we need to retrieve
and store data to a external database, and of course, we can code this second
access inside an activity (maybe at shared code). But what about making a new
workflow preference to store the connection parameters (host, db, etc) and
deliver a ready Adodb object to the developer? If you think its fine, we can try
do this.
Another thing is that we’ll have to delegate programming to other people and we
wouldn’t like to run the risk of a crash by inappropriate use of $db
egroupware-developers@lists.sourceforge.net escreveu:
Mauricio Luiz Viani a écrit :
> Hello Regis,
>
> We started coding a process with Workflow and we are in need of some
> new features:
>
Sure we need 
> - Access to a database outside eGroupware
You can do in activities all the things you can do in PHP, no limit,
that means activities code should only be accessible by administrators,
but you can connect where you want. Maybe you need it as a “designer
form to connect somewhere” but it’s another job.
> - Hide $Globals and $db from designers
This is the way I’d like to take for the next versions, effectively
> - More than one template per activity
This is possible already if you code your templates and code directly in
the dierectories where they are stored (via ssh for example) and not via
the web interface. but having something more usable in the web interface
is one of the thing to do.
> - A path to store images used in processes
Actually it is workflow/template/default/images/ we could think about
something better, effectively
> - Integration with an external Php editor
You can, activities’s code are stored in real php files, are you talking
about a web editor?
> - A pick user window, at roles mapping, to handle a large list of
> users (thousands). In our case we've Ldap with users grouped by OU
Yes, that’s right, We actually use a deprecated way to list user at this
place, this could be noted as a bug (could you please do the bug report 
> - An option to Smarty templates (already made by Rodrigo Lira, and
> waiting for your tests and commit)
>
Effectively, more of this coming after the stable release
> We'd like to discuss these things in more details and, if you like,
> work in one or more of them.
Everybody is really welcome to work/discuss/collaborate, of course.
Régis Leroy,
>
> Regards,
> ------------------------------------------------------- This SF.net
> email is sponsored by: Splunk Inc. Do you grep through log files for
> problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
> _______________________________________________ eGroupWare-developers
> mailing list eGroupWare-developers@lists.sourceforge.net <#>
> https://lists.sourceforge.net/lists/listinfo/egroupware-developers
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net <#>
https://lists.sourceforge.net/lists/listinfo/egroupware-developers
------------------------------------------------------- This SF.net email is
sponsored by: Splunk Inc. Do you grep through log files for problems? Stop!
Download the new AJAX search engine that makes searching your log files as easy
as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________ eGroupWare-developers mailing
list eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers