Greetings customers, partners and friends. Some updates, new features and other goodies for this months update of Orchestry. Please note that this update will be automatically applied and requires no action on your side.
Bug Fixes
- Inability to add an existing site to the Workspace Directory has been fixed
- Orchestry could get into a state whereby you have a metadata value that is marked as not required but Orchestry still thinks it is required. This will no longer occur.
- Improved handling of M365 tenants that error when trying to set Group and SharePoint setting values.
Improvements
- If you add a Microsoft Lists Tab to your template but it is not configured Orchestry will now copy it over
- If a provisioning job fails you will be able to see the log of the job. Previously no log file was generated.
- Similar sites functionality now returns a much richer array of sites and what search thinks are duplicates are no longer being removed
- Improved support for when trying to provision Groups whose name already exists. Orchestry now does a bunch of checks to ensure that Groups, URL's and also mailbox ID's are not duplicated
New Features
Limit who can request Workspaces
Orchestry now provides a blanket ability to control who can request Workspaces. Previously this was done at a template level but now this can be applied to an Active Directory Group.
In Settings -> Accounts there is a new field that allows you to limit who can request Workspaces. By default all users will still be able to request Workspaces but this value can be used to limit groups of users quickly and easily.
Send Notifications As a Group/Shared Mailbox
Instead of using an account you can now set up Orchestry to send out email notifications as a Group or Shared Mailbox which is super useful. Just go to Settings -> Notifications to find out more.
Rejection Comment Now Required
Comments are now required for rejections to ensure that you capture this important information:
