Scribd
Upload
23 views

Python Requirements

The document outlines three logics to check user access requests, user creations/modifications, and common account creations against data in MyAccess and Helix systems. Logic 1 checks statuses and approvals of user access requests and ensures approvers are in Helix. Logic 2 checks that user creations/modifications are requested in MyAccess before the action date. Logic 3 checks that common account creations in Helix are found as requests in MyAccess with matching dates.

Uploaded by

CyberMoriarty
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
23 views

Python Requirements

The document outlines three logics to check user access requests, user creations/modifications, and common account creations against data in MyAccess and Helix systems. Logic 1 checks statuses and approvals of user access requests and ensures approvers are in Helix. Logic 2 checks that user creations/modifications are requested in MyAccess before the action date. Logic 3 checks that common account creations in Helix are found as requests in MyAccess with matching dates.

Uploaded by

CyberMoriarty
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Create a PEP8 Layout Code for this logic and conditions.

LOGIC 1

Check that the person approving the request in MyAccess is found in the list of business owners and
delegates in Helix.

1. Check the statuses of user access request “[Req]Status”, “execution_status”, project manager
approval “Mngr-WIstate” and business owner approval “Owner-WIstate”.
 If the statuses of the user access request “[Req]Status” is “Incomplete”,
“execution_status’ is “Completed”, project manager approval “Mngr-WIstate” is
“Finished”, business owner approval “Owner-WIstate” is “Finished”, remark would be
“Request is incomplete but has been approved” and result would be “Not Compliant”.
 If the statuses of the user access request “[Req]Status” is “Success”, “execution_status’
is “Completed”, project manager approval “Mngr-WIstate” is “Rejected”, there will be
no exception.
 If “Mngr-WIstate” column is blank, remark would be “Project manager status is blank,
pending data check”.
 If “Owner-WIstate” column is blank, remark would be “Business owner status is blank,
pending data check”.
 If “Mngr-WIstate” and “Owner-WIstate” columns are blank, remark would be “Project
manager and Business owner statuses are blank, pending data check”.
 If statuses of the user access request “[Req]Status” is “Success”, “execution_status” is
“Completed”, project manager approval “Mngr-WIstate” is “Finished”, business owner
approval “Owner-WIstate” is “Finished”, proceed to step 2.
2. Check that Project Manager and Business Owner in My Access are found in Helix IT Asset.
 If project manager in “Mngr-ApprovedBy” in MyAccess is not found in “Project Manager”
column in Helix IT Asset, remark would be “Project manager not found in Helix IT Asset” and
result will be “Not Compliant”.
 If business owner in “Owner-ApprovedBy” column in MyAccess is not found in “Business
Owner” column in Helix IT Asset, remark will be “Business owner approver not found in
Helix IT Asset” and result would be “Not Compliant”.
 If project manager and business owner in “Mngr-ApprovedBy” and “Owner-ApprovedBy”
columns in MyAccess are not found in “Project Manager” and “Business Owner” columns in
Helix IT Asset, remark will be “Project Manager and Business owner approvers are not found
in Helix IT Asset” and result would be “Not Compliant”.
 Else, result is “Compliant”.

LOGIC 2

The first check is that the list of user creation or modification in each application is found in the
list of provisioning requests in MyAccess. The second check is to ensure that the date of approval is
before the date of user creation or modification.

Check 1
1. Check that the list of user creation or modification is found in the list of provisioning
requests in MyAccess.
1.1 If user creation or modification ID is found in MyAccess, proceed to check 2.
o Else, result is “Not Compliant”.

Check 2

 Check if the date of approval is before date of user creation or modification.


o If date of approval is before date of user creation or modification, result is “Compliant”.
o Else, result is “Not Compliant”.

LOGIC 3

Check that the list of common account creations is found in the list of provisioning request from
MyAccess.

1. Check that the list of common account creation IDs is found in the list of provisioning
requests in MyAccess.
 If “Request Number” column in Helix common accounts list is not found in “[Req]
Request ID” column in MyAccess listing, remark is “Common account creation request
ID is not found in MyAccess” and result is “Not Compliant”.
 Else, proceed to next step.

2. Check that the list of common account creation dates in Helix for the respective common
account creation request is found in MyAccess listing.
 If “Submit Date” column in Helix common accounts list for the respective common
account is not found in “[Req] RequestCreationDt” column in MyAccess listing, remark is
“Common account creation request ID is found, but creation date cannot be matched in
MyAccess” and result is “Not Compliant”.

Else, result is “Compliant”.

You might also like