Deploy

1. Change the following resource in mta.yaml to reflect your subdomain in the URL

- name: workzone_timeout-destination
    type: org.cloudfoundry.managed-service
    parameters:
      config:
        init_data:
          subaccount:
            destinations:
              - Authentication: NoAuthentication
                Name: workzone_timeout-html5-repo-rt
                ProxyType: Internet
                Type: HTTP
                URL: https://<<Subaccount Subdomain>>.launchpad.${default-domain}
                CEP.HTML5contentprovider: true
            existing_destinations_policy: update
      service: destination
      service-plan: lite
    requires:
      - name: srv-api

2. mbt build

3. cf deploy mta_archives/workzone_timeout_1.0.0.mtar

4. Create new new Content Provider in WorkZone

   • Use "workzone_timeout-cdm" as Design-Time Destination
   • Use "workzone_timeout-html5-repo-rt" as Runtime Destination

5. Create a new WorkZone site in the Site Directory

6. In the Site Settings - Role Assignments, assign the Role with the ID "~timeout_issue_DEFAULT"

7. Assign the equally named role-collection to your user in the SAP BTP Cockpit

8. CAP endpoints not secured (mocked auth) - Admin role in xs-security not required

9. Open the new WorkZone Site and start the available app

10. Trigger the Timeout Action and insert 10000 into the popup (errors from 8secs)

11. You should be facing a 504 error

Fix the error

1. Add a timeout property to the following mta.yaml destination

- name: workzone_timeout-app-deployer
    type: com.sap.application.content
    path: gen
    requires:
      - name: srv-api
      - name: workzone_timeout-auth
      - name: workzone_timeout-html5-repo-host
        parameters:
          content-target: true
    parameters:
      config:
        destinations:
          - forwardAuthToken: true
            name: srv-api
            url: ~{srv-api/srv-url}
            timeout: 60000

2. Redeploy

3. Sync the Content Provider in the Content Channels in Work Zone