ideas
<div> </div>
<p>Idea:</p>
<p><span style="font-size:18.0pt"><span style="font-family:"Sitka Display""><span style="color:#2d428a"><strong>Consolidated Mail for All scenarios for Job and Data pull status </strong></span></span></span></p>
<p><span style="font-size:9.0pt"><span style="font-family:Arial"><span style="color:#3d4442"><strong>BACKGROUND </strong></span></span></span>:</p>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:8.0pt"><span style="font-size:100%"><span style="color:#3e4043"><span style="font-family:Arial">•</span></span></span></span><span style="font-size:8.0pt"><span style="font-family:Arial"><span style="color:#3e4043">Numerous emails are generated for every job, scenario, and country in the event of data errors or any exceptions which flooded the mailboxes of all recipients.</span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:8.0pt"><span style="font-size:100%"><span style="color:#3e4043"><span style="font-family:Arial">•</span></span></span></span><span style="font-size:8.0pt"><span style="font-family:Arial"><span style="color:#3e4043">Due to above scenario it was difficult to locate the exceptional emails and identify the underlying causes of these exceptions on each occasion.</span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:8.0pt"><span style="font-size:100%"><span style="color:#3e4043"><span style="font-family:Arial">•</span></span></span></span><span style="font-size:8.0pt"><span style="font-family:Arial"><span style="color:#3e4043">Consequently, the Support Team is compelled to individually inspect the mailbox in order to address these issues.</span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in">
<p style="text-align:left"><span style="font-size:9.0pt"><span style="font-family:Arial"><span style="color:#3d4442"><strong>IDEA / SOLUTION</strong></span></span></span></p>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:8.0pt"><span style="font-size:100%"><span style="color:#006cb8"><span style="font-family:Wingdings">§</span></span></span></span><span style="font-size:8.0pt"><span style="font-family:Arial"><span style="color:#3e4043">We recommended that the emails be consolidated for the purpose of mailbox organization and to acquire a comprehensive summary in a centralized location.</span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:8.0pt"><span style="font-size:100%"><span style="color:#006cb8"><span style="font-family:Wingdings">§</span></span></span></span><span style="font-size:8.0pt"><span style="font-family:Arial"><span style="color:#3e4043"> As a result, the Support team will only need to access a single email to obtain a thorough overview of the Data pull and job status. </span></span></span></div>
<p style="text-align:left"><span style="font-size:8.0pt"><span style="font-family:Arial"><span style="color:#3e4043">A Consolidated Summary Email will be furnished for each of the Features, Alerts, Thresholds, and Heatmaps pulled in MWB</span></span></span></p>
<p style="text-align:left"> </p>
<p style="text-align:left"><span style="font-size:18.0pt"><span style="font-family:"Sitka Display""><span style="color:#2d428a"><strong>Removed Dependency of Business' Dates Entries by ACF Integration in Markets Product</strong></span></span></span></p>
<p style="text-align:left"><span style="font-size:9.0pt"><span style="font-family:Arial"><span style="color:#3d4442"><strong>BACKGROUND :</strong></span></span></span></p>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:10.0pt"><span style="font-size:100%"><span style="color:#3e4043"><span style="font-family:Arial">•</span></span></span></span><span style="font-size:10.0pt"><span style="font-family:Arial"><span style="color:#3e4043">We need to configure dates for every scenarios in Mongo Database to fetch data from the CUNO DB/ EAP. </span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:10.0pt"><span style="font-size:100%"><span style="color:#3e4043"><span style="font-family:Arial">•</span></span></span></span><span style="font-size:10.0pt"><span style="font-family:Arial"><span style="color:#3e4043">We need to sync business date entries in PROD twice a month because dates for newly onboarded scenarios do not change frequently. </span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:10.0pt"><span style="font-size:100%"><span style="color:#3e4043"><span style="font-family:Arial">•</span></span></span></span><span style="font-size:10.0pt"><span style="font-family:Arial"><span style="color:#3e4043">Consequently, the Support Team is compelled to sync business dates entries between scenarios.</span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"> </div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in">
<p style="text-align:left"><span style="font-size:9.0pt"><span style="font-family:Arial"><span style="color:#3d4442"><strong>IDEA / SOLUTION</strong></span></span></span></p>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:10.0pt"><span style="font-size:100%"><span style="font-family:Arial">•</span></span></span><span style="font-size:10.0pt"><span style="font-family:Arial"><span style="color:#3e4043">Idea was to create BD Codes for Date in ACF to fetch date along with data based on that date.</span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:10.0pt"><span style="font-size:100%"><span style="font-family:Arial">•</span></span></span><span style="font-size:10.0pt"><span style="font-family:Arial"><span style="color:#3e4043">Now, the user only needs to configure one date on the ACF UI, and the product will pull data for all scenarios.</span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"><span style="font-size:10.0pt"><span style="font-size:100%"><span style="font-family:Arial">•</span></span></span><span style="font-size:10.0pt"><span style="font-family:Arial"><span style="color:#3e4043">We no longer need to configure dates for each scenario and no longer need to sync dates between scenarios, saving us approximately 16-24 hours per month.</span></span></span></div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"> </div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in"> </div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in">Enhancement of MWB EAP Component Alert/Notification mail send functionality to resolve the confusion of alert notification between MWB Service and MWB EAP </div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in">Problem:</div>
<div style="margin-bottom:4px; margin-left:18px; text-align:left; text-indent:-.19in">
<div> </div>
<table cellspacing="0" style="border-collapse:collapse; width:296px">
<tbody>
<tr>
<td style="background-color:#ddebf7; border-bottom:none; border-left:none; border-right:none; border-top:none; height:154px; text-align:left; vertical-align:middle; white-space:normal; width:296px"><span style="font-size:15px"><span style="color:black"><span style="font-family:Calibri,sans-serif">Currently all alerts/notifications of MWB EAP Components store in MWB Mongo DB. At regular interval, MWB Service Chron job picks the alerts/notifications from Mongo DB and send via mail sender. This creates confusion to Receiver that the mail is generated by MWB service component. Whereas it was generated by MWB EAP Component. </span></span></span></td>
</tr>
</tbody>
</table>
<p> </p>
<p>Solution:</p>
<div> </div>
<table cellspacing="0" style="border-collapse:collapse; width:415px">
<tbody>
<tr>
<td style="background-color:#ddebf7; border-bottom:none; border-left:none; border-right:none; border-top:none; height:154px; text-align:left; vertical-align:middle; white-space:normal; width:415px"><span style="font-size:15px"><span style="color:black"><span style="font-family:Calibri,sans-serif">Implement a Spark mail connector in MWB EAP Spark Jobs to send Alert/Notification mail related to MWB EAP Component. This will give better clarity to the Receiver about mail alert/Notification. Additionally it will reduce the dependency upon MWB Service.</span></span></span></td>
</tr>
</tbody>
</table>
<p> </p>
<div> </div>
<table cellspacing="0" style="border-collapse:collapse; width:325px">
<tbody>
<tr>
<td style="background-color:#ddebf7; border-bottom:none; border-left:none; border-right:none; border-top:none; height:77px; text-align:left; vertical-align:middle; white-space:normal; width:325px"><span style="font-size:15px"><span style="color:black"><span style="font-family:Calibri,sans-serif">Movements of excel download mappings from Java BE code to Mongo DB.</span></span></span></td>
</tr>
</tbody>
</table>
<p> </p>
<p>Problem:</p>
<div> </div>
<table cellspacing="0" style="border-collapse:collapse; width:296px">
<tbody>
<tr>
<td style="background-color:#ddebf7; border-bottom:none; border-left:none; border-right:none; border-top:none; height:77px; text-align:left; vertical-align:middle; white-space:normal; width:296px">
<p><span style="font-size:15px"><span style="color:black"><span style="font-family:Calibri,sans-serif">Needs to commit Mapping in Code base. So moved from Java Code to Mongo DB. No touch in actual code base as part of Onboarding and Catch up.</span></span></span></p>
</td>
</tr>
</tbody>
</table>
<p> </p>
<p>Solution:</p>
<div> </div>
<table cellspacing="0" style="border-collapse:collapse; width:415px">
<tbody>
<tr>
<td style="background-color:#ddebf7; border-bottom:none; border-left:none; border-right:none; border-top:none; height:77px; text-align:left; vertical-align:middle; white-space:normal; width:415px"><span style="font-size:15px"><span style="color:black"><span style="font-family:Calibri,sans-serif">Created the Collection in Mongo and moved mapping for all Scenarios.</span></span></span></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>