GitHub repository

[bhimavarapumurali]

using System; using System.Net.Http; using System.Net.Http.Headers; using System.Threading.Tasks; using Newtonsoft.Json.Linq;

class Program { // Configuration private const string OWNER = "your_owner"; // Replace with your repository owner private const string REPO = "your_repo"; // Replace with your repository name private const string TOKEN = "your_github_token"; // Replace with your GitHub token private const string SINCE_DATE = "YYYY-MM-DDTHH:MM:SSZ"; // Replace with your desired date (ISO 8601 format)

static async Task Main(string[] args)
{
    try
    {
        // Fetch pull requests updated since the specified date
        var pullRequests = await GetPullRequests(SINCE_DATE);

        // Initialize total count of modified files
        int totalFilesModified = 0;

        // Iterate over each pull request and count modified files
        foreach (var pr in pullRequests)
        {
            int prNumber = pr.Value<int>("number");
            int fileCount = await CountFilesModified(prNumber);
            totalFilesModified += fileCount;
            Console.WriteLine($"PR #{prNumber} modified {fileCount} files.");
        }

        Console.WriteLine($"Total files modified in the specified period: {totalFilesModified}");
    }
    catch (Exception ex)
    {
        Console.WriteLine($"An error occurred: {ex.Message}");
    }
}

static async Task<JArray> GetPullRequests(string since)
{
    using (var client = new HttpClient())
    {
        client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("token", TOKEN);
        var url = $"https://api.github.com/repos/{OWNER}/{REPO}/pulls?state=all&since={since}";
        client.DefaultRequestHeaders.UserAgent.TryParseAdd("request");

        var response = await client.GetAsync(url);
        response.EnsureSuccessStatusCode();
        var content = await response.Content.ReadAsStringAsync();
        return JArray.Parse(content);
    }
}

static async Task<int> CountFilesModified(int prNumber)
{
    using (var client = new HttpClient())
    {
        client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("token", TOKEN);
        var url = $"https://api.github.com/repos/{OWNER}/{REPO}/pulls/{prNumber}/files";
        client.DefaultRequestHeaders.UserAgent.TryParseAdd("request");

        var response = await client.GetAsync(url);
        response.EnsureSuccessStatusCode();
        var content = await response.Content.ReadAsStringAsync();
        var files = JArray.Parse(content);
        return files.Count;
    }
}

}

[bhimavarapumurali]

Here’s a revised version of your accomplishments and improvements for the month:

• Bootstrap Upgrade Validation: Completed a successful upgrade of Bootstrap for the application, followed by validation of all components under the app management module to ensure stability and prevent any breaks.

• .NET 8 Upgrade: Upgraded our assigned batch processors, including AD-Sync and Attachment Processor, to .NET 8, resolving all existing vulnerabilities in the process.

• Regression Testing: Executed a comprehensive regression suite on all components to confirm no issues were introduced after the build pack upgrade.

• Manual Testing: Performed thorough manual testing on components not covered by the regression suite to ensure the integrity and functionality of the system.

This summary reflects both the upgrades and the testing efforts to ensure system stability after significant changes.

[bhimavarapumurali]

She identifies the least possible scenario in analysis or spike stories, contributed to EF Core-related changes, and proactively suggests new scenarios during functional story validation.

[bhimavarapumurali]

Certainly! Here’s a more detailed summary of the research analyst’s responsibilities based on the content from the images. I'll break it down into key tasks, actions, and the processes involved in the day-to-day operations:

Detailed Summary of Research Analyst Responsibilities:

---

1. Case and Allegation Review:

The research analyst is responsible for reviewing all cases and allegations. This involves:

• Initial Allegation Review:

  • All allegations related to the reported party are set to "Yes" upon initial review.
  • If the research team finds that an allegation does not meet the necessary criteria, it must be changed from "Yes" to "No."
  • When changing an allegation to "No," the research analyst must provide a clear explanation in the “Rationale” field for the decision.

• Validation Process for Changed Allegations:

  • If any allegations are changed from "Yes" to "No," a review using the Allegation Decision Matrix-Exhibit is required.
  • This step ensures that any changes made are justified and documented according to internal policies.

---

2. Case Routing and Handling:

After the initial review of the allegations, the analyst takes further actions based on the status of the allegations:

• Referral to Management or Business Group:

  • If any allegations remain set to "Yes," the case is escalated and referred to the appropriate business manager or group for additional handling.
  • These cases often involve significant misconduct or performance concerns, requiring further assessment.

