HELP!!!! AOW_Workflow - Action steps disappear from workflow setup

dgreene · 28 March 2014 14:25

Once a workflow has been defined, if I go back to edit it, the action steps i’ve defined are not there (intermittently). When this happens I must recreate them because they will never re-appear. It used to only happen on “Create Record - New Task” steps, but now it appears to be happening to any action steps i’ve defined.

Any idea why this is happening? Records are in the AOW_Actions table - but the specific details of the actions/fields are apparently stored elsewhere.

See attached screenshot. The “Create Record” action had been defined with at least 12 or more fields defined - now no action steps are appearing. Also, when this happens and the workflow executes - the record created by the workflow is blank.

Will · 28 March 2014 14:35

Hi dgreene,

Are there any errors in your sugarcrm.log? Does this happen with standard module workflows? Have you tried disabling AJAX for the WorkFlow module and performing a Quick Repair & Rebuild? Also what are your permissions?

Thanks,

Will.

dgreene · 28 March 2014 14:47

Happens with all modules
Disabled ajax, did the quick repair - still missing
Permissions are windows based - “Everyone” user with full permission to the Cache, Upload, Custom, Modules, data folders
Log is full of these errors today - these weren’t here yesterday. Doesn’t appear to be related. No explicit errors for AOW_Workflow.

03/28/14 10:37:28 [1012][36481b03-923e-310e-2d0b-520912a5bdf7][FATAL] Query Failed: SELECT bm_budget_package.* ,bm_budget_package_cstm.accounting_comments_c,bm_budget_package_cstm.accounting_rejection_c,bm_budget_package_cstm.approved_assessment_c,bm_budget_package_cstm.assessment_date_c,bm_budget_package_cstm.assessment_resolution_c,bm_budget_package_cstm.billing_frequency_c,bm_budget_package_cstm.billing_frequency_details_c,bm_budget_package_cstm.billing_letter_c,bm_budget_package_cstm.billing_posted_c,bm_budget_package_cstm.billing_post_date_c,bm_budget_package_cstm.billing_type_c,bm_budget_package_cstm.budget_corrections_pm_c,bm_budget_package_cstm.budget_rat_required_c,bm_budget_package_cstm.budget_request_status_c,bm_budget_package_cstm.ca_updated_c,bm_budget_package_cstm.ca_update_date_c,bm_budget_package_cstm.cinc_billing_batch_c,bm_budget_package_cstm.collections_resolution_c,bm_budget_package_cstm.corrections_made_c,bm_budget_package_cstm.current_billing_frequency_c,bm_budget_package_cstm.current_billing_type_c,bm_budget_package_cstm.current_extra_fee_c,bm_budget_package_cstm.current_first_billing_month_c,bm_budget_package_cstm.current_late_date_c,bm_budget_package_cstm.current_late_fee_c,bm_budget_package_cstm.current_late_interest_c,bm_budget_package_cstm.current_year_apr_c,bm_budget_package_cstm.date_final_budget_received_c,bm_budget_package_cstm.date_resolution_submitted_c,bm_budget_package_cstm.date_sent_bod_c,bm_budget_package_cstm.draft_budget_c,bm_budget_package_cstm.draft_budget_date_c,bm_budget_package_cstm.final_budget_c,bm_budget_package_cstm.general_notes_c,bm_budget_package_cstm.late_date_c,bm_budget_package_cstm.manager_budget_approval_c,bm_budget_package_cstm.manager_resolution_approval_c,bm_budget_package_cstm.mar_approval_date_c,bm_budget_package_cstm.mb_approval_date_c,bm_budget_package_cstm.pm_billing_approval_c,bm_budget_package_cstm.pm_billng_approved_date_c,bm_budget_package_cstm.scheduler_updated_c,bm_budget_package_cstm.scheduler_updated_date_c,bm_budget_package_cstm.sent_to_bod_c,bm_budget_package_cstm.statement_letter_c,bm_budget_package_cstm.currency_id , LTRIM(RTRIM(ISNULL(jt0.first_name,’’)+N’ ‘+ISNULL(jt0.last_name,’’))) modified_by_name , jt0.created_by modified_by_name_owner , N’Users’ modified_by_name_mod , LTRIM(RTRIM(ISNULL(jt1.first_name,’’)+N’ ‘+ISNULL(jt1.last_name,’’))) created_by_name , jt1.created_by created_by_name_owner , N’Users’ created_by_name_mod , LTRIM(RTRIM(ISNULL(jt2.first_name,’’)+N’ ‘+ISNULL(jt2.last_name,’’))) assigned_user_name , jt2.created_by assigned_user_name_owner , N’Users’ assigned_user_name_mod, N’ ’ accounts_bm_budget_package_1_name , N’ ’ accounts_bm_budget_package_1accounts_ida FROM bm_budget_package LEFT JOIN bm_budget_package_cstm ON bm_budget_package.id = bm_budget_package_cstm.id_c LEFT JOIN users jt0 ON bm_budget_package.modified_user_id=jt0.id AND jt0.deleted=0

