Cloud Services Catalog: Known Issues and Workarounds1. Workspace "sa11111111_123412341234" already exists: unexpected operator When requesting a stack choosing "Use Existing Workspace" as true and selecting an existing workspace from the list catalog order might fail with error which looks like Workspace "sa11111111_123412341234" already exists: unexpected operator. This happens when the VM hosting the Terraform CLI has particular linux flavors like Ubuntu. Resolution: The cloud script that runs Terraform CLI commands in the bash on terraform provider VM might run into issues with certain linux flavours. To fix this, go to Cloud Admin Portal and navigate to Design > Cloud Scripts and switch to Cloud Script Templates Tab. Open the script named "TerraformApply" and change the only occurance to double equals operator ("==") to single equals ("="). The line should now look like "if [ "$tf_workspace_exist" = "$tf_new_workspace_response" ];". This command will work with all Linux flavours. 2. Quota Configuration in CSC The behavior of quotas in the Cloud Service Console (CSC) differs from that of the Cloud User Portal as the quota component is not added to the current CSC UI. But if the quota configurations are set and quota is exceeded it will generate actions based on whether the out of box Quota approval policy is active or not. 3. Service Catalog Item column is empty in Stacks table - My Stacks page for a User Resolution: Add Permissions to the needed Catalogs using the Permissions module in Cloud Admin Portal. You can follow the documentation - Permissions management for Cloud Governance roles [OR] follow the steps laid out below. The following steps needs to be performed by Root administrator (User who has role sn_cmp.cmp_root_admin) [OR] System Administrator. Navigate to All > Cloud Admin Portal in the platform.Click Permission under Govern from the left side navigation options and click New button 3. Add permission to Group the user is part of & Submit. Target Type: Cloud Catalog ItemAll Entities: Check if need permission for all Catalogs. Uncheck and then select specific catalog in Target Entity field if permission is needed for only one specific catalogGroup: Select group which the user is part ofPermission: Read (*read is minimum level permission) 4. Now check the table and see the Service Catalog Item column is not empty. 4. Some of the Service Request Item & Request columns are empty in Stacks table - My Stacks page for Group Admin. Request Items & Requests are specific to user Expected behaviour - No Solution: So even though the Group Admin can see the Stacks assigned to all the members in the group he is part of, he will not be able to access Requests of his group members. Hence he will not be able to see those columns which are hidden by ACL constraints. 5. Images/Icons are not showing for Catalog & Stacks In CSC Portal Home Page In Stack Details Page While ordering the catalog Resolution: The Images/Icons of a Catalog item are part of the Catalog Item table. If user has access to Catalog item then he has access to the fields inside the catalog item in-turn he has access to the Image/Icon of the Catalog. Hence the Solutions is same as the one suggested in the one of the above stated issues - 4. Service Catalog Item column is empty in Stacks table - My Stacks page for a User. After adding permission, You can see the issue is resolved in all places 6. Search results are not showing properly for CSC Catalog items - After enabling AI Search Resolution: To resolve the above issue, navigate to Catalog Item Table - Indexed Source (*direct link given below for the record) and add entry - sn_cmp_bp_cat_item to the list Child Tables - Related list (as highlighted below). https://<INSTANCE_NAME>service-now.com/ais_datasource.do?sys_id=4d1c4185772300102d71af61681061f0 7. Error Message "Read operation on table 'sn_cd_content_visibility' from scope 'Cloud Services Catalog' was denied" on Employee Center. This error message is shown because of the Cross-Scope privilege being requested from Cloud Services Catalog to Content Publishing (com.sn_content_delivery). Resolution: To resolve the issue, navigate to Restricted Caller Access Privileges table (sys_restricted_caller_access). Filter the records with Source Scope = Cloud Services Catalog and Target Scope = Content Publishing. You can see Read operation in Requested state. Open the record and modify State from Requested to Allowed and save it. Now refresh the CSC page on employee center.You will now see another error message "ErrorExecute operation on script include 'cd_ContentDelivery' from scope 'Cloud Services Catalog' was denied."Navigate back to Restricted Caller Access Privileges table (sys_restricted_caller_access) and refresh it. You will now see another record added for Execute API Operation in Requested state. Open the Execute API record and modify State from Requested to Allowed and save it.Refresh CSC page on employee center. You will not see any error message.