City of Madison. Information Services. Crystal Enterprise Polices, Standards, and Guidelines

Transcription

1 City of Madison Information Services Crystal Enterprise Polices, Standards, and Guidelines March 2006

2 City of Madison Crystal Enterprise Policies, Standards, and Guidelines Table of Contents Crystal Enterprise Policies...4 INTRODUCTION...4 PURPOSE...4 COVERAGE...4 SPECIFIC POLICY ITEMS...4 Language...4 Licenses...4 Security...4 Standards...5 Training...5 STAFF RESPONSIBILITIES...5 Agency Head...5 Agency Contact...5 Project Manager/Team Leader (IS)...5 Agency Report Writer...6 IS Developer (IS)...6 Crystal Enterprise Administrator (IS)...6 DBA Administrator (IS)...6 EXCEPTIONS...7 FAILURE TO COMPLY...7 Crystal Enterprise Standards...8 INTRODUCTION...8 NAMING CONVENTIONS...8 Report Name...8 Folder Name...8 Component Name...9 Data Connection...9 Data Foundation...9 Business Element...9 Business View...9 PROCEDURES...9 Requesting Rights to Crystal Enterprise...9 Requesting a New Report...10 Requesting a Change of an Existing Report...10 REPORT DOCUMENTATION...11 REPOSITORY...11 SECURITY...12 Gaining Access to Crystal Developer...12 Gaining Access to Run Existing Reports...12

3 Table of Contents ii Guest User ID...12 Everyone Security Access...12 Statement of Accountability...12 TEMPLATES...13 TEST VS. PRODUCTION FOLDERS...13 VERSIONS...13 Crystal Enterprise Guidelines...14 CONTENTS OF A REPORT...14 USING CRYSTAL ENTERPRISE WITH PROGRESS OR MICROSOFT SQL DATABASE...14 USING CRYSTAL ENTERPRISE WITH ADOBE (MACROMEDIA) COLDFUSION...15 Crystal Enterprise Statement of Accountability...18 Crystal Enterprise Request for User ID...19 Crystal Enterprise Report Specifications...20 Crystal Enterprise Crystal Report Test Results Instructions...21 Crystal Enterprise Crystal Report Test Results Details...22 Crystal Enterprise Crystal Report Promotion...23

4 Crystal Enterprise Policies 4 City of Madison Crystal Enterprise Policies Introduction The City of Madison s Information Services standards and strategic direction is to use: Crystal Enterprise-Crystal Reports as our preferred tool, for the creation and distribution of reports for all City agencies. Purpose By standardizing on this tool, and having policies, standards, and guidelines for its use, the City of Madison will be able to use its limited resources more effectively, keeping costs to develop and maintain the City s reporting needs manageable. Coverage These policies will cover all City of Madison agencies, their employees, and any 3 rd parties doing work on behalf of the City of Madison. Specific Policy Items Language The default language shall be English. Providing report and information in other languages, while it may be desirable, is not required unless there is a specific APM, Ordinance, or Policy that mandates it. If reports and information in another language is required, then a separate plan will need to be established on how and who may maintain that report. Licenses Information Services will be the central administrator of all Business Objects licenses used by any and all agencies, organizations, or units within the City of Madison, although the funds may come from the agency or organization. As such IS will determine software levels. Security All reports on any City of Madison workstations and servers or on any servers hosted by the City of Madison shall follow our Security standards as outlined in our Crystal Enterprise Standards.

5 Crystal Enterprise Policies 5 Standards Standards for coding requirements, general design, naming conventions, page layout, security, etc. will be developed and maintained as needed by Information Services. Training Before any staff is allowed to use Crystal Developer, they must receive appropriate training, as determined by Information Services from an outside vendor. At all levels, there will be various City staff assigned roles and responsibilities. Staff Responsibilities Agency Head Responsible for the authorization of employees who will have access to Crystal Enterprise. Enforce policies and procedures within your agency and ensure each employee signs the Statement of Accountability form. Responsible for designating who will be their Agency Contact and ensure these individuals are afforded the sufficient training and are competent to do the work. Agency Contact Staff should be permanent, non-rotating positions due to the training issues and learning curved involved for Crystal Enterprise applications. Ensure that all Information Systems Policies and Procedures are followed. Fill out Request for Service (RFS) form for Information Service; contact IS Systems & Programming Manager if need be. Review all requests for access to their data in a timely manner and specifically approve access by signing off on the employee Crystal Enterprise Request for User ID for appropriate folder access. Project Manager/Team Leader (IS) Take requests from Agency Head, Agency Contact or Systems & Programming Manager. Meet with customer and gather requirements, timeframes and other pertinent information. Assign IS Developer and communicate with customers and Developer as necessary.

