Scribbling the Contact Lenses Order/Collect Business Process (ready for BPEL?)

Lucas Jellema 2
0 0
Read Time:1 Minute, 54 Second

I use contact lenses. A pair will last me a month, then should be chucked away and replaced by a fresh pair. I buy them in six-month packs. From time to time I have eye difficulties and may wear my glasses for a few weeks. Sometimes I forget to replace the lenses after a month and use them for six weeks.....

The company where I ordered the first set of lenses will call me, some 5 months after collecting a pack of lenses, that my new lenses have arrived. I am supposed to come and collect them – and pay handsomely. I never asked for this automatic reordering, but they do it anyway and so far I have retrieved them – in the end.

Since they typically are ahead of me, I will ignore their first notification. After two weeks they call again – or send a note. After four such messages, them getting crankier every time it seems, I will finally get round to going to the store and getting those lenses.

5 months later, the phone starts ringing again. Note: that’s not 5 months after they received the lenses – it’s 5 months after I collected them.

I was wondering how their internal process is organized. How do they keep track of all their contact lens buyers and the schedules they are on. How do they know when to order and when to send me those notifications. And to what extent has that process been automated?

Being involved with BPEL quite a lot, my solution for this nail challenge is obvious: the great shiny BPEL hammer. So I sat down and scribbled the business process. Later on I will try to find time to turn it into a nice little BPEL demo.

But hey, when do I find time?

Note: after sending the notification, is waiting for two weeks until the next notification the main process and are event handlers on that event the best way of reacting to either the customer collecting the lenses or cancelling the order? Or should I use a Pick that either waits for two weeks and returns to the notifcation step or receives a cancellation and terminates or has the customer collect the lenses, wait for 4.5 months and return to ordering the lenses?

About Post Author

Lucas Jellema

Lucas Jellema, active in IT (and with Oracle) since 1994. Oracle ACE Director and Oracle Developer Champion. Solution architect and developer on diverse areas including SQL, JavaScript, Kubernetes & Docker, Machine Learning, Java, SOA and microservices, events in various shapes and forms and many other things. Author of the Oracle Press book Oracle SOA Suite 12c Handbook. Frequent presenter on user groups and community events and conferences such as JavaOne, Oracle Code, CodeOne, NLJUG JFall and Oracle OpenWorld.
Happy
Happy
0 %
Sad
Sad
0 %
Excited
Excited
0 %
Sleepy
Sleepy
0 %
Angry
Angry
0 %
Surprise
Surprise
0 %

Average Rating

5 Star
0%
4 Star
0%
3 Star
0%
2 Star
0%
1 Star
0%

2 thoughts on “Scribbling the Contact Lenses Order/Collect Business Process (ready for BPEL?)

  1. Just a question — since your previous post was about “…No need for expensive, fancy or complex SOA, JMS, ESB etc. infrastructure”. I know this is just an example, but why in the hell would I go to so much length as to setup/configure/maintain a BPEL architecture – just to automate/improve a single business process?

Comments are closed.

Next Post

Use BPEL Correlation Sets for repeated (synchronous) access to long running BPEL processes

Standing on the shoulders of Anthony Reynolds and Matt Wright, I finally managed to get the Correlation Sets feature in Oracle BPEL PM to do what I intended: I can instantiate BPEL process instances, with an identifier of my choosing and immediately receive their first response. Then at some later […]
%d bloggers like this: