Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Language Copy Wizard vs Create & Translate

Avatar

Level 2

I'm trying to understand the difference between the processes for the Language Copy Wizard and the Create & Translate process under References. They appear to go through the same workflow, but the metadata for Language Copy Wizard has several options that are not passed through with Create & Translate, specifically srcPathList and languageList. The only place I'm seeing any reference to the language(s) selected for the Create & Translate process is in the Workflow Title as 

Translation of "PATH/TO/PAGE" using new project "TITLE" in "LANGUAGE".
 
We are having issues with experience fragment paths not updating when translation is started using the Create & Translate option. A previous developer had written a process step which was added to the workflow to pick up the srcPathList and languageList options from the workflow metadata, but as stated, those don't exist for Create & Translate but do for the Language Copy Wizard. The wizard form is more robust with more options, but I don't understand why the only location for the form selections from Create & Translate is in the workflow title. 
1 Accepted Solution

Avatar

Correct answer by
Level 2

I was able to access the language value from the Create & Translate workflow when getting the metadata from the workflow rather than the workflow data. 

 

item.getWorkflow().getMetaDataMap() does pass in the language property while 
item.getWorkflowData().getMetaDataMap() does not.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 2

I was able to access the language value from the Create & Translate workflow when getting the metadata from the workflow rather than the workflow data. 

 

item.getWorkflow().getMetaDataMap() does pass in the language property while 
item.getWorkflowData().getMetaDataMap() does not.