I've made a change to an existing application which has included a new CDT.

If this is a new CDT added to the datastore, existing processes won't be impacted because the CDTs that they were using will not create a new version. We add new entities/CDTs to our datastore frequently without issue. The only time you need to be concerned with running process instances is if you create a new version of a CDT used by that process.

However I would not recommend importing anything on a production environment while users are active in the system, this should always be scheduled for off-hours.

Thanks for the information.

I agree with your comment re: importing to the production environment.


I've been reading the Application Deployment Guidelines in the documentation. I'd be interested to know if there any best practices with any do's and don'ts when it comes to importing a newer version of an already published data store.

Is there any risk to the exsisting processes when adding new columns to an existing CDT?

If you passed a CDT byreference() into a sub-process, then updating that CDT would cause a conflict when the sub-process is called. If not, as long as you are only adding new fields to the CDT it shouldn't cause any issues, but you should be careful that when you use a write-to-datastore with that CDT that you aren't going to be blanking out the data in the new fields if your process isn't using a query rule to pull the CDT first.