この一時的回避策では我々の作業が増えてしまいます。
我々のチームとは関係ない人でログインされているリンクがメールに添付されているのか、どうやってポータルサイトのITに説明すればいいのでしょうか？BOTのCodeは我々ではわかりません。
そしてこのメールはBOT側が送っているものでポータルサイト側からくるメッセージではありません。
はっきりとしてRCがわからないまま完了するのは納得できません。
評価
44
翻訳 / 英語
- 2021/05/24 09:17:36に投稿されました
This temporary workaround will require more work on our part.
How do we explain to portal IT that there is a link attached to the email that is being logged in by someone not related with our team?
We don't know the code of the BOT. and this email is sent by the BOT side, not the portal site side.
We are not sasisfied that we complete the process without knowing the RC clearly.
How do we explain to portal IT that there is a link attached to the email that is being logged in by someone not related with our team?
We don't know the code of the BOT. and this email is sent by the BOT side, not the portal site side.
We are not sasisfied that we complete the process without knowing the RC clearly.
![[削除済みユーザ]](https://secure.gravatar.com/avatar/695023b4efd563721d13716b1457bc73.png?d=identicon&mode=crop&r=PG&s=42)
評価
52
翻訳 / 英語
- 2021/05/24 09:21:14に投稿されました
This temporary solution increases our task somehow.
We do not know the code of BOT. Because there is no idea why the link of the email logged in from others without our relationship with our team is, or how we can explain the IT on the portal site.
Also, the email is sent from BOT and not a message from the portal site.
We are not convinced that the completion of the RC is not known firmly.
We do not know the code of BOT. Because there is no idea why the link of the email logged in from others without our relationship with our team is, or how we can explain the IT on the portal site.
Also, the email is sent from BOT and not a message from the portal site.
We are not convinced that the completion of the RC is not known firmly.
