﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>New Boundary Support Forum / Prism Deploy &amp; Prism Pack / Feature Requests  / Changes in how to handle Tasks / Latest Posts</title><generator>InstantForum.NET v4.1.3</generator><description>New Boundary Support Forum</description><link>http://nbtnet.newboundary.com/forum/</link><webMaster>support@newboundary.com</webMaster><lastBuildDate>Wed, 08 Feb 2012 16:46:58 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Changes in how to handle Tasks</title><link>http://nbtnet.newboundary.com/forum/Topic1788-11-1.aspx</link><description>The first issue was added to a feature request that we already have and the second two were added as new feature requests.  Thanks for the input.</description><pubDate>Thu, 02 Apr 2009 14:51:42 GMT</pubDate><dc:creator>New Boundary Support</dc:creator></item><item><title>Changes in how to handle Tasks</title><link>http://nbtnet.newboundary.com/forum/Topic1788-11-1.aspx</link><description>I use tasks fairly heavily for everything from distributing new hosts files, installing/upgrading Norton Antivirus, to creating local Security groups. And I think the following changes would increase the flexibility and usability of the tasks function.&lt;/P&gt;&lt;P&gt;1) To me this first one seems like a logical step. I can already assign a group of tasks at once based on the folder they are in, but if I later add a task to that group it doesn't automatically get the assignment of that group(How and what it is applied to.) It would be nice to have the group folder actually handle the assignment and then just check itself for what tasks it should run.&lt;/P&gt;&lt;P&gt;2) When a task is moved into a group folder, create a duplicate of the task that actually resides in the folder instead of just creating a link to the existing task. This way you can use the same task template without creating several virutally identical tasks manually.&lt;/P&gt;&lt;P&gt;3) Ability to set various permissions/default username/password at the task group folder level, where tasks can auto update the information when they are moved under that folder. (I opperate within several nearly distinct AD networks and organize task accordingly.)&lt;/P&gt;&lt;P&gt;The tasks are fairly easy to use as is but I think the above improvements would help organization and tracking a lot. Thanks.</description><pubDate>Thu, 02 Apr 2009 10:54:58 GMT</pubDate><dc:creator>ebrusky</dc:creator></item></channel></rss>
