My WebLink
|
Help
|
About
|
Sign Out
Home
8K Consent Calendar 2016 0718
CityHall
>
City Clerk
>
City Council
>
Agenda Packets
>
2016
>
Packet 2016 0718
>
8K Consent Calendar 2016 0718
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/15/2016 3:49:58 PM
Creation date
7/15/2016 3:49:50 PM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Staff Report
Document Date (6)
7/18/2016
Retention
PERM
Document Relationships
Reso 2016-100
(Reference)
Path:
\City Clerk\City Council\Resolutions\2016
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
94
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Download electronic document
View images
View plain text
21Tech Response: <br />San Leandro’s Information Technology RFQ for Accela Development Services Page 19 of 34 <br />#TASK NAME REQUIREMENT TYPE EX.RESPONSE <br />(HRS) <br />LOW <br />(HRS) <br />HIGH <br />8.Building Reports Fix:Consolidated Comments Report for <br />Building Permits need to pick up <br />Conditions from Conditions Tab and <br />Documents from the Documents Tab <br />(that way these items all get to the <br />applicant at one time through <br />Consolidated Comments) <br />Fix Report No The workflow comments are stored in the <br />GPROCESS table's SD_COMMENT field, which <br />is a 4,000-character field. The report would be <br />modified to incorporate workflow comment <br />text. This does not include any additional <br />configuration pertaining to workflow and/or <br />task-specific information. This report will likely <br />require use of a sub report. <br />8 16 <br />9.New User fees not <br />calculating <br />Mike Schaffer added but fees not <br />calculated; believe related to scripts <br />written by TruePoint <br />Bug Fix No Content about transactional conditions and <br />documents can be pulled from the B6CONDIT <br />and BDOCUMENT families of tables, <br />respectively, and included within existing <br />reports. This does not include any additional <br />configuration pertaining to conditions or <br />document metadata. This report will likely <br />require use of a sub report. <br />4 8 <br />10.Future new users What scripts are affected when new <br />users are added, possible to train staff <br />to modify scripts on our own? <br />Training This request needs to be better understood. <br />Based on current understanding, we would <br />identify any special considerations <br />surrounding the creation of new Accela users, <br />and would provide a playbook for how to <br />handle personnel turnover, e.g. new hires, <br />position changes, termination/ separation, <br />etc., and identify all places in Accela that need <br />to be updated, such as user profiles, inspector <br />profiles, workflow designer, shared <br />dropdowns, Standard Choices, etc. Your <br />scripts should not need to be modified, but <br />constructs that they leverage most likely will <br />need attention. This might take some time <br />with specific users to figure out the needed <br />details to resolve an issue. We expect that <br />when we review the error it will reveal a Fee <br />and where it is triggered from (WTUA, ASIUA, <br />etc.) <br />4 8 <br />301
The URL can be used to link to this page
Your browser does not support the video tag.