On Sun, Aug 23, 2009 at 10:32 PM, lanfeust21<[email protected]> wrote:
>
> i had an error line 76
> if v == nil && not(attributes.has_key?('val') || attributes.has_key?
> ('value'))
> if i remove && and replace it by and everything goes well

Hello,

I'm sorry but line 76 of which file of which version ?


> i'll update the local ruote folder with the lastest code.
>
> in the meantime i reswitch to 2.0
> (and i use the same definition and adapted the user to be
> fsparticipant.)
>
> My problem are the following

I assume you're writing about 2.0 from now on.


> 1) The process did not stop at the user expression
>
>>look_for_matching_profile : ref='look_for_matching_profile'
>>guest_email : 
>>redirect_url='double_optin'&type='profile_already_activated'&ref='guest_email'
>>activated_matched_profile : ref='associate_registrar_with_his_matched_profile'
>>user : activity='double optin profile'&user_id=''&ref='user'
>>user : role='superuser or admin_of_group :association'&activity='validate 
>>matched profile'&ref='user'
>>user_email : type='account refused'&user_id=''&ref='user_email'
>
> i want the process to stop in the sequence at the first user
> participant , to wait he's input.
> That is not the case

I'm sorry, could you please tell me which participant is handling "user" ?

If you use DmParticipant, the workitem will quietly sit the the
database and wait for someone to "dmParticipantInstance.reply(it)"


> 2) it is rails specific,
> when i start a processus in a rails controller action, i can't use
> spleep 10 in it just to wait that the process is finished or that it
> wait users' input
>
> do i have to fork it ? i usually use a modified version of spawn to do
> that

As said on IRC, I'd recommend using a DmParticipant or ArParticipant
(if available) and let the users pick the workitems they're allowed to
see.

So when you launch a ruote process (I guess that's what you're talking
about but I'm not sure since you are talking about "forking" and
"spawning" which are about kernel processes), you simply return
immediately without waiting for the ruote process.

Note that engine#launch returns the "workflow instance id" of the
newly launched process. You could use that information and return a
redirection to something like "/workitems/?wfid=1234" or
"/workitems/1234" so that the user is redirected to a list of
workitems belonging to him and process 1234 (or an empty list).

I tend to do things like "process 1234 got launched, you can see its
workitems at http://here.example.com/workitems/1234"; in the "flash".

Now you're doing webflow... I guess you have 1 process "en route" per
user. What about something like "/webflow", which given the session's
user, lookup the corresponding workitem and displays the "screen"
specified in the workitem. If there is no workitem (yet), you could
reply with a 404 or a 200 "come check later or there is no webflow
going on for you" or a rotating wheel with a sleep before a reload...

Sorry not to be more helpful, but it's the first time someone asks me
about webflow with ruote.


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
-~----------~----~----~----~------~----~------~--~---

Reply via email to