<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Modifying the Change Request email text in Windchill</title>
    <link>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107527#M12664</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my experience, ignorable emails become noise and eventually Users start to ignore everything coming from Windchill... well at least the non-core Users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My approach to this would be to look at doing conditional branching of parallel notification robots if/when a particular group of recipients needs to know, and removing the notification for the Assignment itself (or leaving in place for those that need to take action).&amp;nbsp; Do all the impacted groups need to take action (i.e. complete the assignment), or dot they just need to be informed?&amp;nbsp; You could do the same type of conditional branching of parallel assignments with different participant pools if action or documented acknowledgment is needed.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 14 Nov 2015 19:59:37 GMT</pubDate>
    <dc:creator>kpritchard</dc:creator>
    <dc:date>2015-11-14T19:59:37Z</dc:date>
    <item>
      <title>Modifying the Change Request email text</title>
      <link>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107525#M12662</link>
      <description>One of our options we have put in the CR form is multiple entry field for which group within the company will be impacted by the change.The first option we are thinking of is to have the email only be sent to those members of the impacted teams. There could be anywhere from 1 to 10</description>
      <pubDate>Fri, 04 May 2018 13:29:26 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107525#M12662</guid>
      <dc:creator>BenLoosli</dc:creator>
      <dc:date>2018-05-04T13:29:26Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying the Change Request email text</title>
      <link>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107526#M12663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, the email text comes from the Instructions field in the workflow activity.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Nov 2015 21:03:25 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107526#M12663</guid>
      <dc:creator>DonSenchuk</dc:creator>
      <dc:date>2015-11-13T21:03:25Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying the Change Request email text</title>
      <link>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107527#M12664</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my experience, ignorable emails become noise and eventually Users start to ignore everything coming from Windchill... well at least the non-core Users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My approach to this would be to look at doing conditional branching of parallel notification robots if/when a particular group of recipients needs to know, and removing the notification for the Assignment itself (or leaving in place for those that need to take action).&amp;nbsp; Do all the impacted groups need to take action (i.e. complete the assignment), or dot they just need to be informed?&amp;nbsp; You could do the same type of conditional branching of parallel assignments with different participant pools if action or documented acknowledgment is needed.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Nov 2015 19:59:37 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107527#M12664</guid>
      <dc:creator>kpritchard</dc:creator>
      <dc:date>2015-11-14T19:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying the Change Request email text</title>
      <link>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107528#M12665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are some options which we have used in the past here &lt;A href="http://www.ptc.com/cs/help/windchill_hc/wc101_hc/index.jspx?id=WCCG_BusLogicCust_WorkflowAdmin_EmailNotif&amp;amp;action=show" title="http://www.ptc.com/cs/help/windchill_hc/wc101_hc/index.jspx?id=WCCG_BusLogicCust_WorkflowAdmin_EmailNotif&amp;amp;action=show"&gt;http://www.ptc.com/cs/help/windchill_hc/wc101_hc/index.jspx?id=WCCG_BusLogicCust_WorkflowAdmin_EmailNotif&amp;amp;action=show&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Binesh Kumar&lt;/P&gt;&lt;P&gt;Barry Wehmiller&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 06:06:29 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107528#M12665</guid>
      <dc:creator>BineshKumar1</dc:creator>
      <dc:date>2015-11-16T06:06:29Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying the Change Request email text</title>
      <link>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107529#M12666</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I meant to add more but had to leave the office suddenly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are a couple of other ways to get the email notification to only go to the intended recipients. It may depend on where in the path this takes place. If it's on initial creation, then I'm not sure. We're setting our CRs up right now and the intent is to make every downstream group look at every CR and determine if they need to give input or not (rather than let the creator or some other person outside their department make that determination for them). If the intent is for the team selection to take place during an assigned activity, then the two things that come to mind are Transition &amp;amp; Routings or the Set Up Participants tab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the Transitions &amp;amp; Routings, the assignment page (the one with the Complete Task button) could have a list of check boxes. The assignee simply checks a box for each group or person that is to get the Change Request. From that assigned activity, one or more action paths are fired off: one for each chosen group. This does make for a cluttered workflow template, but that's really only something the admin sees anyway (IME). Then, when the next assignments are started, with the Activity tab's 'Send Notification' box checked, the new assignee gets whatever message is in the Instructions field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Set Up Participants tab keeps the workflow clean while allowing the assignee to choose who gets the next action in the path. The cludgy part in my experience is that the same assigned activity is used for all participants. This means generic instructions like, "Review Change Request and give input". That's okay for early in the flow when it's an overview list like estimates for dates, tools, man-hours, etc. Later in a workflow when you might want to explicitly define the work each participant needs to do is when this method falls off in usefulness. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Nov 2015 13:23:22 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107529#M12666</guid>
      <dc:creator>DonSenchuk</dc:creator>
      <dc:date>2015-11-17T13:23:22Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying the Change Request email text</title>
      <link>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107530#M12667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It sounds like you need to control/set the recipients on the fly. I would say in the workflow before the main tasks that are sending out these emails have an initial task from a change coordinator of some kind with Set Up Participants, that way you can custom tailor who gets each task for every change.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Feb 2016 23:44:13 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107530#M12667</guid>
      <dc:creator>doehr</dc:creator>
      <dc:date>2016-02-19T23:44:13Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying the Change Request email text</title>
      <link>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107531#M12668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A href="https://community.ptc.com/u1/111899"&gt;Ben Loosli&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It looks like several people have given some good ideas here. Did any of them get you headed down a path you could work with? Any follow up questions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2016 22:23:47 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Modifying-the-Change-Request-email-text/m-p/107531#M12668</guid>
      <dc:creator>LoriSood</dc:creator>
      <dc:date>2016-02-26T22:23:47Z</dc:date>
    </item>
  </channel>
</rss>