• Handling Significant Events:

  • The research team determines whether the case involves a significant event that may have a broader impact on the business or customers.
  • If a significant event is identified, the research team follows specialized procedures outlined in the Significant Events section of the documentation.

• Immediate Referral to Investigations:

  • In cases where immediate action is required (e.g., high-risk events involving potential harm to customers or employees), the research analyst refers the case directly to an investigations team.
  • The case is then routed according to the Allegation Routing Table-Exhibit to the appropriate investigations team based on the type of allegation.

• Sales Practices Risk Assessment:

  • The research analyst may need to complete a risk indicator assessment for cases involving sales practices. Allegations involving sales practices are marked as "Yes" if they meet the criteria outlined in the Sales Practices Misconduct-Exhibit.

---

3. Research and Documentation:

A key responsibility of the research analyst is to conduct thorough research and document findings:

• Timely Completion of Research:

  • All research actions must be completed within 30 business days to maintain compliance with business procedures.

• Comprehensive Documentation:

  • The research team must collect and document all relevant information regarding the reported party, allegations, and actions taken. This includes:
    • Details about the reported party.
    • A clear and concise rationale for whether a referral is required to an investigation team.
    • If no referral is made, a reason for not pursuing the case further must be provided.

• Violations Identification:

  • The research analyst is responsible for identifying any violations of internal policies or procedures.
  • Document these violations using the Policy and Procedure Task Creation Job Aid and create a Policy Procedure Review (PPR) task in the system (EAP).

---

4. Collaboration and Consultation:

The research analyst collaborates with different teams to ensure comprehensive case management:

• Consult with Subject Matter Experts (SMEs):

  • The analyst may consult with SMEs, particularly for cases requiring specialized knowledge or legal input.
  • In such cases, the actions and outcomes of the consultation must be documented in the EAP system.

• Legal Department Involvement:

  • If the research team consults with the Legal Department, a note must be added to the EAP case. The note should detail the consultation, but not include specific legal advice.
  • The analyst documents actions taken as a result of legal input.

---

5. Case Disposition and Closure:

After conducting research and consultations, the research analyst finalizes the case:

• Disposition of Allegations:

  • Depending on the research findings, the analyst decides whether the case should be referred for further investigation or closed.
  • Cases that do not require an investigation but confirm a performance concern are processed according to business procedures.

• Closing the Case:

  • The research process is complete when one of the following occurs:
    • The case is closed.
    • Employee Relations is engaged for consultation.
    • The case is routed to the evaluation stage for final review.

---

6. Handling Different Scenarios:

The research analyst must be able to handle a variety of case outcomes, including:

• Needs Referral to Investigation:

  • The case must be referred to the investigations team if unresolved or requiring further inquiry.
  • Ensure that appropriate indicators, such as the Potential Customer Impact Indicator, are filled in or left blank as needed.

• Does Not Need Referral, but Performance Concern Identified:

  • When a confirmed performance concern is identified, but no investigation is needed, the case is dispositioned based on business procedures.

• Does Not Need Referral or Performance Concern:

  • Cases that do not require referral or further action can be closed, with findings documented.

---

Next Steps: Presentation Outline

Slide 1: Title

• Title: Day-to-Day Responsibilities of a Research Analyst
• Subtitle: A Detailed Overview of Tasks, Processes, and Responsibilities

---

Slide 2: Allegation Review Process

• Set initial status of all allegations to "Yes."
• Change status to "No" with justification and rationale.
• Conduct validation review using the Allegation Decision Matrix.

---

Slide 3: Case Routing and Handling

• Refer cases with "Yes" allegations to business managers.
• Handle significant events or urgent cases through the Investigations team.
• Conduct Sales Practices Risk Assessment when applicable.

---

Slide 4: Research and Documentation

• Complete research actions within 30 business days.
• Document all findings, violations, and actions in the EAP system.
• Provide clear rationale for decisions regarding referrals and case closure.

---

Slide 5: Collaboration and Consultations

• Consult with Subject Matter Experts and Legal teams for complex cases.
• Document consultations and outcomes in the EAP system.

---

Slide 6: Case Disposition and Closure

• Make decisions on referral to investigation or closure based on findings.
• Close cases following proper business procedures, ensuring all documentation is accurate.

---

Slide 7: Scenario-Based Case Handling

• Handle cases based on the need for investigation or performance concerns.
• Follow routing tables and ensure proper case disposition.

---

This presentation will highlight the detailed steps involved in the research analyst's responsibilities, focusing on the investigation, documentation, collaboration, and case closure process.

Let me know if you’d like me to proceed with creating the presentation slides or modify any details!

[bhimavarapumurali]

