Reject Translation function doesn't work in Translation Connector | Community
Skip to main content
Level 2
October 17, 2018
Solved

Reject Translation function doesn't work in Translation Connector

  • October 17, 2018
  • 14 replies
  • 7031 views

Hello every experts:

I am using bootstrap connector to test Pseudo Translation functionality. If I totally have 7 pages need to be translated, 6 of them are approved translation, 1 of them is rejected, however I still can see the page is still be translated even though I reject this page in Translation Job. I also checked the JS code of accepttranslation.js and rejecttranslation.js are pretty similiar, so I assume reject translation functions is the same as accept translation which means reject translation doesn't work.

I also tested Microsoft Translation Connector, the behavior is the same.

So does anyone know why reject translation doesn't work? Is this the AEM bug and any solutions to resolve this problem?

Please refer to attachment for more detail.

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 Ankur_Sial

Hi,

Reject functionality would initiate update translations, if supported by translation partner. Once a user rejects translation objects, translation partner will be notified with the same. If you are working with a partner, please request your translation partner regarding the support for reject workflow. If you are building your own connector or a partner, this process is initiated via updateTranslationObjectState[1].

Also, as this needs reading comments and updating translations accordingly, it is not supported by Machine Translation only frameworks like Microsoft.

Reject status is an indication that the content needs update. The content would not be reverted to source language.

[1] https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/javadoc/com/adobe/granite/translation/api/TranslationService.html#updateTranslationObjectState-java.lang.String-com.adobe.granite.translation.api.TranslationObject-com.adobe.granite.translation.api.TranslationState-

14 replies

Level 2
October 24, 2018

Thank you smacdonald2008​ for your reply. BTW: Can you let me know where I can find the source code of Accpet Translation and Reject Translation step?

Please check screenshot if I find the right one?

One more question: If I want to have RejectTranslation event integrate with 3rd party Translation provider, how should I do this ? As I know Accept/Reject translation is AEM OOTB function, not sure how to call out external application?

Ankur_SialAccepted solution
Level 2
October 24, 2018

Hi,

Reject functionality would initiate update translations, if supported by translation partner. Once a user rejects translation objects, translation partner will be notified with the same. If you are working with a partner, please request your translation partner regarding the support for reject workflow. If you are building your own connector or a partner, this process is initiated via updateTranslationObjectState[1].

Also, as this needs reading comments and updating translations accordingly, it is not supported by Machine Translation only frameworks like Microsoft.

Reject status is an indication that the content needs update. The content would not be reverted to source language.

[1] https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/javadoc/com/adobe/granite/translation/api/TranslationService.html#updateTranslationObjectState-java.lang.String-com.adobe.granite.translation.api.TranslationObject-com.adobe.granite.translation.api.TranslationState-

Level 2
October 24, 2018

Hi Ankur,

Thank you for your reply, you means reject translation doesn't supported by Machine Translation? Only support by Human Translation? If I have to use Machine Transaltion, how can I customize reject translation code to co-operate with 3rd Translation Provider? Do you have any ideas?

Level 2
October 29, 2018

Hi @Ankur Sial,

I think I get the inspiration from you comment about "If you are building your own connector or a partner, this process is initiated via updateTranslationObjectState[1]" which means any status changed for TO will trigger the updateTranslationObjectState method, this helped me a lot, as I can write my custom "Accept" or "Reject" script in this method to communicate with TMS.

So I will mark your answer as the correct answer. Thank you again.