[UWRF ITS] Creating Information Systems Requests

Creating Information Systems Requests in Footprints

The Information Systems Requests project in Footprints is designed to track eSIS customizations, report creation requests, run report requests, and upgrade requests. This document contains field descriptions to assist you in filling out this form. To create a new request, login to the Information Systems Requests project and click Create Issue. Fill out the new Issue as desribed below.

Title:		Short description of your request.
Priority:		Assign a priority to your request.

Priority Description

Urgent Without this request a large number of people are being negatively impacted right now. Immediate action is needed to resolve this problem.

High Without this request an individual, or small group of people, will have significantly more work to perform in the near future.

Normal This request is needed within the specified time frame. Other methods are available as a work around.

Low This request would be nice to have.

Requests should follow the process flow diagram. Typical status flow is Open > Functional Approval > Technical Approval > Approved > InProgress > Completed > Move to Production > Closed.

Status:

Shows the status of the current request.

Status Description

Open Initial Request status. All requests start in this status.

Functional Approval Each Functional Lead (AD, REC, FA, SF) needs to add a comment stating they approve this request. The last person to approve the request will also need to change the status to Functional Approval.

Technical Approval An IS team member will review and fill out the Technical Area of the request and change the status to Technical Approval.

Approved Set by Project Manager when they approve the request.

InProgress Technical team member may set the status to InProgress so others can see that work has begun.

OnHold Request has been put on hold and will not be worked on in the near future.

Completed Request has been completed and is ready for testing.

Move to Production Testing has been completed and the request is ready for production

Closed Request has been moved to production.

Description: Description of Request. All information entered in this area is time-stamped and user identified. This is the area where all approval comments will be entered. It is also the location of any changes, comments or other such note worthy items to be entered.

RequestType: Enter the type of request being made.

RequestType Description

Customization Request to change, add, or remove some piece of functionality from the software system..ie eSIS.

Report Request to create a new report. Requests to change a report should be placed in the Description of the original request and change the status back to Open.

Run Report Request to run a report that has already been created. Reports that are available can be found as a solution in the Knowledge base or by searching for Reports.

Upgrade Request to upgrade software, operating system. Example: CDR updates, PeopleSoft Patches and Fixes.

DueDate: Date the request needs to be completed by.

Modules Affected: Multi-select field to indicate which functional area(s) is affected by this change.

Navigation: eSIS page navigation or bread crumbs. Ie..Build Community > Comments > Use > Personal Comments.

Process Functionality: This field only needs to be filed out for customizations.

Process Functionality Description

New Additional functionality that does not exist

Enhance PS Change to existing PeopleSoft Funtionality

Replace PS Replace PeopleSoft Functionality with this customization.

Impact:

Describe the impact this customization/report will have on business operations. Include the impact of NOT doing this requested customization / report in terms of business operations and/or cost.

Alternate Options: List at least one alternate option to resolve the issue. Give the possible impacts of using the alternate option.

Permission List Security: Which permission list will need access to this customization/report.

Data Fields: What data fields do you need in this report.

Run Frequency: How often you want this report or process run?

Run Frequency Detail: More detail about the frequency.

Distribution/Notify List: List of email address for those people you want to receive this report or be notified on failure for this scheduled customization.

Technical Area

Difficulty:		The Technical Team will determine what the level of complexity is based on the definitions given below.
Environment:		The environments that contain this Request.
Report Type:		The type of report that was created to satisfy this request.
Prior ID:		The Customization/Report ID that was converted from prior tracking method.
Technical Impact:		Describe the solution in technical terms. Include the possible impact regarding patches/fixes/upgrades. Also, include an estimate of the time needed to complete.
Objects used/created:		Name of objects (PeopleSoft, RDS..etc) used or created in satisfying this request.
Object Type:		Select all object types created or modified.
Customization Category:		Category for this customization. The area affected by this customization.
Installation Instructions:		Instructions for installing or moving this customization from one environment to another.
Customization Path:		Complete path where this customization can be found.
Original Path:		Complete path to the original objects prior to their change.