Got it! Here's the revised version of your speech incorporating the correct terms:

---

Hello, my name is Murali Krishna, and today we will be discussing the Research Life Cycle at the Allegation Management Platform.

First, let's talk about how cases enter the research stage. After the intake process is complete, the intake analyst routes cases to the research stage based on the specific allegations involved. Here, I’m presenting the routing matrix that is used to direct cases to the appropriate research teams.

Let’s go through a few scenarios:

• If the allegation involves the reported party being an employee or an accounting unit based outside the U.S., the case is routed to the ER International department.
• If the allegation concerns harassment, bullying, discrimination, or other misconduct related to employment matters in the U.S. region, it is routed to the Employment Research team.
• For potential violations of Wells Fargo’s advisory compliance policies, internal procedures, or securities regulations, the case is routed to the WFS team.

If the allegation doesn’t fall into any of these categories, the routing is determined by the reported party, their line of business, enterprise function, or the incident date.

• If the reported party is part of Consumer and Small Business Banking (CSBB), the case is routed to the Sales Conduct Oversight Team (SCOT).
• For those involved in Home Lending, the case is directed to the Home Lending Oversight Team (HLCOT).
• If the reported party is part of Commercial Banking or Corporate & Investment Banking (CB/CIB), the case is routed to Wholesale.
• If the reported party is in Consumer and Small Business Banking Operations Customer Service (CSBBO), it is routed to the Contact Center Oversight Team (CCOT).
• If none of the above apply, or if the business group or function is unknown, the case is routed to CM Research.

---

This should now reflect the correct team names and routing details. Let me know if you'd like to tweak anything further!

Here’s a refined version of your extended speech, incorporating more detail and improving clarity:

---

Once a case enters the research stage, the Research Life Cycle begins. In general, research teams collect and review readily available and reasonably accessible information. Their goal is to compile evidence relevant to the allegation, leading to the determination of potential misconduct or other performance concerns. Afterward, they route the case according to established business procedures. These are the key steps involved in the process:

1. Allegation Review Process:
   During the initial review, all allegations related to the reported party are set to "S" (under investigation). If the research team finds that an allegation does not meet the necessary criteria, the status must be changed from "S" to "NO" (not substantiated). When changing an allegation to "NO," the research analyst must provide a clear explanation in the rationale field for the decision.

   There is a validation process for changing an allegation. As part of the task, when an allegation is changed from "S" to "NO," all supporting documentation and justifications must be provided and documented according to the policies. This step is crucial for ensuring transparency and compliance with company guidelines.

2. Initial Analysis and Further Action:
   After the initial review, the research analyst takes further action based on the status of the allegation. For example, they search for EAP (Employee Assistance Program) records to identify any other cases involving the same reported party. If related cases are found within the research team’s EAP visibility, the cases may be linked using the Related Records feature.

   If the allegation remains at "S" after the review, the case is escalated and referred to the appropriate business manager or group for additional handling. Cases that involve significant misconduct or performance concerns often require further assessment. The research team must determine whether the case involves any significant events that could have a broader impact on the business or customers.

   If a significant event is identified, the research team follows specialized policies outlined in the Significant Events documentation. A task is created to document the significant event, and all necessary records are maintained according to policy.

3. Immediate Referral to Investigation:
   In cases that require immediate action—such as high-risk events involving potential harm to customers or employees—the research analyst refers the case directly to the investigation team. When routing the case to investigation, they follow the same routing matrix we discussed earlier to ensure the case is handled by the appropriate team.

4. Sales Practice Risk Assessment:
   If an allegation involves sales practices, and the criteria outlined in the sales practice misconduct policy are met, the allegation is marked as "S." This indicates that the sales practices require further review and potentially more in-depth investigation.

---

This version adds structure and clarity, ensuring that each part of the research process is explained in an organized manner. Let me know if you need further adjustments!

Here’s a refined version of your extended speech for clarity and flow:

---

The key responsibility of a research analyst is to conduct thorough research and document their findings. This research and documentation process is a critical part of the research stage. During documentation, research analysts carry out several important activities:

1. Timely Completion of Research:
   All research actions must be completed within 30 business days to ensure compliance with business procedures.

2. Comprehensive Documentation:
   The research team must gather and document all relevant information related to the reported party, allegations, and actions taken. This includes providing a clear and concise rationale for whether a referral to the investigation team is required.

3. Referral Justification:
   If a referral to the investigation team is made, the reason for not pushing the case further must be clearly documented in the research findings.

4. Violation Identification:
   The research analyst is responsible for identifying any violations of internal policies or procedures. If violations are discovered, they must be documented using the appropriate policy/procedure task.