AND jt0.deleted=0 LEFT JOIN users jt1 ON bm_budget_package.created_by=jt1.id AND jt1.deleted=0

AND jt1.deleted=0 LEFT JOIN users jt2 ON bm_budget_package.assigned_user_id=jt2.id AND jt2.deleted=0

AND jt2.deleted=0 where (bm_budget_package_cstm.budget_request_status_c = N’Budget_Approved’ AND bm_budget_package_cstm.date_final_budget_received_c >= DATEADD(day, + 15, GetDate()) AND bm_budget_package.reuse_ar_c != ‘1’ AND NOT EXISTS (SELECT * FROM aow_processed WHERE aow_processed.aow_workflow_id=N’51e1a9e0-2e20-3fa6-a148-5318bbcb569a’ AND aow_processed.parent_id=bm_budget_package.id AND aow_processed.status = N’Complete’ AND aow_processed.deleted = 0)) AND bm_budget_package.deleted=0::: [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid column name ‘reuse_ar_c’.

Will · 28 March 2014 14:53

Hi dgreene,

Those errors seemt to be related to your custom module. What version of SuiteCRM are you running? Did you have a previous version which was installed and working?

Thanks,

Will.

dgreene · 28 March 2014 14:56

SuiteCRM 7.02. Have been using SuiteCRM since December 2012. Workflow has been working since I upgraded to suiteCRM from the base sugar install - but with these intermittent problems. Unfortunately i’m developing a number of workflows for business processes now and its becoming a more frequent problem.

Using Windows server 2008, IIS, MSSQL if that matters.

Will · 28 March 2014 15:25

Hi dgreene,

Is there any possibility of you installing on a linux environment to isolate if it is OS/MSSQL related?

Thanks,

Will.

dgreene · 28 March 2014 15:28

No. I don’t have a linux environment available.

Can you tell me where the action details are saved so I can attempt to troubleshoot this? Database or a directory?

Will · 28 March 2014 15:31

Hi dgreene,

The table aow_actions stores the actions data.

Thanks,

Will.

dgreene · 28 March 2014 15:33

Will,

That table does not seem to have the specific action step details (fields dates etc) that were selected. That data appears to be stored elsewhere. That’s what I’m looking for.

Will · 28 March 2014 15:38

Hi dgreene,

The data is stored in that table, it’s just stored as an encoded array under the column name ‘parameters’.

Thanks,

Will.

dgreene · 28 March 2014 22:23

There is no way to troubleshoot this issue since the details of the action are stored as an “encoded array”. There is also no rhyme or reason as to why some actions disappear, and some don’t. (see attached screenshot)

No errors in PHP log or SugarCRM log related to AOW.

I need assistance in resolving this issue.

dgreene · 31 March 2014 19:41

See my bug report - i’ve determined what is causing the error.

http://suitecrm.com/forum/bug-tracker/869-workflow-use-of-description-field-creates-issues-with-workflow

techeccentric · 1 April 2014 12:23

I have updated the bug report linked in the post above.

techeccentric · 6 April 2014 02:01

And posted a possible fix with the bug report.