http://www.perlmonks.org?node_id=887723

Dear monks,

I really don't know where to write this or to start a new thread about it, but considering the title says is a place to share perl code, well, this is about shearing a lot of code.

I started a new workflow OpenSource project eflowmx, located in sourceferge.net.

http://sourceforge.net/projects/eflowmx

Is fully developed with perl. I would like to find developers that like perl as I do, and that have been or like to develop workflows. If anyone finds it interesting and wants to give some feed back. Or if any would like to join, I'm open.

Sometimes I feel like everyone now only develops with php and MySQL, but I believe that perl still has lots to offer, so hope someone gets interested.

If I shouldn't wrote this here, then I'm deeply sorry, just tell me where to move it.

Thanks, Hans Peyrot

Replies are listed 'Best First'.
Re: New opensource project with perl
by Anonymous Monk on Feb 12, 2011 at 06:33 UTC
    Great! But what does it do?
      Using fancy names, would be a BPM (Business Process Management) application, or more commonly known as WorkFlow application.
      With it you can visually create an "electronic document" (form) and "draw" all steps of a process. The electronic form will flow through all the steps, and the system will manage: time, people involved, apply rules to deliver the document to the next responsible person in line, connect each step with any application in the company to apply rules or move data as steps are validated, notify, escalate, etc.

      With it you can automate almost any kind of traditional administration processes : vacations, payments, purchasing, credit line authorization, expenses reports, processes to deliver new products to the market, warranties claims, complains, or any that is totally unique to a company.

      Any sequence of events where people has to interact with authorizations and participate at a defined point in time can be put into the application.

      The must important feature, is that you can change the process as many times as needed as the company rules change, needs grow or shrink. Buy moving parameters.

      End users will use the workflow to create new tasks, and those will pass from person to person, through all the steps necessary, controlled by the application.

      Perhaps the best way to see it is watching a video in my site and reading some of the work already done with some companies.

      http://eflow.mx/en/video.htm
      http://eflow.mx/en/clients.htm