Hi John,
We seemed to found an issue with ruote::sequel during reply. we have a
process that looks like this:
Ruote.process_definition :on_error => "error_handler", :revision =>
"0.1", :name => "Ethics Violation" do
define "error_handler" do
set :_model => "Error"
participant "[email protected]", :task => "process ${wfid}
has gone ballistic"
end
sequence do
set :field => "_form_name", :value => "Ethical Violation Project"
participant :name => "Review potential Ethics Violation", :task =>
"Review potential Ethics Violation", :ref => "${f:_gatekeeper_email}"
participant :task => "Create Project", :ref => "create_project"
set :field => "_form_name", :value => "Next Action"
participant :name => "Begin documentation collection", :task =>
"Schedule first action", :ref => "${f:_gatekeeper_email}"
end
end
the process works fine with a fs_storage participant. However when we
tried it with ruote::sequel, it errors out when finishing (replying)
participant :task => "Create Project", :ref => "create_project".
This is the error we get in the development console:
#<NoMethodError: You have a nil object when you didn't expect it!
You might have expected an instance of ActiveRecord::Base.
The error occurred while evaluating nil.[]>
This is the line that when executed raises the error:
RuoteKit.engine.storage_participant.reply(workitem)
And this is the workitem that is passed into the line above:
#<Ruote::Workitem:0x000001091f12e0
@h={"fields"=>{"matter"=>{"custom_string_05"=>"Financial Disclosure",
"name"=>"ewf wef wef wefwefewf", "number"=>"WQErf wqef wqfwfwfw",
"custom_string_03"=>"", "description"=>" ewr werwe rwe ra3r w2",
"custom_string_01"=>"", "custom_string_02"=>"",
"matter_dictionary_id"=>"8", "matter_template_id"=>"42"},
"_attachment_fields"=>"attachment", "_gatekeeper_email"=>"jpgilman
[email protected]", "_process_definition_id"=>"2361",
"_form_name"=>"Ethical Violation Project", "controller"=>"workitems",
"action"=>"update", "_created_by"=>53, "_updated_by"=>"jpgilman
[email protected]",
"_after"=>"setTimeout(\"refreshStore('matter',true);refreshStore('workitem');
\",700);", "format"=>"extjs", "params"=>{"task"=>"Create Project",
"ref"=>"create_project"}, "dispatched_at"=>"2011-03-10 21:49:56.083291
UTC", "_matter_id"=>484}, "fei"=>{"engine_id"=>"engine",
"wfid"=>"20110310-puranura",
"subid"=>"721af1cdb7a0471e64131049c60a9c70", "expid"=>"0_1_2"},
"participant_name"=>"create_project", "type"=>"workitems", "_id"=>"wi!
0_1_2!721af1cdb7a0471e64131049c60a9c70!20110310-puranura",
"wfid"=>"20110310-puranura", "put_at"=>"2011-03-10 21:49:10.984091
UTC"}>
We have not been able to trap exactly where in the reply ruote is
throwing the error but we think it is somewhere inside the ruote-
sequel.
Please let us know if there is any additional information that we can
get you.
We will continue to see if we can narrow where the defect is.
Thanks,
Iuri
--
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
