Use case
Imagine you sit in front of the ITRP inbox. An implementation task has been assigned to you. The specific relevant information rests in the Request’s custom data field because a request template with an UI extension provided the structured input form.
Therefore, you need to click on the Request link of your task, to open the Request in a new tab (cmd + shift + click). The inefficient thing is that you need to work with 2 tabs, you read specific information in one tab and you need to comment in a second tab.
The automator solves this problem with a couple of lines of code
//This package copies "custom_data" from the request
//to all tasks, so that people do not need to click
const PKG_SETTINGS = {
automTaskTemplateID: 139
};
(function main(){
if (task.template.id !== PKG_SETTINGS.automTaskTemplateID) return;
const chg = task.change;
if (chg.requests.length === 0) return;
const req = chg.requests.first();
const reqCustomData = req.custom_data;
for (let t of chg.tasks){
let mergedCustomData = assign({}, reqCustomData, t.custom_data);
update('tasks', t.id, {
custom_data: mergedCustomData;
});
};
})();
Output
The automator package copies all UI extension data to all tasks if a certain Task Template is used. Therefore it works in a generic way. Independent of what you have in your Request UI extension. It always works!
Furthermore you can select what UI data you want to see in specific tasks. Simply put your field selection into the UI Extension and add the extension to your task template.
Now, you instantly know what you need to do, without clicking around. Makes sense, right?
k.konwalin@techwork.at
Like this:
Like Loading...
A couple of months ago, the automator got a new important capability: It can now integrate into applications via SOAP.
