====== Decision Tracker ======

[[cab_decisions | CLICK HERE]] > Click here to go to the CAB Decisions
----

=====New Hire View=====
Question:  Do we need to add a new view for the New Hire Catalog Item so the notes and worknotes sections are viewabble?
<code>Answer:  We will make the default view for the New Hire Catalog to be 'Project Insight' </code>
----
=====REQ Reopen if closed=====
Question:  If a request is accidentally closed, will we reopen the request?
<code>Answer: NO.  It is not good practice to reopen a closed request. The user will need to resubmit a NEW request</code>
----
=====Time Reporting Decisions=====
====ADMINISTRATION:====
<code>Team meetings, 1 on 1 meetings, deployment meetings, department meetings, change control (anything not related to a different time record)</code>

====NON PRODUCTION OPERATIONS ACTIVITIES:====
<code>Working Work Queues, Re-Occurring Manual Tasks, Running Reports</code>

====PRODUCTION OPERATIONS:====
<code>Help Desk Staff Hours, Creating/Managing Scheduled Jobs/Activities, System Monitoring, Database Updates, Error Logs

Patches, App updates, Security updates</code>

====HELP DESK TICKETS====
<code>Incidents, Security Requests

Meetings about tickets, incidents, communications</code>

====RESEARCH:====
<code>Pre-Project Research & Discovery, Initial Request Estimation This category will NOT be used for an active project, hours will be logged to that specific proj

Research related to a project goes to a project; research outside a project/before project goes to Research project
Solution work: meetings, requirements, forms</code>

====TRAINING:====
<code>Self-Development, Re-Certifications, Seminars, e-Learnings, Mentorship</code>

====SERVICE REQUESTS:====
<code>this counts towards projects, catalog items</code>
----

=====Official DATE Format=====
Question: What is the official Date Format?
<code>Answer: 12/01/2020 or 12.01.2020 or mm/dd/YYYY</code>
----

=====Group Terminology=====
Question: What is the preferred terminology for a group of users?
<code>Answer: Assignment Group</code>
----

=====Request Notifications=====
Question: What notifications will be needed for requests?
<code>Answer: 'Request Created' and 'Request Created on your Behalf'</code>
----

=====PI Integration Project Number=====
Question: Will the project number need to pull back to the PI ticket?
<code>Answer: NO. Due to the duplication, it will not be pulled back at this time.</code>
----

=====Modifying Code Needs Comment=====
Question: Do we need to add our UserID and a comment anytime we modify ANY Code?
<code javascript commentSyntax.js>Answer: YES.   We will comment with our UserID and information
Here are the Standard Commenting Syntaxes going forward:
- HTML:  <! - - Comment Here - -> 
- JavaScript: // comment for single line,  /*  */ for multiple lines 
- Jelly:  <! - - Comment Here - -> 
- XML:  <! - - Comment Here - -> 
- Server Side Comments that are not seen in the browser:  <j:comment> 
</code>
----
=====ADJUST Update Sets=====
Question: When should we adjust update sets?
<code>Answer: It would be appropriate to go to the local update sets and adjust your update sets accordingly.  Options are ‘in progress’, ‘complete’, or ‘ignore’.  If you are still developing this update, they will stay ‘in progress’.  If all development has completed, change them all to ‘complete’, and all in progress ‘default’ update sets and update sets you will not be using, set them to ‘ignore’ </code>
----

=====Question Title=====
Question: 
<code>Answer: Here</code>
----