57370_en-US

liliconcom

Minutes Week 20 18-May

 Updates: What are we working on?

1. Met with core team to review testing and training approaches.  

   Project progress has been hampered by:

   • limited resource availability due to existing schedules and current business constraints
   • lack of complete team agreement on breadth of testing, including which test cases, number of test cases, fringe cases, failures, probabilities of occurring, happy path, etc.

Decision to move forward with testing 

All products and countries as well as opportunities in scope

Discussions about training staff globally on new JMP processes. 

Training planning and execution—How do we train everyone on the new JMP process?

• Who will need to be trained?
• When do they need training?
• How to handle new hire training?

Met with several managers to discuss resource needs as they pertain to SFDC. SFDC developer, SAS Macro programmer, and part-time tester. Requistions underway.

Decisions:

1. All products should be within scope of testing
2. All countries should be within scope of testing
3. All types of opportunities within scope of testing
4. Use SFDC to handle queue requests and task assignments in lieu of developing a new tool  (SFDC has built-in workflow and task management capabilities out of the box)

Need Help:

• Troubleshooting API with d-Wise: 
• Why is it failing?
• Changes to COMIT API due to new fields
• Changes to COMIT API due to changed fields
• Continue to work with Orion team to ensure contract / dependency agreement between two systems is in place moving forward ahead of production
• Continue scoping and contact validation requirements gathering of queueing system in SFDC to handle missing and out of sync information with contacts between SFDC and Orion 
• Development of queueing system in SFDC to handle missing and out of sync information with contacts between SFDC and Orion 
• Continue scoping and account validation requirements gathering of queueing system in SFDC to handle missing out of sync information with accounts between SFDC and Orion
• Development of queueing system in SFDC to handle missing and out of sync information with accounts between SFDC and Orion

 