6 Crystal Enterprise Policies 6 Agency Report Writer Agency assigned individual who has been trained by outside vendor on Crystal Report Writing and has a licensed copy of Crystal Developer software on their workstation. Writes or compiles simple reports for their agency as directed by their Agency Head or Manager. Works with IS Developer with technical questions and test environment. Promote Report to personal folder. IS Developer (IS) Ensure that all Information System policies and procedures are followed. Provide time-estimate for the request. Meet with Project Manager and/or Customer on questions specific to reports requested. Write and test reports where applicable. Work with CE IS Administrator to promote and publish reports as needed. Assist others with technical issues related to the creation, design, implementation and distribution of Crystal Reports. Promote Reports to personal folder as needed. Design Business Views when necessary for users of Crystal Explorer Crystal Enterprise Administrator (IS) The City of Madison Crystal Enterprise (CE) Administrator as designated by Information Services has overall responsibility for the City of Madison s Crystal Enterprise Environment. The CE Administrator s duties include but are not limited to: Approval of all Crystal Enterprise workspaces. Maintaining the Crystal Enterprise Policies, Standards, and Guidelines as necessary. Maintaining License inventory and software levels. Granting rights to various Crystal Reports objects. Assisting others with technical issues related to the creation, design, implementation and distribution of Crystal Reports. Setup Data Connections on Appropriate Servers. Monitor Windows Server and Crystal process servers workload. Work with Database Administrator to setup access for required data connections. DBA Administrator (IS) Grant Rights and Setup UserID for Agency Report Writer and/or IS Developer to access tables/views and database.

7 Crystal Enterprise Policies 7 Exceptions Setup, fine-tune existing database servers to enable Crystal to run against server without degrading normal services. Make sure Agency Report Writer and/or IS Developers workstations have the proper ODBC connection (Read Only) and Drivers for Crystal. Any exceptions to these policies or standards will require the approval of the Information Services Director. Requests for exceptions shall be in writing and will state the specific policy or standard that is being challenged and the business reason for the exception. The decision of the Information Services Director shall be final. Failure to Comply Any Agency, Organization, Group, or Application that represents the City of Madison or that is hosted by the City of Madison that fails to comply with these policies and standards may be required to remove their reports until they are in compliance.

8 Crystal Enterprise Standards 8 City of Madison Crystal Enterprise Standards Introduction The purpose of these standards is to provide members of the City of Madison, Crystal Enterprise Developers with a complete tool for creating and maintaining the City s Crystal Enterprise environment. The standards outlined are essential to maintaining a consistent, professional, and well-maintained secure system. These standards will be periodically reviewed and updated as necessary. Naming Conventions Having a naming standard will reduce opportunity for error. To eliminate inconsistencies in naming and possible errors when creating Crystal Reports all users should follow the standards presented in this section. To avoid compatibility problems when naming reports, folders, and components follow these guidelines: Always use lower case letters for names and extensions. Use only alpha characters: a-z and numbers 0-9 in names. Never use special characters except the underscore _ for files only. Do not use in folder names. Never use spaces or dashes in a name, instead use a _ for files only. Do not use in folder names. Use descriptive names and when possible limit them to one word; however avoid creating unreadable names for the sole purpose of limiting name length. Report Name Crystal Enterprise allows a flexible alphanumeric structure to a report name. Behind the scenes, Crystal Enterprise establishes a number to track the object. This allows the name to be changed later on without disturbing all of the schedules and historical instances. It is recommended that you create a report name that is most informative for the user. If an organization needs to refer to a report from outside of Crystal Enterprise, and you want to refer to the exact report reference, then using the report ID identified by Crystal Enterprise would be the recommended method. This is identified by navigating to the location where you would change the name of the report. It is the numeric value at the end of the field described as the file location. Folder Name Crystal Enterprise allows a flexible alphanumeric structure to a folder name. This should be established to provide the user with as much

