How to move automation including script from one project to another without building the script
Hi Team,
We have automations which are having scripts inside while moving those automations from one project to another. the script corrupts and we have to build the new cs class inside and then paste the script to work.
Is there any other way to do instead of rework for building the script.
Regards,
du
AE
Hi @HaniefB4,
It is a hectic issue in which any automation has a broken script block will never get opened. Hopefully Pega has a solution for how to handle such scenario as reusing existing automations and components is key in enterprise scale implementations. That is a point for the community as well if any had the same situation and has a workaround to deal with it.
An alternative would be to implement an automation encapsulating each code script so that if a script reference breaks core automations don't break. However, it would be a hassle task to create an automation for each script considering the enterprise level scale again!
Looking forward for more responses on this interesting topic.
Pegasystems Inc.
US
@AymanAgamy You really shouldn't have scripts inside of an automation. They should be created globally. If you have re-usable functionality, the best way to make a copy of that is to create it in a separate project. The project is then re-usable. There really isn't a good way to copy an automation with a script inside it since that script has to have an ID and that ID must be changed if you are making a copy since it will already be in-use. You'd then need to update that ID within the OS file to point to the new script container.
My suggestion is to create your script container in the global container and then have your automations refer to that. After that, you can copy your automations easily from the Add Project Items wizard (by selecting "Existing Item").
Tata Consultancy Services (TCS)
IN
@ThomasSasnett Even if we copy a global container (having script) from one project to another following Add project items method, .cs file is not getting copied. And when we click on edit script, project is creating a fresh cs file without any methods. I am using V19.1.71 software.
Pegasystems Inc.
US
@HaniefB4A script component actually requires a separate file (the CS file) to be included as well. The process of Adding an existing project item does not include these extra files and they would need to be handled manually. You can manually copy over the CS file and then copy the "Compile" node containing reference to it from the osproj file to actually make a copy of the script. You can open the osproj file in any text editor (like Notepad++ for example) and search for your cs file by name. You'll see a section where it is being included. This needs to be copied if you want to have your global container or automation have access to the script to compile it. This is not really my recommended approach however.
My suggestion would be to add any of your common scripts to a separate project. You can then reference this project from wherever you need access to it. That makes it such that you don't ever need to copy it and maintain multiple copies. You also would not need to alter the osproj file or edit any of the os files (which might potentially corrupt them).
As always though, before you make any changes, always create a backup of your solution directory and any projects it references before you make any changes like this.