automation-hub
latest
false
- Release Notes
- Getting Started
- Permissions
- Starting as
- Admin Console
- Workspace
- Explore
- Share Idea or Automation
- Dashboards
- My Tasks
- Notifications
- Email Notifications
- Resources
- Process Mining Integration
- Studio Integration
- Task Capture Integration
- Automation Hub - Automation Cloud Integration
- Automation Store
- Additional Resources
January 2024
Automation Hub User Guide
Last updated Nov 11, 2024
January 2024
- Automation Profile > Edit mode: Removing any package from the Execution Assessment table always removed the last one instead of the the required one.
- Automation Profile: Fixed performance issues when opening Cost Benefits Analysis for ideas.
- Admin Console > Platform setup > Idea flow customization > Idea flow settings: The assessment versions picker in the assessment section was blocked by the context dialog.
- Admin Console > Platform setup > Customize assessments: All mandatory file questions became non-mandatory after adding a custom question that requires a file upload.
- Workspace > Automation Pipeline: Export to CSV wasn't downloading all the ideas properly.
- Workspace > Automation Pipeline: No values were shown in the Application Used column for automations that had more than one applications used.
- Workspace > Automation Pipeline: Launch date wasn't updated after manually filling the the Actual & New Estimate table within the Cost Benefit Analysis.
- In some cases Development Type would show different values in the Profile versus Pipeline.
- Transitioning between statuses was throwing an error for certain users with the Process Owner roles assigned.
- The publishing sidebar wasn't showing any sections marked as Visible before publishing to Store even if the visibility condition was marked by default in the Detailed Assessment.
- Users that established a connection to their Azure Active Directory (AAD) account via Automation Cloud didn't have their attributes automatically synced from AAD.
- In certain cases users could be able to see KPI's marked as Sensitive Information.
Important: Erratum - 14 March 2024
Due to a mishap on our side, the above bugfix wasn't listed in the original announcement day (5 January 2024).