@GayathriK9873 ,

The need to deploy the Built-On application from Development to higher environments will depend on if the Robot Manager application is already installed in those higher environments. You would have manually installed the Robot Manager component available from the Pega Marketplace to your development system. Some client prefer to do this in all environments manually while others prefer to use their automated deployment tools to do it automatically from Development, though the latter does create an extra level of complexity. So to answer your question regarding deployment of the Built-On Robot Manager, if the application already exists in all your higher environments then there is no need to package it for deployment. Just ensure any configurations / changes made to support your robots are included in the package you create for your Case Management application.

What you see in the Robot Manager Portal is for managing the assignment of your automation packages. As you move your automation package through your path to production you should update the assignment of these packages manually in each environment and keep them in sync. Of course not all automation packages will make it as far as production or staging due to bug fixing and adding additional features before a production go-live. With this in mind I would recommend creating a Retired stage in the Robot Manager Portal to store all your automations that are no longer being developed or have been replaced.