Workflow Sample: Episode 498: Variations of Data Processing at Automated Step (Part 5)

"Want to share translated document with the team..."

Indeed, "Share by Email" is not so bad. A translated sentences would be shared quickly with the team by a setting to send automatically to Team ML (Mailing List) upon completion of translating. Feedback about mistranslated or brushing up might be obtained.

However, it would not be happy that when a person who has received an email wants to reply, he or she must reply by email. Enterprise Social Networking is the mainstream for in-house information exchange, nowadays.

The Workflow definition below, it is devised to post to [OpenChat], which is an Enterprise Social Networking of Questetra, upon completion of translating. It allows co-workers to Like immediately on a High-quality translation.

[Translation Process-OpenChat Post]

The [OpenChat Post], an Auto-step (Service Task) used in this sample, will become available by feature expansion with [Addon XML] in advance. （v11.1: 2016-09-05）

Different from a [Script Task], which is to write JavaScript all by yourself, you can achieve a mechanism of Auto-posting by simply configuring the following.

Messaging target (Organization type data item)
Header of the Post (Fixed sentence)
Translated sentences to be Posted (String type data item)
Hash value (String type data item)
Number of characters (Numeric type data item)

You need no programming knowledge for this. (And no risk of Script error by your own)

Incidentally...

If you would like "Auto-posting to Slack", you conduct feature expansion to be capable of using an Auto-step (Service Task) of [Slack Post] moreover. (You need to configure setting related with OAuth2 which is a communication permission separately.)

[Translation Process-Slack Post]