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

Monday, August 29, 2016
"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)


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]

= Setting sample of Communication permission OAuth2.0
== 1. Setting on Slack side ==
※ https://api.slack.com/apps/new
  • Redirect URI(s): https://s.questetra.net/oauth2callback

== 2. Setting on Questetra side (Client) ==
*[Process Model Details] > [OAuth 2.0 Setting]
  • Name: Questetra2Slack
  • Authorization Code Request URL: https://slack.com/oauth/authorize
  • Access Token Request URL: https://slack.com/api/oauth.access
  • Scope: chat:write:bot
  • Consumer Key: ( from https://api.slack.com/apps )
  • Consumer Secret: ( from https://api.slack.com/apps )

<Modeling screen: OpenChat Post setting screen>

&lt;Modeling screen: Slack Post setting screen&gt;

[Data Items list]

[Free Download]
<Similar Models>
<<Related Articles>>

[Japanese Entry (ε’Œζ–‡θ¨˜δΊ‹)]