Workspace Builder: Playbook isn't added when you add it to a workspace in App Engine StudioIssue After the Utah Store 1 release, you can't add a playbook to the workspace using Workspace Builder in App Engine Studio (AES). When you select Add a playbook in the Record details, you see a success message but the playbook isn't added to the record. ReleaseApp version: 23.0.1CauseAES doesn't read the Playbook component's sys_id from the sys_ux_macroponent table for you because of an ACL restriction.ResolutionSuggested Workaround: Log in as a System administrator into the affected instance.Navigate to App Engine Studio.Open the app that has a workspace where you want the playbook. Open the workspace by selecting Edit. In Workspace Builder, select Record pages, and then select the record page with the playbook. On the Record page, select Open in UI Builder. Select the Main Tab in the left side panel, and in the Tabs section of the right panel, select the configure icon for the playbook. Select Delete. In the right panel after the deletion, select + Add for the tab. On the modal, select Start from an empty container, and then select Next. Enter a value for the Tab label, and then select Create. On the left panel, select Add component. On the modal, enter Playbook, and then select the Playbook component. Select the newly added component in the right panel, select the Config tab, and enter the following field values as data using the Bind data option: Specify the Parent table as @context.props.table.Specify the Parent Sys ID as @context.props.sysId.Specify the User session as @context.session.user. Select Save.Return to the Workspace Builder tab within AES and refresh the browser.In Workspace Builder, select the record page and view the record details to confirm that the Playbook has been added. Note: There should be only one Playbook tab in UI Builder. If you find more than one tab for Playbook under Tabs in right panel, delete the extra Playbook tabs as described in steps 7 and 8.Related LinksSeen In: App version: 23.0.1 Related Problem: PRB1628077 Fix In: App version: 23.1.x