BMC Helix Remedyforce 20.19.01 patch 2 sandbox testing guidelines
BMC Helix Remedyforce 20.19.01 (Winter 19) Patch 2 contains a number of defect fixes to improve the product quality. It also includes improved checks on objects and fields for various user personas such as Staff and Client to further secure the application usage and prevent unwanted access. It is recommended that if you elect to self-upgrade, then first upgrade and test in your sandbox before pushing 20.19.01 Patch 2 to your production instances.
This document provides testing recommendations related to various defect fixes and security enhancements addressed in the BMC Helix Remedyforce 20.19.01 Patch 2 release. Note that these guidelines might not cover all customization or configuration that are specific to your organization. Hence, it is recommended that this document be used as a reference for understanding the possible product areas which might have undergone changes. Partners and customers are expected to not limit their validations to the ones mentioned in this documentation. They should also execute their test suites to ensure all the use cases important to their business continue to work as expected.
For more information on the release details, refer BMC Helix Remedyforce 20.19.01 Patch 2 release notes.
For more information about the testing guidelines, refer the following topics:
Testing guidelines for security enhancements
Improvised checks on the objects and fields for various supported personas have been added into this patch. This will further help in enhancing the application security. There should not be any impact if you are using OOTB (out of the box) permissions for various personas, however, it is recommended that you validate your key use cases related to customization using various personas such as Staff, Client, and Change Manager.
Sample testing scenarios for security enhancements
Perform validations whenever you see any of the following scenarios:
- Any field(s) which were visible earlier on the form but are not visible now.
Reason: Those fields might be missing the Read or Edit field level permissions.
Fix: Grant appropriate permissions to those fields which are missing.
- You receive error message, such as Insufficient permissions on specific field while performing any operation.
Refer to the following screenshots:
Reason: Insufficient object or field level permission.
Fix: Grant appropriate permissions on that object or field to the persona as displayed in the error message.
- If you see any unexpected behavior for any of the feature(s).
Reason: Permissions on the object or fields driving that feature may be missing.
Fix: Basic objects or fields involved for proper functioning of that feature as described in above scenarios. Granting basic permissions might resolve the issue.
Using OOTB (out of the box) permission sets provided for that persona should fix the issue. If the issue persists, please contact the BMC support team.
Testing guidelines based on defect fixes