Cognite Data Fusion: Allow Update of Name and External Id of Transformation From New UX

@Sunil Krishnamoorthy fyi

Hi @Ben Brandt that change was intentional in the new UI. Users can run a transformation using its externalId via the API, SDK and CLI. In the past some user updated the externalIds on the UI which caused Transformations triggered by the SDK and CLI using the externalId fail. 

https://docs.cognite.com/api/v1/#tag/Transformations/operation/runTransformation

@Ben Brandt  ( My bad, please ignore my previous comments - I confused myself with another jira ticket we have in the backlog related to renaming of transformations)

So you can update the name and external id of a transformation in the new UI as shown in the image above. In the old UI we allowed updating name and external id of a scheduled Transformations as well but we don’t allow that in the new UI. During the design of the new UI we observed that scheduled Transformations are often deployed in controlled environments (production/staging) using CLI/SDK and allowing changes to these Transformations in the UI created out of sync issues with the code/script used for deploying them.  

OK.  In the new UX, when you click “Duplicate”  it auto-names the new Transformation as {old name} Copy and generates a random external Id. Having to navigate to another place to change these feels a little awkward.