Kuali Cloud Internal test 1-Access Security

Person

-Review Person function layout, tabs, drop down menu

-Search old, new users, each criteria: Principal Name, Principle Id, Entity ID, First Name, Last Name, Employee ID, with and without using wild card *, check sort result ascending and descending

Note: per Brett, we don't use Delegate
-Add permissions including affiliations, groups, roles, dates. 

-Update permissions including affiliations,groups, roles, dates. 

-Remove permissions including groups, roles, dates. 

-Adhoc FYI to a person

-Test Submit, Save, Blanket Approve, Close, Cancel 

-Tested several access requests from web access queue and all processed successfully.

I noticed that if you save the document before entering a value in the required fields, you get a stack trace. Creating Jira.

-Review Group function layout, tabs, drop down menu

-Search Group Criteria: Group Id, Group Namespace, Group Name, Group Description, Group Type, Active, Inactive, All, with and without using wild card *, check sort result ascending and descending

-Add new group including dates.

• assign users to the new group.
• assign the new group to a role.
• if not sure how to do the above, look at the year end drop down groups like 10491-YE Accounting (Year End Accounting Group for Post back).
  
  -Update group including descriptions, dates. 

-Remove group, users, dates. 

-Adhoc FYI to a person

-Tested several access requests from web access queue and all processed successfully.

-Test Submit, Save, Blanket Approve, Close, Cancel 

Y

4/25/23

-Review Role function layout, tabs, drop down menu

-Search Role Criteria: Group Id, Group Namespace, Group Name, Group Description, Group Type, Active, Inactive, All, with and without using wild card *, check sort result ascending and descending

-Add new group including dates.

• assign users to the new group.
• assign the new group to a role.
• if not sure how to do the above, look at the year end drop down groups like 10491-YE Accounting (Year End Accounting Group for Post back).
  
  -Update group including descriptions, dates. 

-Remove group, users, dates. 

-Adhoc FYI to a person

-Tested several access requests from web access queue and all processed successfully.

-Test Submit, Save, Blanket Approve, Close, Cancel 

3/17/23

Search Permission - Pass

Created new permission - Pass

View created persmission edoc - Failed 3/20/2023, Brett created a KualiCo Jira ticket, same behavior in PRD.

FINUCONN-392 (resolved)

Yes 3/20/2023

Yes 3/20/2023

No 3/21/2023

Y

4/25/23

Attribute

Y

4/26/23

submitted a copy, went to exception.  entered Jira FINUCONN-447.

8/9/23:  retested copy function, using Account again.  worked successfully and went to final status.  Jira should still be reviewed by I'm flagging this as complete for now.

FINUCONN-447 (closed) this is a base bug, replaced by FINP-9869 (now closed)

Set up a new model for a security group.

-Added a new model strictly for History 1286.  Created a new security group for the model.  used dfm04001 to grant role 54 and group 11185.  When searching for General Ledger entries for other non History accounts, user receives message: One or more balance records have been removed from search results due to access security restrictions.  Using specific History accounts, user can view GL transactions.

y

4/26/23

Tested search criteria. Able to edit and copy.

Tested search criteria. Able to edit and copy.