Timeline for How we can add translation job metadata through customization or TMPlugin code?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 19, 2017 at 14:01 | comment | added | Alvin Reyes | +1 to Lars' points that Tridion is aware of when a job completes and job metadata isn't needed. However you handle the automation, the Event System is a better approach than TM plugin (deprecated since Web 8). Typical places for where to store emails would be user description or AppData. | |
| Nov 18, 2017 at 7:41 | comment | added | Lars Møllebjerg | Since the TMS system does not know when a Tridion job completes without a lot of extra code I do not think this is a good idea. Please check this is not an X-Y problem: What is the real business requirement? I doubt it is "emails must be send from TMS", it is more likely that the requirement is to receive emails in certain cases (job completion/fail, etc). Once you update your question with the business (not technical) requirements, we can help finding the best technical solution. | |
| Nov 17, 2017 at 21:04 | comment | added | Vivek | We want to send translation job metadata to TMS system. We want to do it through code. We have requirement to get email notification from TMS system so we want to send email id's as part of translation job metadata. We don't want Author to put their email id while sending job so we want to automate this. | |
| Nov 17, 2017 at 6:17 | history | answered | Lars Møllebjerg | CC BY-SA 3.0 |