Action Item	Who	When	Comments	Status
Provide JMP data table with list of countries sorted by top grossing revenue	Jon	May 25	This will help focus and prioritize testing and identifying test cases	In-Progress
Schedule 3 hour blocks of time on calendar for testing	Stan	May 25	Invites: Ashley, Tina, Kathy   Testing Approach— War room, meeting for 3 hours a day over two weeks with optional 3rd week if necessary Identification of test cases Movement of test cases from production to test Preparation of test cases Execution and documentation of test cases and their outcomes Review results Iterate if necessary   Timing for testing July 2 through July 13 (off July 4) Optional July 23-27	In-Progress
Post contact and account ID queueing system requirements to community	Stan	May 4	Account validation requirements	Completed
Add Opportunity attachment object to test environment	Antoine	May 25	Add Apex and visual force page code to test environment Create opportunity object to use code	In-Progress
Update production SFDC environment with account IDs	Tina / Antoine	June 15	Continue to update SFDC production environment with GIDB account IDs	In-Progress
Update production SFDC environment with contact IDs	Tina / Antoine	June 15	Continue to update SFDC production environment with Orion contact IDs	In-Progress
Earned credit at team level	Carol		On hold until upgrade testing completed	On hold
Add new SFDC field to capture subject for an attachment	Antoine	March 30	constrained to 50 characters. April 6 Unable to modify attachment object to add subject field. Parsing function will be added to API to handle requirement. Stan created an opportunity attachment object and demonstrated the process of adding attachments at the opportunity level by creating by typing in the subject prior to adding an attachment. Antoine to move from Stan’s development environment into test environment	In-Progress
Add "subject" to attachment	Don	March 30	waiting on SFDC field creation (see action item #6 above) April 6 Unable to modify attachment object to add subject field. Parsing function will be added to API to handle requirement. "|" will be used as delimiter. Construct for naming of file will be: subject | type | filename.extension	In-Progress
Add new SFDC field to capture "type" for an attachment	Antoine	March 30	contracts email expedited April 6 Unable to modify attachment object to add type field. Parsing function will be added to API to handle requirement. Stan created an opportunity attachment object and demonstrated the process of adding attachments at the opportunity level by creating by selecting a type from the drop-down list. Antoine to move from Stan’s development environment into test environment	In-Progress
Add "Type" to attachment	Don	March 30	waiting on SFDC field creation (see action item #6 above) April 6 Unable to modify attachment object to add type field. Parsing function will be added to API to handle requirement. "|" will be used as delimiter. Construct for naming of file will be: subject | type | filename.extension	In-Progress
Decision: actual contact record required in SFDC or dummy contact record with actual passed as attachment or SFDC admin to provide data entry	Jon / Todd / ?		Handled through queueing system as noted above	Deleted
Opportunity type passed to Orion incorrect.  For example, upgrade shown as new	Don	April 6	Investigating. April 6: Working with Orion team to identify possible causes. May 4: Don fixed and attempted to test. Errors indicate that the Orion end point changed May 18: Antoine to work with Neil to confirm which field names changes that may impact API call May 18: Antoine to contact Don (d-Wise) to update macro code to accommodate field mapping changes	In-Progress
API timeout when session is idle for an extended period of time SAS 7612311958	Don		With the API scheduled to run every 5 minutes this should not be an issue.  Workaround is to restart the SAS session.	On hold
Prevent multiple attempts to post same failed record to Orion	Don / ?		Need to provide requirements on how to handle April 6: In rare case that the API is attempting to write to SFDC with successful post (Orion return code) and SFDC has catastrophic failure the API will not process any other requests until this error status is cleared and a successful update to SFDC has been completed	In-Progress
Verify data mapping fields are final	Tina / Antoine	April 13		In-Progress
SFDC 2.0 rollout	Tina			In-Progress
SAS macro API Documentation covering use and how to modify field names	Don	April 13	April 6: d-Wise to make draft available for review April 20 May 4: Draft published in community	In-progress
test case writing / editing	Ashley / Kathy / Stan	April 13	April 6: Identify which test cases need attachments and opportunities created and update accordingly Review Upgrade test cases for completeness; do opportunities and attachments exist	In-progress
Update test cases with opportunity information	Ashley / ?	April 13		In-progress
Execute the Upgrade test cases		April 27		Open
Review account IDs and contact IDs in SFDC test environment for inaccuracies	Kathy / Ashley / Stan	April 20	April 6 Review accuracy for inconsistencies, missingness, and inaccuracies	In-progress
Review matching criterion for Orion account IDs	Antoine / Stan / Kathy	April 20	April 6 Review criterion to see if we can improve accuracy based on findings from review	In-progress
Review matching criterion for Orion contact IDs	Antoine / Stan / Kathy	April 20	April 6 Review criterion to see if we can improve accuracy based on findings from review	In-progress
Review account validation process and contact ID creation process developed by Business Operations	Kathy/ Carol / Stan	April 13	Verify requirements.  Write specifications. Document data flow. Prepare to for full team review.	In-progress
Run SAS job in SFDC test environment to populate account information	Antoine	March 30		Completed
Contact d-Wise with maintenance contract request	Stan	March 28	d-Wise can no longer provide services to JMP as this is not part of their core mission.   We are a Health and Life Sciences focused organization and we are striving to focus on delivering value to those organizations as well as focusing on our core mission - "Innovation for a healthier world".	Completed
Confirm March hours remaining for d-Wise contract	Stan	March 7	~approximately 10 30 hours remaining	Completed
Contact d-Wise to see if they can help with SOP writing	Stan	March 28	d-Wise can no longer provide services to JMP as this is not part of their core mission. We are a Health and Life Sciences focused organization and we are striving to focus on delivering value to those organizations as well as focusing on our core mission - "Innovation for a healthier world".	Completed
Schedule meeting with Business Operations to discuss development activities	Stan	March 29	Will work on documenting account validation and contact ID processes before proceeding. Business Operations will take ownership of this effort. Goal: Round-trip create/read/write of account and contact ID from Orion to SFDC Queueing system to consolidate processing of requests that will allow for resource, efficiency gains, higher quality data, and more predictable timing.	Completed
Add test cases to stage	Antoine			Completed
Add available Orion Contact IDs to SFDC test environment	Antoine	April 6		Completed
Add available Orion account IDs to SFDC test environment	Antoine	April 6		Completed
Document Account validation process	Carol / Kathy	April 6	April 6 First pass of process created. Ready for data flow mapping and requirements writing.	Completed
Document Contact creation process	Carol / Kathy	April 6	April 6 First pass of process created. Ready for data flow mapping and requirements writing.	Completed