Post by ben on Dec 15, 2008 16:58:35 GMT -5
For sometime I have built LB applications that run some of the core functions of my small electronics company (product testing, order management, dispatch, confirmation emails, etc...)
We now want to provide a better customer experience by allowing the customer to see the status of their order online, automatic notification of delays and updates to the progress of their order, examine test reports online, etc...).
The way I think I would like to tackle this is to create an application that lives on a RUN BASIC server (pref. somebody elses managed server).
The skeleton flows I think I would like to build are:
PHASE 1 - ORDER ACKNOWLEDGEMENT
The customer will order a product from our website using PayPal or GoogleCheckout.
An email is generated by the payment processor with all the details of the order contained within, this can be duplicated and redirected.
RUN BASIC application will need to read this email (POP3?), strip out key features and then email the customer back (SMTP?) with an order acknowledgement (and a password).
From my past experience of LB I'm fairly sure the stripping, processing and sending the email can be done - the question is really how to 'grab' or 'receive' the email?
PHASE 2 - ORDER TRACKING
I think this should be all do-able with RB in it's current form, the main issue is the interfacing of barcode readers with RB - I'm assuming we can build an application which will cope with a barcode scanner working in keyboard emulation mode. Anyone done anything similar?
Can RB be made to run a program (on a remote RB server) at a specific time or on a schedule?
PHASE 3 - CUSTOMER INTERFACE
When the customer has placed an order and the RB system has sent them a password and a confirmation. The customer must be able to access a 'secure' web page that allows them to see a filtered 'snapshot' of a database (SQLIte), they should also be able to turn on/off some features like "please email me updates"
It would be great to get some feedback (on potential pointers/suggestions or flaws) before we spend too much time designing the workflows.
We now want to provide a better customer experience by allowing the customer to see the status of their order online, automatic notification of delays and updates to the progress of their order, examine test reports online, etc...).
The way I think I would like to tackle this is to create an application that lives on a RUN BASIC server (pref. somebody elses managed server).
The skeleton flows I think I would like to build are:
PHASE 1 - ORDER ACKNOWLEDGEMENT
The customer will order a product from our website using PayPal or GoogleCheckout.
An email is generated by the payment processor with all the details of the order contained within, this can be duplicated and redirected.
RUN BASIC application will need to read this email (POP3?), strip out key features and then email the customer back (SMTP?) with an order acknowledgement (and a password).
From my past experience of LB I'm fairly sure the stripping, processing and sending the email can be done - the question is really how to 'grab' or 'receive' the email?
PHASE 2 - ORDER TRACKING
I think this should be all do-able with RB in it's current form, the main issue is the interfacing of barcode readers with RB - I'm assuming we can build an application which will cope with a barcode scanner working in keyboard emulation mode. Anyone done anything similar?
Can RB be made to run a program (on a remote RB server) at a specific time or on a schedule?
PHASE 3 - CUSTOMER INTERFACE
When the customer has placed an order and the RB system has sent them a password and a confirmation. The customer must be able to access a 'secure' web page that allows them to see a filtered 'snapshot' of a database (SQLIte), they should also be able to turn on/off some features like "please email me updates"
It would be great to get some feedback (on potential pointers/suggestions or flaws) before we spend too much time designing the workflows.