Customer service has not yet been converted to Cosmos UI - Having said that all the flow actions that you created in your main application should render fine inside the Customer Service app - All the formats used in the CosmosSkin are also present in the UI-kit skin (pyEndUSer) which CS inherits from. So you will need to have 2 application stacks: your Main application running on Cosmos UI should include the Theme-Cosmos built on app and your CS app that you be based on the CustomerService app.
Following your response. Is there a way a Cosmos App (as of Pega 8.4.1) can leverage case types (or service cases) from a CS application?
We've trying to do a POC on adding a CS app as a built on application with no luck: we get some strange behavior in the User Portal (like no Settings > Theme) or missing the ability to import case types from the CS app.
To use the CS services case, you need to include the whole CS App stack and it is based on ui-kit - Certainly you are picking up changes from the Perform harnesses and other sections from the CS layer and they are expected to work with ui-kit - it is possible to run such application but first make sure that Theme-Cosmos is at the top of the stack. You will have to withdraw some of the rules (harness / sections) from the CS Layer so that the rules from Theme-Cosmos are used. For the skin, you need to use a skin that inherits from CosmosSkin and not from CSEndUser skin.
Hello, the conversion of the Customer Service portal is being done in phases. In 8.5, the Knowledge Management component was converted to be Cosmos compliant. In 8.6, the plan is to start the conversion of the remaining portal. It's very unlikely that the work will be completed in the 8.6 release. I would not guess as to when the entire conversion will be completed, but it is very highest on the priority list.