9 Crystal Enterprise Standards 9 information as possible. Short, cryptic names should be avoided. Often folders are structured into logical work groups like departments or teams. Component Name Crystal Enterprise allows a flexible alphanumeric structure to all of the components of a business view. Procedures Data Connection The data connection should be prefaced with dc_ and then a descriptive name. This makes the element easier to identify later. Data Foundation The data foundation should be prefaced with df_ and then a descriptive name. This makes the element easier to identify later. Business Element The business element should be prefaced with be_ and then a descriptive name. This makes the element easier to identify later. Business View The business view should be prefaced with bv_ and then a descriptive name. This makes the element easier to identify later. Requesting Rights to Crystal Enterprise The following is the procedure for requesting rights to Crystal Enterprise. 1. Request is received by Information Services Department for a Crystal Enterprise User ID from user. 2. User is directed either by or telephone to the Information Services website to download (1) Crystal Enterprise Statement of Accountability, and (2) Crystal Enterprise Request for User ID form. User is also notified that they must have a valid Network User ID in order to process their request, along with Director (Agency Head) signoff. 3. User signs the Statement of Accountability form, attaches it to the Request for a Crystal Enterprise User ID form, and gives it to their Supervisor/Manager for completion. 4. The Supervisor/Manager completes all the appropriate areas of the form (obtains Agency Head signature) and sends it to the Information Services Department Attn: Crystal Enterprise Administrator (IS): Request. 5. The Crystal Enterprise Administrator (IS) coordinates with Network Administration to create the User ID in Crystal using the Network User ID and then with the IS Database Administrator (DBA), for setting up access to specific database tables. 6. IS DBA notifies IS Crystal Enterprise Administrator of table access setup completion.

10 Crystal Enterprise Standards Crystal Enterprise Administrator (IS) tests User ID, password, folder and group access to verify the user s expectations have been met. They then forward to IS Developer. 8. IS Developer notifies staff of the user s User ID and password for Crystal Enterprise. 9. IS Developer follows up with user to ensure all access is as expected by the user. 10. IS Developer dates and scans the copy of the User ID Request form into the City of Madison s imaging system, under the IS Catalog, Crystal Enterprise folder. Requesting a New Report The following is the procedure for requesting a new report. 1. The user who wants a report obtains permission from their Agency Contact. 2. The Agency Contact fills out the RFS (Request for Service) form and submits to Information Services. 3. Information Systems assigns Project Manager. Project Manager/Team Leader works with user and IS Developer if necessary to complete the Crystal Reports Specifications. 4. The IS Developer creates and tests the report using Crystal Reports. During the development cycle, the user should save the report to his/her network USER drive. 5. The IS Developer will Promote the report to Crystal Enterprise into a test folder. 6. The IS Developer will notify the user to test the report. The user should fill out the Crystal Enterprise Crystal Report Test Results Details document to record the success/failure of each report test. 7. Once the report has completed testing, the IS Developer should complete the Crystal Enterprise Crystal Report Promotion document and forward to the Crystal Enterprise Administrator (IS). 8. The CE Administrator (IS) will move the object from the test folder to the production folder and configure the object based on the information on the Crystal Report Promotion document. 9. The CE Administrator (IS) will now notify the IS Developer that this report is now available. IS Developer will notify the end-user. Requesting a Change of an Existing Report The following is the procedure for requesting changes to an existing report. 1. The end-user who wants a report change, obtains permission from their Agency Contact. 2. The Agency Contact fills out the RFS (Request for Service) form and submits to Information Services. 3. Information Systems assigns Project Manager. Project Manager/Team Leader works with user and IS Developer if necessary to complete the Crystal Reports Specifications. Only the changes need to be described in this document.

