CSC’S Exceed

ISSUE FORM

NOTE: Copy/Paste functions can be used to complete data entry in FSITS for the required Short and Long Description fields. Save form as IssueForm*.doc. Customer-specific identifier may be used following IssueForm.
Today’s Date: / Customer Ref. Number: / CSC Issue Number: / System date: [Date set in the environment where issue was discovered]
Name of person completing form: / Person to contact (include telephone, email):
Priority Requested: [Critical, Serious, Important, Moderate, Non-critical]
Short Description:
Detailed (Long) Description: [Include system dates, transactions processed and transaction dates]
Steps to reproduce: [Include specific workflow, dates and transactions used. Include screen prints to illustrate problem or show evidence of defect]
1) 
Was this recreated on a new policy? / Yes / No
If this is a PRODUCTION problem, impact on production data: [Holding up production, performance or output impacted, data written to database incorrectly, other]
Is there a work-around available?:
Logon ID: [User’s ID being used when problem was detected] / Environment: [Environment in which the problem was identified including name and release level]
If this is a TESTING problem, type of testing: [mark selection with “X” in left column]
IVP / ATD: / Step:
Ad hoc
Code Evaluation
Other / Explain:
PRODUCT INFORMATION
Exceed Application:
Client Name: [If issue is in Client, include client’s name. If in Billing, Policy or Claims, list all associated clients]
If Issue is in Client:
Attach Client SPUFI results (The member name in QRYLIB is CIWQQRY1)
If Issue is in Policy:
Policy Number:
Line of Business: / Transaction dates: [List each transaction associated with the policy and its corresponding transaction effective date]

Attach Policy SPUFI results (The member name in QRYLIB is UWSQQRY4)

If Issue is in Billing:

Account Number:
Attach Billing SPUFI results for specific bill account: [Before running SPUFI, from the database where data is being captured, update (1) Database qualifier, (2) Bill Account Tech ID, (3) Policy ID, and (4) Bill Account Number. NOTE: This SPUFI is based on Exceed release 2.4.1. Those operating on earlier releases may need to comment out references to tables and/or columns that are not applicable.]

If Issue is in Claims:

Claim Number: / Date of Loss:
Comments: [Additional information such as error messages and pertinent comments, attachments, etc.]

1

Form Version: 8/8/12