Knowledge

ALTER PROCEDURE [TT].[SP_IsManagerOrAdmin]

    @EmployeeNWName NVARCHAR(100) = NULL,

    @CurrentUserNWName NVARCHAR(100) = NULL

AS

BEGIN

    DECLARE @IsManagerOrAdmin BIT = 0;

    -- Only check if both parameters are provided

    IF @EmployeeNWName IS NOT NULL AND @CurrentUserNWName IS NOT NULL

    BEGIN

        SELECT @IsManagerOrAdmin = CASE

            WHEN R.Mgr1stLineNWName = @CurrentUserNWName

              OR R.Mgr2ndLineNWName = @CurrentUserNWName

              OR (A.AdminNWName = @CurrentUserNWName AND A.Active = 1)

            THEN 1

            ELSE 0

        END

        FROM Resource R

        LEFT JOIN Admin A ON A.AdminNWName = @CurrentUserNWName

        WHERE R.EmployeeNWName = @EmployeeNWName;

    END

    -- Return the result

    SELECT @IsManagerOrAdmin AS IsManagerOrAdmin;

END;

During this appraisal cycle, I have made significant efforts to deliver high-quality results and actively pursued opportunities to enhance my skills and career trajectory. Below, I've summarized key achievements, my aspirations for future growth, and a request for continued support from the organization:

• Performance and Recognition: Over the past year, I have consistently delivered performance that exceeded expectations, reflected by receiving ratings of 'Beyond Exceptional'.

• Additional Responsibilities: Proactively assumed additional responsibilities, significantly contributing to the success of our team and broader organizational goals.

• Career Advancement Request: Based on my consistent high performance and contributions, I formally communicated my aspiration for promotion via email. Although internal constraints were shared, I remain hopeful for recognition and advancement within our organization.

• Professional Aspiration and Development: My long-term career goal is to become an Enterprise Architect. To support this objective, I've proactively completed the training required for the AWS Certified Solutions Architect – Associate certification.

• Commitment to Growth: I am deeply committed to continuous professional growth and enhancing my value to the organization.

• Support Request: I sincerely appreciate your ongoing support and guidance in identifying internal opportunities aligned with my career aspirations.

Woekd with team for k2 license renewal

K2 work hours for 

Identity sync service

Style profile

K2 health check

Setup permissions for K2

Worked with ops team to set up load balancer connect in QA for Nintex DB

Change Password for K2_ADGroupManager-s and SQL accounts

Provided suggestions on new identity synch service.

TT - Jim started on 29th July, I developed almost 75% of application because he has no sql background and those stored procedures are complex

Helped Devops team in upgrade k2 4.7 

SharePoint app upgrade

Helped team to deploy k2 p&D shared tips and tricks, best practices.

Participated in May and September team meeting up

Jira and k2 integration

Worked On DR with Ops teams

Added Jira instructions email signature

Helped team to troubleshoot and figure out P&D issues and deployed packages for LPP and CVTF

Meeting with all managers

Presented Idea app

Password changes for sql and service accounts

S

Created SharePoint survey guide fully secured

Idea to add link in signature for Jira ticket submission

Governance with K2 team

Fixed permissions on k2 servers

Did out of cycle k2 and SharePoint post validations for team

Helped out Operations team

GETS/WPS enhancements

K2 SQL and Oracle Connectivity

Support issues

Proactively worked with k2 support and Operations team to repair k2 in all environments and resolved related issues

IT user Audit

For your information along with IT asset Audit SharePoint and Service now synch we have made below changes in PowerShell at high level. These changes will save us lot headache in time.

• Exception handling - Added exception handling in employee and contingent worker PowerShell. In case employee is not active PowerShell will skip the record and continue to process next record.

• Inventory list update - Inventory list will be updated every Friday, in case anything goes wrong we do not need to delete any records from inventory list and start over. We can run PowerShell with corrected inventory report and it will automatically correct all issues.

• User resolution in SharePoint - PowerShell will resolve users in both in audit list and inventory list so no need to manually resolve users with samrtform.

• Logs - While processing each record we are keeping log of it. In case of exception or diagnosis we can analyze logs. Chris liked the idea of having logs for their refence. All logs will get stores in SharePoint logs library

• Function - PowerShell script had sequential code, reorganized code in functions for reusability.

· PowerShell Script Schedule - Script is schedule to run every day at 3:30pm. Script finds ServiceNow report ‘UserAuditPrepopulateForSharepointUpload_04_02_2024’ with report name containing today’s date appended. If report name does not have today’s date, then script will simply fail and not process any record. [Jay G] If there is no file then Script exit with no data to process and send out notification, right?

· Updating Assets - Previously we were doing only initial upload, now script update assets all assets except audit status is ‘Completed’. If asset does not present, then adds that in asset list. If there are any issues, we don’t need to fix them manually as script also updates records every time it gets new report.

· Employee and Contingent worker resolution – if user is not present script skips the record and move on to next. Script itself resolves all users in SharePoint. We don’t need to additionally spend time to resolve users manually and deal with in-active users.

· Logs - While processing report each record is getting logged. In case of exception, we can use logs to find any issue. Log also tracks duplicate asset. Logs are stored in Logs document library - https://portal-dev.vrsn.com/sites/ITA/Logs/Forms/AllItems.aspx. I will encourage you to check logs after script finish running every time for any issues or errors. [Jay G]  Please make sure to send out an email to our collaboration DL with the errors in the log file.

· Reports status – ‘Process Status’ column in reports library will let you know if report has been processed completely, in progress or Not started.

· PowerShell script optimization – All code is added in function for improved reusability and improved readability.

· Added email notifications