Content Comparison

18/10/2024

Recording Link

Jira Tickets discussed in the session:

#	Key	Summary
1	TAPSS-2321	UC01 Types of Activities
2	TAPSS-2188	UC16 Activity and Details Visibility - TAP wide
3	TAPSS-2328	UC08 Specify activity User Experience for Call Task (Layout)

Decisions

#	Jira#	Decision Summary
D-031	TAPSS-2321	This ticket is now 'Ready'. Business sign-off required
D-032	TAPSS-2188	How to define 'sensitive' data? : To be defined by Field, not by the record.
D-033	TAPSS-2188	If someone send sensitive information (credit card details etc), we should not store in system. Not part of this ticket but potential action to addrerss it in the future Training perspective How to remove what's in the system as a separate initiative.
D-034	TAPSS-2188	Q: is there any DO who want to keep private activity? Business to confirm but the discussion is not part of this ticket and activity should be public A:Decision is to keep it public.
D-035	TAPSS-2188	Q: Why block non-tap user to view if we are aiming to not store sensitive data? A: there are non-tap users who we still want to block further details not just stricktly privacy sensitive but tap-sensitive. May not be legal-breach, but more for commercial sensitivity.
D-036	3.TAPSS-2328	There are fields that we need business decision on before progressing to the next step. Call Subject Picklist vs Subject free text Call Resulsts picklist values Purpose picklist values Type picklist values.

Actions

#	Jira#	Action	Action Owner
A-015	TAPSS-2321	Business Sign-off for the ticket Build efforts will be distributed to other ticket but training and change management to refer this ticket for the confirmed types of activities	john.lardis tina.verma for Training piece
A-016	TAPSS-2188	Sekar to confirm the design and progress	sekar.krishnan
A-017	3.TAPSS-2328	4 Jira subtasks for the business decision and input are now assigned to John to finalise so TAPSS-2328 can progress: TAPSS-2360 Decision on Call subject (Picklist) vs Subject with free text TAPSS-2361 Decision on Call Result Picklist values TAPSS-2362 Decision on Purpose Picklist values TAPSS-2363 Decision on Type Picklist values	john.lardis

Recording Link

Jira Tickets discussed in the session:

#	Key	Summary
1	TAPSS-2326	Relating Activites to Accounts and Contacts
2	TAPSS-2324	Backdate Actvities
3	TAPSS-2331	Objects with Activity Component
4	TAPSS-2117	Surface Substantive Activity into Task pagelayouts
5	TAPSS-1862	As a Development Officer, I want to have my opportunity stage to be Early Cultivation or Late Cultivation
6	TAPSS-2314	As a Development Officer, I want to update Prospect Pool in opportunity in Late Cultivation stage before moving to Solicitation
7	TAPSS-2311	As a Development Officer, I want to update at least one of Gift Theme in opportunity in Late Cultivation stage before moving to Solicitation
8	TAPSS-2312	As a Development Office, I want to create opportunity with only with Identification & Qualification stage
9	TAPSS-2016 (only briefly)	AQ 26: SmartBatch 2.0 soft credits on Batch Item Transaction need to adjust Batch Approval Reports

Decisions

#	Jira #	Decision Summary	Labels Added
D-022	TAPSS-2326	Focus on Household to reflect all the activities form all contacts associated with it. User stories to be reflected to this for further communication and training purpose. Priority = Must Have, T-shirt Size = XS	Training
D-023	TAPSS-2324	Define the business rule for backdating. Adding tracking function in the future may assist with future audit - this will be a separate build. Priority = Must Have, T-shirt Size = XS	Training, BusinessRule
D-024	TAPSS-2331	Business want the consistent acitvity visibility for Contact and Cases as well. UX for activity creation will be 'cut over' from Activity reports and surface Email, Event, Call, Task for Activity Priority = Must Have, T-shirt Size = S	Training
D-025	TAPSS-2117	Business decision to surface this fields for End user but only 'read only' or to be used purely for insights. 3 options are presented: Show 'Read only' substantive acitvity' for development offier Keep track of Substantive Activity' backend and not display to development officer Do not create any additional automation for Substantive Activity but once business rule is defined, get the insights from the reporting	BusinessRule
D-026	TAPSS-1862	Signed-off
D-027	TAPSS-2314	Signed-off
D-028	TAPSS-2311	Signed-off
D-029	TAPSS-2312	Signed-off
D-030	TAPSS-2016	Separately discussed with GA business

...

#	Jira #	Action	Action Owner
A-011	TAPSS-2326	Once Rommel update the user story and acceptance criteria, assign to Laila for review and sign-off	rommel.ngo
A-012	TAPSS-2324	TAP Business confirm the business rule on backdate. We will not change this user story and solution but we highlight that system will provide created date vs backdate for potential report and audit if required. Once Rommel update acceptance criteria, assign to Laila for review and sign-off	john.lardis rommel.ngo
A-013	TAPSS-2331	Rommel to confirm the existing activity visibility for Contact and Cases for consistent record type. Update the user story with acceptance criteria for Contact/ Case and action buttons, assign to Laila for review and sign-off	rommel.ngo
A-014	TAPSS-2117	Park for further development on this until business decision. TAP business to discuss and confirm.	john.lardis

...