On Mon, Dec 13, 2010 at 02:51:06AM -0800, Waqas Qureshi wrote: > > I am new to Ruby and I have to develop a solution which is not focused > on just one workflow rather every user can create application based on > the workflow they design. The data model for the workflow and > business variables will be quite dynamic because we won’t know about > the workflow\business variables [data fields] in advance. We will keep > the data in either tables created at runtime, in xml or we might use > MongoDB. > > We will be saving and retrieving data bypassing the model layer as we > cannot create classes for every new type of workflow. > > I want to know how are we going to pass the transaction data to ruote > to make decisions e.g. if total job experience is less than 3 years > then move the record/transaction to “junior resources” state. And then > persist the data and state in mongoDB.
Hello Waqas, welcome to the ruote mailing list. I would suggest that you 1) become better with Ruby 2) then learn about ruote via its quickstarts and by building small prototypes 3) then a prototype of your solution 4) then build your solution When you have precise questions about ruote, feel free to ask them here. Best regards, -- John Mettraux - http://jmettraux.wordpress.com -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
