[Vtigercrm-commits] [Vtiger development] #8624: Migration from 5.4.0 to 6.x doesn't handle VTCreateEntityTask differences

Vtiger development vtiger-tickets at trac.vtiger.com
Wed Sep 9 08:31:27 GMT 2015


#8624: Migration from 5.4.0 to 6.x doesn't handle VTCreateEntityTask differences
-----------------------+------------------------
 Reporter:  alanlord   |      Owner:  developer
     Type:  defect     |     Status:  new
 Priority:  major      |  Milestone:  Unassigned
Component:  vtigercrm  |    Version:  6.3.0
 Severity:  High       |   Keywords:
-----------------------+------------------------
 The Create Entity Task in version 6 is *not* functionally equivalent to
 that in 5.4.0.

 In 5.4.0 We were setting the "Assigned To" field of the new entity to the
 value of the Assigned To of the Triggering Entity.

 In this case when creating a new Account, the workflow creates a new
 LSSite (a custom vtlib module) record. See screenshot from 5.4.0 system.

 In version 6 you can't set the Assigned To of the new record to be the
 "value" of the Assigned To of the triggering Entity. You can only hard-
 code a particular user from the Picklist. See other screenshot.

 This is a regression and a removal of a very important part of the Create
 Entity Task feature.

 Secondly, the Migration scripts do not take this difference into
 consideration. So when you try to open the Create Task editor on a
 migrated system it crashes (just sits there with the throbber for
 infinity) because it expects the value of the assigned_user_id to be a
 userid when it is instead the name of the field: "assigned_user_id". Look
 at the file modules/Settings/Workflows/views/EditTask.php you will see
 where this breaks in the foreach loop starting on line 56.

--
Ticket URL: <http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/8624>
Vtiger development <http://trac.vtiger.com/>
Vtiger CRM


More information about the vtigercrm-commits mailing list