Technical Documentation: Guidelines: Create sections in this area for each staff member that worked on the request. Each staff member should enter details, as defined below, about what they did on the request. Include details and notes on items such as the following:

SQR’s or AE’s created, what they do and their reason for doing it
PeopleTool objects created or modified (i.e. fields, records, pages, components, menus, app engines, etc.)
PeopleCode created or modified, and its purpose
Breadcrumbs of where new pages were added
Run controls created or used
Process Definitions created and Process Groups to which they are assigned
The project to which the customization belongs
What security actions are granted to which permission lists
Problems discovered implementing the request

Attachments:		Attach any additional documents necessary, such as before and after snapshots of page modifications, sample of report output, etc
Time Tracking:		Enter the amount of time you spent working on this request. You can enter your time spent by date or you can enter a total once completed. The time-tracking functionality will total all times entered in relation to this request. You can create all kinds of time tracking reports See: Reports > Time Tracking in this Project.

GO You must push GO to save.

Web site comments
Need immediate assistance?
Call the HelpDesk at (715) 425-4357 (HELP)

Site Map |
Google Custom Search

Last modified: August 23, 2007

Priority	Description
Urgent	Without this request a large number of people are being negatively impacted right now. Immediate action is needed to resolve this problem.
High	Without this request an individual, or small group of people, will have significantly more work to perform in the near future.
Normal	This request is needed within the specified time frame. Other methods are available as a work around.
Low	This request would be nice to have.

Status	Description
Open	Initial Request status. All requests start in this status.
Functional Approval	Each Functional Lead (AD, REC, FA, SF) needs to add a comment stating they approve this request. The last person to approve the request will also need to change the status to Functional Approval.
Technical Approval	An IS team member will review and fill out the Technical Area of the request and change the status to Technical Approval.
Approved	Set by Project Manager when they approve the request.
InProgress	Technical team member may set the status to InProgress so others can see that work has begun.
OnHold	Request has been put on hold and will not be worked on in the near future.
Completed	Request has been completed and is ready for testing.
Move to Production	Testing has been completed and the request is ready for production
Closed	Request has been moved to production.

Description:		Description of Request. All information entered in this area is time-stamped and user identified. This is the area where all approval comments will be entered. It is also the location of any changes, comments or other such note worthy items to be entered.
RequestType:		Enter the type of request being made.

RequestType	Description
Customization	Request to change, add, or remove some piece of functionality from the software system..ie eSIS.
Report	Request to create a new report. Requests to change a report should be placed in the Description of the original request and change the status back to Open.
Run Report	Request to run a report that has already been created. Reports that are available can be found as a solution in the Knowledge base or by searching for Reports.
Upgrade	Request to upgrade software, operating system. Example: CDR updates, PeopleSoft Patches and Fixes.

DueDate:		Date the request needs to be completed by.
Modules Affected:		Multi-select field to indicate which functional area(s) is affected by this change.
Navigation:		eSIS page navigation or bread crumbs. Ie..Build Community > Comments > Use > Personal Comments.
Process Functionality:		This field only needs to be filed out for customizations.

Process Functionality	Description
New	Additional functionality that does not exist
Enhance PS	Change to existing PeopleSoft Funtionality
Replace PS	Replace PeopleSoft Functionality with this customization.

Impact:		Describe the impact this customization/report will have on business operations. Include the impact of NOT doing this requested customization / report in terms of business operations and/or cost.
Alternate Options:		List at least one alternate option to resolve the issue. Give the possible impacts of using the alternate option.
Permission List Security:		Which permission list will need access to this customization/report.
Data Fields:		What data fields do you need in this report.
Run Frequency:		How often you want this report or process run?
Run Frequency Detail:		More detail about the frequency.
Distribution/Notify List:		List of email address for those people you want to receive this report or be notified on failure for this scheduled customization.