First of all, I only solicit answer to technical question. 2nd I do not see the need to overreact to questions which may be naive or obvious for experts.
Back to the business. In our rails app, there is a need for approve process. For example, company A may need a quote to be approved by the manager and ceo before it is sent out. Company B may only needs approval by the manager. So we don't exactly know which person needs to approve the quote beforehand (i.e. we can not hard code the approve process and can not even prepare the database for it. We need to customize the approve process for every software client). Also we would like to keep the info about who approves at when or reject because of what for tracking and future reference. ruote provides storage and seems capable to do what we are looking for. Our rails app consists of multiple rails engines and this is the architecture ruote is going to be integrated into. Thanks for the comment. On Friday, June 21, 2013 10:46:45 PM UTC-5, marsbomber wrote: > > Hi emclab, > > Fill in some background info, I did quite some work with Ruote last year > and believe or not, John could be the single most proactive gem > author/maintainer I came across ... > > So ... back to your very original questions. I think you may get a much > better recommendation from the experts here if you explain what you want to > achieve from your application. The answer to if you should implement Ruote > at the main Rails app level or at each Rails engine level will probably be > worked out naturally... > > My 2 cents from not understanding what you want to achieve is this > > As John already explained, since Ruote maintains its own states (jobs to > run, workitem states, etc), why don't you just treat Ruote as a single work > horse, map it to your main Rails app? I'd question if you indeed need to > implement all those Rails engines ... If you want to use each engine to > process parts of a workflow, you can achieve it via messaging (even if you > do go down the Rails engine path, messaging will still give you a much > loose coupling to other parts of your overall system, compare > to implementing Ruote at Rails Engine level ...) > > I guess all I want to say is jump out the implementation details, look at > your overall architecture of the app a little more, maybe you'll find a > better solution. And of course, let's give OSS authors credits for even > caring about their mailing lists. To me, we shouldn't take that as granted. > > On Thursday, 20 June 2013 03:13:38 UTC+10, emc_lab wrote: >> >> We plan to integrate ruote into our rails 3.2.12 engines. Our 3.2.12 >> rails app consists of multiple rails engines. There are a few questions we >> have now: >> >> 1. Where to implement ruote? Can we add the ruote to each individual >> engine which needs ruote? Or add the ruote to rails app and provide its >> features to whichever engine who needs it. > > 2. If implementing ruote in rails app level, can all the ruote engines >> share a single table for workitems? Or we have to create a unique table for >> each and every ruote engine. >> 3. Is it possible to implement a workflow spanning over more than one >> engines? I guess this is related to how and where ruote is added to the >> rails app (with rails engines). >> >> >> There are not much online about ruote and rails engine. Any comments are >> appreciated! >> >> -- -- 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 --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
