Field Level Security Check

PPM offers security check on mass updates by adding pre-checks to the following scenarios:

  • When you click Mass Update to perform mass updates on selected multiple requests, a security check is performed to verify the selected requests for potential issues that might cause the mass update operation fail. The security check includes the following pre-checks:

    • Status dependencies check: Checks field status dependencies for non-editable fields.

    • Field level security validation: Validates field level security of the selected requests to see if the user has appropriate privileges.

    • Display-only check: Checks for display-only fields.

    With these pre-checks performed, the Request Batch Update page displays the requests for updates accordingly:

    • If one column is not editable for ALL the selected requests, then this column is displayed as read-only and grayed out.

    • If one column is editable for at least one request among the requests that users selected to update, then this column is displayed as editable.

  • When you click Save or Done on the Request Batch Update page, some more applicable pre-checks are performed, such as checking the status of requests whether they are still valid for the mass update.

    If any potential errors exist, for example,

    • The pre-check finds that the Editable option for a request field is set to No for the current status, then update to this field would not be applied.

    • A request contains fields that users do not have authorization to edit, then the request could not be updated.

    Then, warning messages are displayed on the Request Batch Update Confirmation page, listing requests that could not be updated, with a descriptions of the reasons. This pro-active warning message would enable users to decide whether they want to continue or not.

  • Workflow transition check. When you click any workflow actions on Request Batch Update page, some pre-validations are performed, including security check, check request status, and check whether an action is still available for the selected requests. If any potential errors exist, warning messages are displayed on the Request Batch Update Confirmation page for users, listing requests that could not be updated, and a description of the reasons.