Free business process automation specialists software for linux

Business Process Visual ARCHITECT is a full-featured business process modeler that supports the latest OMG Business Process Modeling Notation (BPMN).
Business Process Visual ARCHITECT provides an easy-to-use diagramming environment for you to model your business process, and is a proven solution for bridging the gap between business analysts and IT professionals.
Main features:
- Frictionless business modeling environment
- On-the-fly syntax check and correction according to BPMN specification
- Advanced printing facility for outputting large business process diagram
- Share business process diagram among your company with Teamwork Server
- Incorporate user-defined images to the business process diagram to increase the readability.
Enhancements:
- Branch and tag capabilities were added to the VP Teamwork Server, including Subversion and CVS repository integration.
- This allows different modeling projects to be run in parallel while keeping the release quality project stable in the trunk.
- There were also a number of enhancements for various other features.

E/AS Automation Solutions is open source software system for help automate your solutions even for personal and/or corporate ones.
E/AS written on CLIP language (CA-Clipper dialect, compiler can be obtained from ITK.ru) and uses CODB (CLIP Object Database) as data storage.
Main features:
- client-server technology (both data and interface forms)
- component infrastructure with interaction between components by messages
- interface forms on XML
- MDI
E/AS contains in typical distribution:
- client software written on clip-ui library
- server software with wrapper for run as daemon
- maintenance tools: CODB console and component manager
- base (form, auth) and example (contact) components
Enhancements:
- completely rewrite code for implement E/AS architecture
- component infrastructure
- own server program instead COBRA
- maintenance tools: CODB console and component manager
- base and example components
- autoupdate views

The Stewie Radio Automation Project is a stand-in replacement for the "XMMS playlist on random" style of independent radio station.
Once properly configured, the user will enjoy the low maintenance of a "random playlist" station while still being able to use legal IDs, liners, multiple playlists, and music logs.
Main features:
- Low maintenance
- Multiple playlists
- Liners
- Legal IDs
- Logs every song and liner played
- Records errors and keeps truckin
Enhancements:
- Fixed a few bugs in install script
- Created error log/warning system
- Main script now updates the settings in stewie.conf in order to continue running. The only thing that *should* kill it, is not having any music available in the "master" playlist.
- Config file can be updated while script is running
- install-stewie gives "not found" audio players another chance
- Rewrote README file

Web Business Pro is a Web application designed for everyday business activities. The project includes support for customer lists, inventory, receipt printing, and accounting. Fully featured search functions and filters make it easy to find what you need quickly.

DRACONi Automation project is a Web-based digital entertainment/automation control package.
DRACONi Automation aims to be a home automation and digital entertainment/automation control package. Its designed to be modular, meaning new kinds of functionality can be added easily.
Currently, the X10 CM11A and Applied Digital Ocelot/Leopard are supported. It can also control XMMS and the Festival Speech Synthesis System.
Enhancements:
- User based system complete with per-user security permissions (you can restrict certain users to only user certain parts of the system)
- Multiple interfaces
- HTML - for most standard web browsers
- mobile HTML - for mobile devices with smaller screens such as PDAs and larger cell-phones that can read HTML, but have
- xHTML Basic/WAP 2.0 - for mobile devices such as cell phones with very small screens and low bandwidth

Business::Associates::XML is a Perl module for encapsulating XML, XSL, and XSLT operations for the Associates package.

SYNOPSIS

use Business::Associates::Data();
use Business::Associates::XML();

$data = Business::Associates::Data->$type ($what, $mode);
$xml = new Business::Associates::XML ($data) if defined $data;
$s = $xml->transform($ss_name, %args) if defined $xml;
print "nn$sn";

METHODS

new($data [, %options ])
This constructor takes an Business::Associates::Data object as the required argument. The optional options hash can be used to set additional values.
xml

This is the parsed xml string. If you want to pass special arguments to the XML::LibXML library then you can do it with this argument:

