Require Perm Set Key if OwP Object

[K8Sewell]

In a .csv for batch process ingests, if "Open with Permission" is the item's intended visibility the Permission Set Key name needs to be included in the CSV. After the .csv is submitted, the authoritative JSON will also be checked (along with the csv) to see if the user has permission to change or modify the objects in a particular admin set. If the Perm Set Name is not included in the .csv, an error should be thrown in MGMT to let the user know that it needs to be included.

Acceptance:

• [x] Add Permission Set Key Name for Batch Process create an object
• [x] Add check for the authoritative JSON field: itemPermission
• [x] Throw an error in if the Perm Set Key name is not included in the .csv
• [x] Throw an error if the user does not have permission to edit the OwP set
• [x] Ensure that Preservica objects can be set to OWP - moved to ticket #2836

[K8Sewell]

PR is green. Before taking it out of draft I wanted to check on the language for the batch errors. Are the error messages on these screenshots ok? ~ got ok in standup ~

Screenshots

Not in CSV Error

Permission Error

[K8Sewell]

Deployed to Demo with release v2.69.5

[K8Sewell]

Bumping to UAT so able to test with mssa Admin Set

[K8Sewell]

Waiting to deploy to UAT until testing for #2824 is completed.

[K8Sewell]

Deploy is live on UAT for testing

[sshetenhelm]

Confirmed this works! Checked for both key and permissions. Thank you!

Ready to close :)