Laserfiche WebLink
Features &Functionality <br />Hardware <br />The City may opt for a variety of hardware peripherals to enhance the CivicRec experience. CivicRec <br />can be integrated with magnetic stripe readers, barcode readers, thermal printers, cash drawers and <br />more. While CivicRec does not provide this hardware, we are happy to assist with procurement and <br />implementation. <br />Release / Upgrade Schedule <br />CivicRec currently utilizes a monthly release schedule. The City of Santa Ana can expect to receive an <br />average of one new feature per month. We also try to release a new major module quarterly. If bugs are <br />identified, those are "hotfixed" into production and do not await our standard release dates. <br />CivicRec is an Saa5 solution and all customers are on the same code base. Product enhancements <br />are provided on an ongoing basis to our clients at no additional charge, Many, if not most, of these <br />enhancements originated from a customer enhancement request that was applied to base product and <br />made available to all CivicRec customers. <br />System changes are communicated via our website (users will see a notice upon login). For major changes <br />that may require additional staff training (e.g., a brand new module is being released), we will notify the <br />City in advance and schedule the rollout with you as appropriate. <br />We base our roadmap on requests from our customers as well as on our own internal product goals, We <br />maintain a roadmap request system that allows for customers to request changes and to up/down vote <br />ideas that are under consideration. <br />PC] Compliance <br />For credit card security, CivicRec maintafns PCI compliance through an Approved Scanning Vendor <br />(ControlScan). We are scanned monthly and provided a quarterly certificate of compliance. Our customers <br />are provided a copy of that certificate for use in their own PCI Compliance. <br />We also try when possible to take CivicRec (and you) completely out of PCI scope by leveraging <br />"hosted" payment pages when available. Many payment gateways have payment forms that can be <br />embedded within CivicRec (or that the browser can be redirected to) that ensure card data never touches <br />the CivicRec servers. Instead, the card data is keyed directly into the payment gateway's form, and <br />CivicRec simply receives a notification that the payment was successfully made, <br />42 <br />