Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Multiple enhancements have been introduced to fix issues with directly assigned locations. The incorrect success message displayed when removing a location has been corrected, and the error handling for adding an already assigned location has been improved. Now, users are properly notified about location removals and existing assignments. This update addresses usability issues without affecting system functionality.

  • Resolved an issue where the UserPrincipalName (UPN) was not populated during provisioning through RET. Additionally, a CSS bug affecting the Start Date and End Date fields was identified, where the calendar icon was missing, preventing users from easily selecting dates. The only way to load the calendar was to click at the end of the field. This fix addresses both the UPN bug and the CSS issue to ensure proper functionality for Daimler Trucks and unblock the release of the Set Validity feature.

  • A bug fix has been implemented to correct the workflow configuration for Mailboxes. The Configure Eligibility workflow has been updated from the ManageGroupWizard to the ManageMailboxWizard. Additionally, the Configure Eligibility button has been removed from Shared Folders, as it incorrectly pointed to the ManageGroup workflow. This fix ensures that users no longer see the configured eligibility option for shared folders.

  • A fix is applied to correct the class name in the Workflow template to accurately reference BRequestItemFulfillmentTemplate. Without this change, the Business Request Fulfillment Workflow created from the template in Workflow Studio would not compile. This update ensures that all customers using version 212 can compile the workflow without further modifications.

  • A fix has been implemented for the access request policy in the IAM Shop, addressing an issue where the maximum allowed duration was enforced even when the policy was not time-restricted. This UI change ensures that the maximum allowed duration is only applied when the policy is time-restricted. Users can now select any end date for policies that are not subject to time restrictions.

  • Resolved an issue of the PBAC label incorrectly appearing for non-PBAC resource types in the UI. The fix ensures that the PBAC label is only displayed for PBAC resources, eliminating user confusion and improving resource type classification in the UI.

  • The issue where Azure role access duration was not displayed in the IAM Shop has been fixed. Now, when an Azure role is requested with a time duration, users will see this information in the manage access listing.

  • Fixed the issues with submitting valid start and end dates in business requests. Updated the default end date in requestDataEndTime, corrected the invalid date errors, and formatted the updated end date time. Additionally, handled the toggle value and resolved related comments.

...