Has anyone resolved continuing using PDK and BP with GP2015R2. Right now the PDK dex throws an error related to the new workflow columns. Why do I ask you say? We have nearly 1000 employees and over 65 managers and supervisors entering, submitting and approving time and expenses weekly in GP2013R2 w PDK and BP We have GP2015R2 and the We Cliebnt up in Test with Workflow 2.0 but have now abanadoned it for the following reasons: 1. Performance is unworkable in the WebClient and MS Silverlight for 100s of concurrent users. It would require a farm of web servers. 2. Workfow fails in that only one active workflow can be made that must hold hundreds of employIDs assigned to over 65 managers. It is massive and as created it is impossible to report via Smartlist or SSRS who is assigned to who or to move/edit employees as they move around the company 3. New workflow steps for new managers cannot be added to the workflow as it is active and at any given time there are 100s of timesheets in some form or workflow process. 4. Workflow is not multiuser capable and we have six employees in HR/Payroll who must be able to manage employees, managers and supervisors and set their approval permissions for over 1000 employees. 5. Managers cannot see/report on missing timesheets for their employees. While these basic features were taken for granted in PDK and BP for over eight years, the new Workflow is amateurish at best and would not not implementable for approvals for more than a handful of employees much less hundreds or a thousand of timesheets per week. At this point we are rev locked at GP2013R2 with no upgrade path and must wait now for GP2016 bypassing GP2015R2 entirely or get BP/PDK to work with GP2015, or go out and buy something that works like Paramount or ReqLogics when GP2016 comes out if workflow is still cheesy. Ideas?
↧