Afect of changing "Internal.Name" on the way.

[#1]

Hello.

This may be a strange question.

I'm holding my head now.

The workflow cannot be executed, or workflow is stoped, and many error.

Shortly before that, a colleague was changing the workflow's "internal.Name".

Does this affect Work Flow?

Thanks.

[uz2020 · Accepted solution]

Hi @uz2020 - the simple answer is not usually

It can affect things like calling workflows, scripts or any other external references (API, etc) that use the workflow internalName to locate the workflow within the system, otherwise it shouldn't affect much within the workflow itself.

Thanks

Darren

[uz2020 · Accepted solution]

@Darren_Bowers Thank you for your quick reply. Do the affected external references include databases and lists? Thanks.

[Darren_Bowers · Accepted solution]

Every set up can be different so its hard to say for sure. For example, if you have a database entry that links internalName of your workflows to some other identifier then that link would no longer work. However, all Adobe database internal references will remain intact if you just change the internalName. Cheers Darren

[uz2020 · Accepted solution]

@Darren_Bowers Thank you for your reply. In that case, it seems that there is no affect other than the script ... By the way, Does it affect the AC cache? Sometimes when I replaced a list, it didn't switch from the previous list. I'm sorry many times, Thanks.

[Darren_Bowers · Accepted solution]

@uz2020 if your script uses the workflow internalName to reference something by a literal string then, yes, it would affect it. I am not sure what the AC cache is when referring to a list. Thanks Darren

[uz2020 · Accepted solution]

@Darren_Bowers Thank you for your reply. There seems to be some other cause. Let's take a closer look. Many times Thank you.