@chaitraA8609 , that uses Pega Robot Runtime. The bare minimum you need to get it to work is install Pega Robot Runtime in the same desktop you open the browser to access the Pega Customer Services application. You need to configure Pega Robot Runtime with attended RPA also know as RDA.
To enable the integration between Pega Customer Services and Pega Robot Runtime you need to enable the local REST service in the runtime like this <LocalApiService enabled="true" SSL="true" port="9443" allowedOrigins="*" JWTSecurity="false" PegaServerURL="https://MyPegaServer.com/RobotMgr/prweb" /> In this case I'm using SSL so you need to enable RDA when installing the runtime so the process installs a local certificate to support this. If you don't require SSL just set it to false.
In Pega Platform you need to set the DSS pegarobotics/runtime/DesktopRoboticsURL to the URL in your local runtime i.e.: http://localhost:9443 or leave as default which will use the localruntime domain in the certificate installed.
If you're not planning to use a robotic solution you need to configure the runtime to allow that. Update RuntimeConfig.xml setting <add key="AllowRunWithNoPackage" value="true" />
With this running you should be able to configure your workspace from Pega CS and setup new apps to work with SMD.
SMD is OOTB you don't need to add any new activities, nor update flow actions or to create any automations. You need to add the SMD component to the global container if you want to use pre-defined adapters only. If you use pre-defined adapters you need also to mark the adapters for SMD (this is an option in the adapter properties).
The first step would be to test that the components integrate even without pre-defined adapters. To do this you should refer to my previous note and enable the integration between Platform and Runtime. Did you manage to do this?
and upon clicking start my day button i m getting this
Unable to invoke robotic automation from this screen. The automation service is either unavailable or this system is not authorized to execute automations. You have the option of either quitting or continuing with your work flow.
@chaitraA8609 , it looks like either the local REST service in Runtime is not running or the CORS policy is blocking your request. Did you check the service is running? you can do that using the URL I indicated before. You can check the CORS errors using the browser's developer tools.