5. Collaboration and Consultation:
   The research analyst collaborates with different teams to ensure comprehensive case management. However, during the research stage, they do not contact the reported party or their managers, with some exceptions, such as international research teams or Wells Fargo Advisory special surveillance review cases, where contact with the reported party or their manager (or qualified supervisor) may be allowed.

   Additionally, research analysts may consult with subject matter experts (SMEs), particularly for cases requiring specialized knowledge or legal input. The actions or outcomes from these consultations must be documented in the EAP system.

6. Legal Department Involvement:
   If the research team consults with the legal department, a note must be added to the EAPK system. The note should detail the consultation, but must not include specific legal advice. The research analyst should document any actions taken as a result of the legal consultation.

7. Case Dispersion or Closure:
   After completing the research and any necessary consultations, the research analyst finalizes the case. There are two main steps in this process:

   • Dispersion of Allegations:
     Based on the research findings, the analyst decides whether the case should be referred for further investigation or closed. If the case does not require further investigation but confirms a performance concern, it is processed according to standard business procedures.

   • Closing the Case:
     The research process is considered complete when one of the following occurs:

     • The case can be closed.
     • Employee relations are engaged for consultation.
     • The case is referred to the evaluation stage for a final review.

8. Handling Different Scenarios During Case Dispersion:

   • Referral to Investigation:
     If the case requires a referral to the investigation team, the research analyst refers the case, leaving the potential customer impact indicator blank.

   • No Referral, but Performance Concern Identified:
     If the case does not need a referral to investigation but a performance concern is identified, the dispersion of allegations follows standard business procedures.

These are the core activities research analysts undertake during the various stages of the research process.

---

This revision

[bhimavarapumurali]

Problem:
Due to a recent organizational policy change, any GitHub Pull Request (PR) that does not adhere to the defined title standards results in a regular code review (CR) being escalated to an emergency code review (ECR), potentially causing delays in the release process.

Solution:
We developed a tool integrated with GitHub that automatically checks the titles of all PRs to ensure they follow the required standards. The tool generates a report listing any PRs with invalid titles along with their corresponding details, helping to identify and address issues before they escalate to an ECR.

[bhimavarapumurali]

"PR Title Conformance Check Report"

[bhimavarapumurali]

Problem:
Due to a recent organizational policy change, any GitHub Pull Request (PR) that does not adhere to the defined title standards results in a regular code review (CR) being escalated to an emergency code review (ECR), potentially delaying the release process. Additionally, release engineers manually track the list of repositories modified as part of each release, which is time-consuming and prone to errors.

Solution:
We developed a tool integrated with GitHub that automatically checks the titles of all PRs to ensure they follow the required standards. The tool generates a report listing any PRs with invalid titles along with their corresponding details, helping to identify and address issues before they escalate to an ECR. Additionally, the tool automates the tracking of repositories modified as part of each release, eliminating the need for manual checks by release engineers and ensuring a more efficient and accurate release process.

[bhimavarapumurali]

Problem:
Due to a recent organizational policy change, any GitHub Pull Request (PR) that does not adhere to the defined title standards results in a regular code review (CR) being escalated to an emergency code review (ECR), potentially delaying the release process. Additionally, release engineers manually track the list of repositories modified as part of each release, which is time-consuming and prone to errors.

Solution:
We developed a tool integrated with GitHub that automatically checks the titles of all PRs to ensure they follow the required standards. The tool generates a report listing any PRs with invalid titles along with their corresponding details, helping to identify and address issues before they escalate to an ECR. Additionally, the tool automates the tracking of repositories modified as part of each release, eliminating the need for manual checks by release engineers and ensuring a more efficient and accurate release process.

Advantage:
One of the key advantages of this tool is its extensibility; the reporting functionality can be adapted for use across different projects, allowing for consistent enforcement of PR title standards and repository tracking organization-wide.

[bhimavarapumurali]

Here's a revised version of the email based on the provided image:

---

Subject: RE: Output Portal Notification Actions not working in UA T3

Hi S&C Team,

We are currently facing an issue after upgrading to .NET 8 in the Tier 3 environment. Specifically, the method OPAcknowledgementResponse/saveOPNotificationRecipientAck is returning a status of “false.”

Root Cause: Our initial analysis indicates that synchronous API calls are not functioning as expected. The issue seems to be that the call to Pega is not being awaited properly, resulting in incomplete execution.

This same code is working as expected in the Tier 2 environment. Please see the attached screenshots for reference.

Best Regards,
[Your Name]

---

Let me know if you need any further adjustments!