Afect of changing "Internal.Name" on the way. | Community
Skip to main content
U
uz2020
Level 2
February 18, 2021
Solved

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

  • February 18, 2021
  • 1 reply
  • 1854 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Darren_Bowers

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

 

1 reply

Darren_Bowers
Darren_BowersAccepted solution
Level 9
February 18, 2021

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

 

Darren_Bowers
Darren_Bowers
Level 9
February 18, 2021
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
Terms & ConditionsAccessibility statement

Loading footer...