PloneFormGen integration with GetPaid

[Christopher Johnson]

Hi folks,

Ever since the first release of getpaid, we realized that a flexible donation/payment form making option was desired for GetPaid. We know that everyone wants their donation form slightly different, so an option like PloneFormGen ( ), which also has wide adoption in the community, seemed like an obvious choice.

One/Northwest and others have worked on an adapter for mapping PFG data into salesfoce.com, which seems like a great model for this use case. This leverages the flexible form making and integrates it into another system for storing/manipulating what was collected in the form - brilliant! For more on this, see http://theploneblog.org/blog/archive/2007/08/09/saving-ploneformgen-data-directly-to-salesforce.com .

The concept would be similar for Getpaid integration with PFG: map fields from a form into GetPaid cart and/or checkout process. Some potential use cases:
  - Make a single page checkout (so you enter all on one page and that generates the order directly)
  - Ordering multiple items from a single page

See an example of both of these at: http://tinyurl.com/53yr8o

We have been gathering information on this use case and the work implied on the wiki: http://code.google.com/p/getpaid/wiki/PloneFormGenAdapter  (same page referenced by the checkout refactoring discussion...). We would appreciate your ideas, feedback, questions, and offers to contribute :)

Cheers,
Chris

--
Cofounder and CEO
ifPeople - Innovation for People
www.ifpeople.net
t: 678-608-3408
130 Boulevard NE, #6
Atlanta, GA 30312

[Matt Halstead]

On May 30, 11:33 am, "Christopher Johnson" <cjj.ifpeo...@gmail.com>
wrote:

> Hi folks,
>
> Ever since the first release of getpaid, we realized that a flexible
> donation/payment form making option was desired for GetPaid. We know that
> everyone wants their donation form slightly different, so an option like
> PloneFormGen ( ), which also has wide adoption in the community, seemed like
> an obvious choice.
>
> One/Northwest and others have worked on an adapter for mapping PFG data into
> salesfoce.com, which seems like a great model for this use case. This
> leverages the flexible form making and integrates it into another system for
> storing/manipulating what was collected in the form - brilliant! For more on

> this, seehttp://theploneblog.org/blog/archive/2007/08/09/saving-ploneformgen-d....

>
> The concept would be similar for Getpaid integration with PFG: map fields
> from a form into GetPaid cart and/or checkout process. Some potential use
> cases:
>   - Make a single page checkout (so you enter all on one page and that
> generates the order directly)
>   - Ordering multiple items from a single page

I'd add to this another use-case, since PFG forms suit it well, which
is to persist user specific data on a line item. At present I have
been using zope 3 form schemas and the persistent options facility to
gather and persist user specific form data onto line items as
annotations (which persistent options uses). The natural extension of
this is to allow more flexibility at the admin level (not developer
level) to do this by way of something like PFG.

>
> See an example of both of these at: *http://tinyurl.com/53yr8o*

[Christopher Johnson]

Hey Matt,

I am having trouble translating that into a use case...still a bit geek-speak to me. Can you give an example of how this would be used?

Thanks!

-chris

>
> See an example of both of these at: *http://tinyurl.com/53yr8o*
>
> We have been gathering information on this use case and the work implied on
> the wiki:http://code.google.com/p/getpaid/wiki/PloneFormGenAdapter (same
> page referenced by the checkout refactoring discussion...). We would
> appreciate your ideas, feedback, questions, and offers to contribute :)
>
> Cheers,
> Chris
>
> --
> Cofounder and CEO

> ifPeople - Innovation for Peoplewww.ifpeople.net

> t: 678-608-3408
> 130 Boulevard NE, #6
> Atlanta, GA 30312

[Matt Halstead]

On Jun 3, 4:25 am, "Christopher Johnson" <cjj.ifpeo...@gmail.com>
wrote:
> On Sun, Jun 1, 2008 at 5:29 AM, Matt Halstead <matt.halst...@gmail.com>

use-case: use PFG to generate forms that when made buyable/shippable/
etc will have their user filled in data persisted on line items that
end up in the final order.

e.g. joining forms, selecting attributes of the item such as color,
size, duration etc.