Users are unable to create new jobstreams in the AAI (Automic Automation Intelligence) Web UI, and the "+ Add Jobstream" button is missing. This behavior persists even after verifying that permissions are correctly configured for "JobstreamV2" and "Business Area" resources in eEM (embedded Entitlement Manager).
AAI V24.4 introduces a new permission model. If any legacy (older) Jobstream policies remain enabled in eEM, the application ignores the new permission model entirely. Consequently, even if user permissions are correctly set in the new policies, the application does not consult them, and the "+ Add Jobstream" button is not rendered.
To enable the new permission model, all legacy policies must be disabled.
Pre-check Configuration: Before disabling legacy policies, review the resource scoping for the new IC Jobstream policy V2 and IC Business Area Policy. If your organization requires departmental separation (e.g., AWA/AutoSys, DW, APL), ensure these matching resource paths are added to the new policies to prevent unintended access changes.
Disable Legacy Policies: Ensure the following six policies are disabled in eEM:
Execute Migration Script: Use the migration script included with the AAI 24.4 installation to automate the policy transition: ./enableAndDeleteEEMPolicies.sh -h -u EiamAdmin -p -exportPath /tmp/eem Answer "yes" when prompted to confirm the disablement of old policies and the enablement of the new ones.
Restart AAI: The permission model is evaluated at application startup. Restart the AAI service to apply the configuration changes.
Verification Once the service has restarted, log in to the AAI Web UI and verify that the "+ Add Jobstream" button is now visible. Confirm that users can only access the jobstreams permitted by their department-specific policies.