$data = Business::Associates::Data->$type ($what, $mode);
my $xml_string = $data->xml();
my $parser = XML::LibXML->new();
$parser->load_ext_dtd(0); # Global setting, unfortunately :-(
my $xml = new Business::Associates::XML(
xml => $parser->parse_string($xml_string));
...

It is possibly more efficient to access this element directly after the construction to set the options on the newly constructed XML::LibXML object.

transform($stylesheet_name [, %args ] )

This method transforms the XML using the named stylesheet, parsing any additional arguments to the stylesheet transform method. Typically, these additional arguments are used to set global XSLT parameters.

$data = Business::Associates::Data->$type ($what, $mode);
$xml = new Business::Associates::XML ($data);
$s = $xml->transform($ss_name, width => "3");

Note that these are named stylesheets. By default, they are found in the Base_Directory (see "Base_Directory") with the same name and the extension .xslt. To change this, either change the Base_Directory variable, or derive another class from this, overriding the get_stylesheet method.

Business::Associates::Stylesheet is a Perl information on the Associates XSLT stylesheets and how to modify the data processing.

THE PROCESSING MODEL

Before we get going on the details, let us first remind ourselves on what we might call the processing model of the Associates package.

The first step is to retrieve the raw XML data from Amazon.com (or, technically, from the local cache if we already have it). This is structured data that describes the (currently) fifteen best-selling titles at Amazon.com for the selection criteria we have chosen. Those criteria can be keyword searches or a look-up of a specific category of product, and are typically chosen by the HTML editor or by the code that generates the HTML. The perl code provided by this package retrieves the XML.

The second step is to transform this raw XML into a format that the device responsible for the visual display can handle. In our case, that device is ultimately the web browser, so we need to transform the XML data into HTML or xhtml data. However, the same process model could be used to render the data in another format, say for inclusion to a postscript document. This data transformation is done used XSLT, a standard and a very powerful tool for transforming XML documents. This is the subject of this document.

The third step is the visual formatting of the data. At this stage we have the data in a format that the visual display device can understand, and we need to tell it of the details of the formatting. In out model and for HTML (or xhtml) output, that is done using traditional Cascading Style Sheets (CSS). That is the topic of a separate document and concerns us only so far as it reminds us that we need to be able to identify each element type in the output such that the CSS designer can say, for example, "lets have all book titles in red text". In HTML, this identification is done by defining class attributes.

Business::PayPal::SDK is an interface to paypals SDKs.

SYNOPSIS

use Business::PayPal::SDK;
my $pp = new Business::PayPal::SDK(
{
paypal_apiid => "sdk-seller_api1.sdk.com",
paypal_apipw => "12345678",
paypal_cert => "paypal_java_sdk/samples/Cert/sdk-seller.p12",
paypal_certpw => "password",
paypal_env => "sandbox",
java_sdk_dir => "/path/to/paypals/java/sdk",
}
);

my $res = $pp->SetExpressCheckout(
{
OrderTotal => 10.00,
ReturnURL => http:://mydomain.com/myreturn,
CancelURL => http:://mydomain.com/mycancel,
}
);

print $res->{token};

Business::PayPal::SDK is a perl interface to the SDK provided by paypal (http://www.paypal.com/sdk). You can use this module to implement paypal pro and paypal express transactions in perl. On the back end this modules uses Inline::Java to interface directly with the paypals java sdk. Consequently you will need to get a J2SDK and Inline::Java installed. This was done for 2 reasons. 1) Speed of development, didnt have to deal with all the SOAP stuff. 2) Easier maintanance regarding future changes. That is to say, I only have to make sure I keep this compatiable with paypals SDK, not thier underlying protocol changes.

This document assumes you have an understanding of the java SDK and API provided by PayPal.

All methods take a single hashref as an argument. All methods return a hashref, or undef if there is an internal failure of some sort. Check $ret->{ack} to see if the call to PayPal was successful. If $ret->{ack} is not Success than you can check the $res->{ErrorCodes}, this will be an hashref with the key being the error code from paypal and the value is the getLongMessage from the error. Check $obj->error for description of failure.