Hi everyone, I have a question regarding the plug in of Set External

The designer of such a process would need to populate some of the data (process instance ID, pv names, etc) automatically, and allow the user to enter the new data on a form with meaningful labels, etc. It would probably be best to have an individual "updater" process model for each process model you wish to allow instance-level updates to be made for (because of PV names); you could then source the instance IDs and perhaps the current data from sources such as process reports. It largely depends on the specific details of your use case and requirements; for instance, the times I've used it have been to do clean-up work in the rare case that process data changes after an instance has ended, but it can be used for more than that.
Also be aware that if you use this to update CDT values, it will not update the value for "outdated" CDTs (i.e. where the instance is using the old version of a CDT).

The designer of such a process would need to populate some of the data (process instance ID, pv names, etc) automatically, and allow the user to enter the new data on a form with meaningful labels, etc. It would probably be best to have an individual "updater" process model for each process model you wish to allow instance-level updates to be made for (because of PV names); you could then source the instance IDs and perhaps the current data from sources such as process reports. It largely depends on the specific details of your use case and requirements; for instance, the times I've used it have been to do clean-up work in the rare case that process data changes after an instance has ended, but it can be used for more than that.
Also be aware that if you use this to update CDT values, it will not update the value for "outdated" CDTs (i.e. where the instance is using the old version of a CDT).