Risk Assess Known Issues
Every attempt is being made to ensure the application is free of issues. Periodically, issues arise where an immediate fix is a bit more complicated and more time is needed to ensure that a quality fix is delivered. Following is a list of known issues on our radar.
Last Updated
October 30, 2019
| Issue | Description | Case Number |
|---|---|---|
|
Error on editing orphaned records that are navigated to via the application search bar. |
Issue: If a user-defined object (UDO) is found via search and the UDO's parent object was deleted, then editing and saving the child (orphan) UDO will cause the application to hang. |
Salesforce Case: 00087039, 00087269 Development Ref: 2771 |
|
Program launch error |
Issue: Program fails to launch if the Assignment Defaults are set to a group, and one of the group members has their out-of-office notification (OOO) set to delegate to a group. Workaround: It is recommended that users delegate their OOO to a single user. Once the OOO is changed, the enrollment can be set to Active and the programs relaunched. |
Salesforce Case: 00089852 Development Ref: 2830 |
|
Display name updates in reporting |
Issue: When the reporting display name is changed in the data dictionary, the change is not reflected in reporting. |
--- |
|
Multi-session login error |
Issue: Logging into Risk Assess using the same user ID and password with more than one session open at the same time, whether across browsers or within the same browser is not supported. Workaround: Only use one session at a time. |
--- |
|
Reporting display name error |
Issue: Reporting page occasionally displays the data source names instead of the Display Names when the page loads faster than the data is retrieved. |
Salesforce Case: 00057215 Development Ref: 1618 |