11 Crystal Enterprise Standards If the IS Developer is using an older version of Crystal Reports, the IS Developer should retrieve the report object from the network. If the IS Developer is using a current version of the Crystal Reports, then the report object should be retrieved from Crystal Enterprise. 5. The IS Developer modifies/tests the report using Crystal Reports. During the development cycle, the user should save the report to his/her network USER drive. 6. The IS Developer will Promote the report to Crystal Enterprise into a test folder. If the IS Developer is using an older version of Crystal Reports, then the report should also be saved into the shared storage location on the network. 7. The IS Developer should notify the user to test the report. The user should fill out the Crystal Enterprise Crystal Report Test Results Details document to record the success/failure of each report test. 8. Once the report has completed testing, the IS Developer should complete the Crystal Enterprise Crystal Report Promotion document and forward to the Crystal Enterprise Administrator (IS). 9. The Crystal Enterprise Administrator (IS) will move the object from the test folder to the production folder and configure the object based on the information on the Crystal Reports Promotion document. 10. The CE Administrator (IS) will then notify the IS Developer that the report is now available. IS Developer will then notify the end-user. Report Documentation Good documentation techniques must be applied to reports created through Crystal Reports. This includes an appropriate request process for new reports and report modifications. Report specifications are the best source of detail information about why and how a report was created. In addition, notes regarding the report should be embedded inside the report. A popular technique to do this is to create a formula called, Report Information. The formula contains the name of the original author, creation date, and report description. It should be updated when modifications are made to the report to record what was done and why. Repository The Repository is the central location where Information Services will store and manage your report objects. Data definitions such as custom functions and custom SQL commands are also stored and maintained here. These objects are then accessible to users and report developers for use in new reports that can be distributed throughout the City of Madison. Physically, the Repository is a database that stores supported object types. These types include: Text objects Bitmaps Custom functions Commands (queries)

12 Crystal Enterprise Standards 12 By Information Services maintaining a shared Repository of report objects, we can modify a particular object and update all reports containing that objected as they are opened for use; which is efficient in the standardization of reports and staff resources. Security All reports on any City of Madison workstations and servers, or on any servers hosted by the City of Madison shall follow secure coding practices as outlined in A Guide to Building Secure Web Applications and Services by the Open Web Application Security Project. These include: Protecting database queries from SQL injections. Using SSL to protect secure transmissions of logins and secure data. Integrating any objects requiring authentication with Active Directory services. Documents should not contain information in the document headers, footers, or anyplace else that can disclose a login id. For example: a document footer with f:\users\isxyz\ should not be allowed. Document properties should not contain initials or the login id of the document author. Adherence to the City of Madison Network and Security Policies is required. Gaining Access to Crystal Developer For access to Crystal Developer License, Agency Report Writer must have permission of Agency Head, appropriate training and be properly licensed. Gaining Access to Run Existing Reports In addition to the Statement of Accountability, a Crystal Enterprise Request for User ID form must be completed and signed by the report owner and appropriate supervisor(s). Guest User ID Information Services will be disabling the guest account feature in Crystal Enterprise. By disabling the Guest account, we ensure that no one can log on to Crystal Enterprise with this account. Everyone Security Access In environments where security needs to be very restricted, Information Services will be setting security for the Everyone Group to No Access. Then each group will be added to the root folder level and set to the appropriate access to meet their needs. This will prevent users from other agencies from accessing the reports for agencies other than their own, unless permission is granted. Statement of Accountability Since the information contained in reports can contain sensitive or confidential information, a Statement of Accountability must be signed and

13 Crystal Enterprise Standards 13 returned before access can be granted. Each employee at the City of Madison who will have access to the Crystal Reports/Enterprise system must fill out the form listed on the following page. Templates A template is an existing report file whose formatting can be added to a new report. At the same time, the formatting of the template report s fields and report objects are applied to the new report. This is very useful to increase the efficiency of report development and to create a consistent look and feel. Templates are best managed by storing them in Crystal Enterprise so multiple users can utilize them. Templates can also be setup by groups (or agencies) to address unique requirements to these areas. Note: Information Services will create a template that will be used by all IS Developers, Agency Report Writers, which will include, (report name, page numbers n of nn, and date/time run). This will need to be applied to any and all reports that are written. Test vs. Production Folders There are many different techniques that can be used to establish a development/test/production promotion process within a single instance of Crystal Enterprise. A popular method is to use test vs. production folders. The root folders are set with your production folders (i.e. Police, Finance, etc.). An additional root folder is created for Test. The subfolders underneath the Test folder contain all of the root production folders (i.e. Police, Finance, etc.). From that point on the folder structures are the same. The only reports kept in the test set of folders are the ones currently being tested. Once they are approved, they are copied to the appropriate production folder and then removed from the test folder. That way you know which reports are the latest and this reduces the confusion found when the same report exists in both the production and test folders. Versions The City of Madison has a variety of Crystal Reports versions in use. These include v8.5, v9, v10 and currently v11. This creates a potential conflict during the development cycle reports are converted into the latest version of Crystal Reports when the report is promoted to Crystal Enterprise. To allow the document to be modified at a later date, the report should be saved as a Crystal Report to a predetermined storage location on the City of Madison s local area network. This is only needed when a developer is using a different version of Crystal Reports then the version of Crystal Enterprise. Unless required to support a specific vendor application, all Crystal Developer Licenses will be upgraded to the current version of Crystal within one year of any upgrade or change to Crystal Enterprise.

14 Crystal Enterprise Guidelines 14 City of Madison Crystal Enterprise Guidelines These guidelines are designed as an aid to anyone who administers, creates, or modifies reports for the City of Madison. While they are only guidelines, we strongly encourage you to follow them. Doing so will help everyone involved now or in the future with Crystal Reports. Contents of a Report Before you begin creating a report, you need to determine what information your report is going to include. If you don t make plans, you might end up with a report that you can t use, or one that you ll need to spend a lot of time modifying to fit your needs. Two elements you should consider when creating a report include the content of the report and developing a prototype on paper. Ask yourself the following questions: 1. What is the purpose of the report? 2. Who is going to use the report? 3. Is your report going to include a title? a. If so, what will that be? 4. What data will you use in the report? 5. What data will be included in the body of the report? 6. Does the data exist or do you need to create it? 7. What types of data will you include in the report? 8. Will the data need to be grouped? 9. Will you need to sort the data? a. If so, how? 10. Will the data be limited to specific records or groups? 11. Will the data need to be summarized? 12. Will any of the data need to be highlighted? a. If so, why? 13. In what order will the data in the report need to be printed? 14. How often will the report need to be printed? 15. How often will the report need to be generated? 16. Who will need to get the report? 17. What format will the report be distributed? Using Crystal Enterprise with Progress or Microsoft SQL Database 1. Agency Report Writer and/or IS Developer needs to request from CE Administrator (IS) what tables/views are needed from associated database(s). 2. CE Administrator (IS) setups a userid for the Agency Report Writer and/or IS Developer to use to design/develop a report. 3. CE Administrator (IS) setups an ODBC connection on the appropriate CE server for the Agency Report Writer to publish to.

15 Crystal Enterprise Guidelines Agency Report Writer and/or IS Developer creates an ODBC connection on there workstation and designs the report. NOTE: Progress - Workstation must have the Merant ODBC driver installed via the Progress network share. NOTE: installed. MS-SQL - Workstation must have SQL connection or client tools Using Crystal Enterprise with Adobe (Macromedia) ColdFusion Crystal Enterprise (Saving the crystal reports): The crystal reports have to be saved on the crystal enterprise server. A folder webaccess has been created to store all reports to be published on the web. Setup the datasource on the Enterprise server. Check the database or datasource properties. Set permissions to allow the user(webaccess) Full Control. Disable prompt for logon, if you want crystal not to ask for username, password. To access the server information for the web, please contact the CE Administrator, IS. Web server: 1. Location of the crystal function files. a. The asp files calling the crystal reports from the crystal enterprise are stored on the webapp server at : C:/Inetpub/wwwroot/crystalasp/ b. The folders param, querystring_param and view, have functionality to call the crystal reports from the enterprise server. 2. Folder functionality: a. Param: Redirect cold fusion files to this folder if the parameters can be passed directly from the form without any alterations. b. Querystring_Param: Redirect coldfusion files to this folder if functions / changes have to be applied to form values. The form values after changes have to be passed through the querystring. c. View: Redirect coldfusion files to this folder if no parameters are passed to the report. 3. Examples: a. View Report without passing parameters. <a href="/crystalasp/view/viewreportintro.asp?report=reportname.rpt" target="_blank">text </a> b. Report with parameters (Parameters w/o modifications)

16 Crystal Enterprise Guidelines 16 <a href="/crystalasp/querystring_param/view_report_parameters.asp target="_blank"> c. Report with parameters (Parameters with modifications) <a href="/crystalasp/querystring_param/view_report_parameters.asp?rep ortname=rptname.rpt&val1=<cfoutput>#val1#</cfoutput>" target="_blank"> 4. Passing Parameters: Specify the parameter names in the same sequence as called in the report. Example: Lets assume the report needs 4 parameters, such as - firstname, lastname, date range and address The parameters can only be named in a specific order to pass to the report. Firstname will be passed as parameter val1. Last name will be parameter val2. Date range will be parameter from3, to3. Address will be parameter val4. You will have to be very specific in the way the parameters are named. You can only name the parameters as val(i) for values, from(i), to(i) for date ranges, where i corresponds to the number of the parameter. Report where the parameters are passed from the form, specify ReportName as one of the form elements (hidden or whichever way is appropriate according to the form) For example (In Coldfusion): A parameter can be passed through a form as a hidden variable <cfform name= xyz method= post action= abc.cfm > <input type= hidden name= ReportName value= XYZ.rpt > <input type= submit name= Submit value= View report > <cfform> Specify parameters as val(i) Specify date ranges as from(i), to(i) Reports where modifications are made to the form elements, you will have to pass the ReportName and the parameters in the querystring. The parameters follow the same format as above.

17 Crystal Enterprise Guidelines 17 Reports without any parameters need only the ReportName in the querystring.

18 Crystal Enterprise Standards 18 City of Madison Crystal Enterprise Statement of Accountability TO: SUBJECT: Information Services, Crystal Enterprise Administrator Crystal Enterprise Report System Policy I understand that as part of my duties and responsibilities as an employee at the City of Madison, I may be given access to the Crystal Enterprise Reporting system. The information contained in this system is often of a private nature, and I acknowledge that is my responsibility to maintain the privacy of those records as stated in the City of Madison, Information Services, Crystal Enterprise Polices, Standards, and Guidelines document. I also agree to follow all City of Madison s Ordinances, APM s, State and Federal laws in accordance to open records. I understand that I am responsible for not sharing my password. I further acknowledge that my failure to follow these rules will subject me to disciplinary action up to and including dismissal as well as possible legal action. (Signature) (Print Name) (Last, First, Middle) (Department Number) (Department) (Date)

19 City of Madison Crystal Enterprise Request for User ID The City of Madison Crystal Enterprise Administrator (IS) must approve all requests for access to data that comes from agency employees. To do this, the Agency Coordinator will look for appropriate signatures and authorization on this form. Please fill in the appropriate blanks (type or print) First Name Initial Last Name Department Phone *Network User ID *Applicants must have a valid Network User ID in order to obtain a Crystal Enterprise ID. Example: ISXYZ. New Crystal User Change of Duties Change Folder Access Modify Access to Folders Your access to various reports is based on the folders and groups assigned to your User ID and required for your job. Your Supervisor/Manager will indicate which folders that you need access to by listing them below: Folders and/or Report Name Check One Access box below for each folder checked on the left. View Only Run Reports View Only Run Reports View Only Run Reports Check here if you have View Only Run Reports Developer s License View Only Run Reports and need appropriate View Only Run Reports access View Only Run Reports View Only Run Reports View Only Run Reports View Only Run Reports Approval is needed from the designated agency/department. Requested by Supervisor Phone: Date: Agency Head Date: *Confidential Agency Folder Approval: Agency Name: Director: Date: The following signature is required on all changes and requests for a Crystal Enterprise User ID. Approving Agency Director: Date: A SIGNED STATEMENT OF ACCOUNTABILITY MUST ACCOMPANY THIS FORM IF ONE IS NOT ALREADY ON FILE WITH INFORMATION SERVICES.

20 City of Madison Crystal Enterprise Report Specifications Report Name Completed By Contact Name Title Date Phone REPORT DISTRIBUTION Scheduling Details Identify when the report should be executed Distribution Method Identify where to print or the report DATA Location Identify the location of the data to be used in the report. Join Details If more then one table, identify how the tables are to be joined together. Include the identification of key fields and join types. User ID / Password Identify the user id and password for each data source. REPORT LAYOUT Provide an example of the report layout (w/graphs if needed). Include the identification of any special formatting expectations (dates, decimals, bolding and color). Example: FIELD MAPPING Field Name Sample Value File Field Notes Customer ACME Co. Tbl.Customer CUSTNAME SORTING- PARAMETERS FILTERS In this section of the specification, identify any expectations regarding data filters, data sorting, or parameters that will control the execution of the report.

21 Instructions: City of Madison Crystal Enterprise Crystal Report Test Results Instructions Each test scenario executed needs to be recorded regardless whether the test results are considered successful or not. The information from the test results documentation will assist the Developer in resolving any errors found faster and with fewer test cycles. A report copy should be printed for each test result scenario performed. For large reports, print the page(s) used to determine that the report was successful or not. Crystal Test Results Details Forms: Test No. Each test should be incremented by 1 to identify each test scenario. Report The report name. Success/Failure In some way, indicate whether the test results are considered successful or not. (example: highlight, circle name, etc.) Date The date that the test was conducted. Person Conducting Test The name of the person who conducted the test. Data Source Location Identify the data source location used for the test. Example: FireSQL-Production or FireSQL-Test Execution Method The method for the test. Example: ed pdf, or Crystal Rpt. Test Description A short description that describes why this test was performed. Parameters Option Abbreviated description of parameter. Parameters Value The value entered when executing the report. Expected Results This should be filled in for failed tests to describe what should have occurred. Actual Results This should be filled in for failed test to describe what actually occurred.

22 City of Madison Crystal Enterprise Crystal Report Test Results Details SUCCESS FAILURE TEST NO. 1 REPORT: Date: Person Conducting Test: Date Source Location: Execution Method: Test Description: Parameters: OPTION VALUE Expected Results: (Apply IS mandated page layout Template) Actual Results:

23 City of Madison Crystal Enterprise Crystal Report Promotion (Form to be used by Information Services) GENERAL INFORMATION Report Name: Developer: Approved By: Date: Promote from: Development to Test Environment Test to Production Environment What folder is this currently located in? What folder is this to be moved in? DATE SOURCE If this report is a dynamic data source, skip this section. Define the new data source location to be used for this report. This can be a different business view or stored procedure or different set of tables. The report will need to be edited and saved to the new folder. Use the Set Data Source Location function from the Database dropdown menu within Crystal Reports. Once you complete, execute the Verify Database function from the Database dropdown menu within Crystal Reports. PROCESS Database Prompt user for Database login? YES NO If no, use the original or a custom database login? ORIGINAL CUSTOM If custom, what are the credentials? Applied IS mandated page layout template? Server Database User YES NO Password Parameters Parameter Description Default Parameter Value

24 Filters Filter Expression Printer Is the report to be printed to the same location regardless of the user? YES NO If yes, specify the printer location SCHEDULE NOTE: Ignore this section, if this is an interactive report. Frequency Daily Weekly Monthly Calendar Start Date/Time Destination Is this report to be ed automatically? YES NO ADDRESS: Format What format do you want the report created? (i.e. Adobe, Excel) The default is a Crystal Report RIGHTS Describe the user/groups and appropriate security if this report is to have a different set of security rights then the folder does.