Skip to main content
RocketMan1-Visitor
1-Visitor
July 31, 2012
Question

Promotion Request Email - not informative

  • July 31, 2012
  • 11 replies
  • 5276 views

Hi All,

 

I'm pretty new to Windchill but I have scoured the PDM User's Guide, Business Admin Guide, and System Admin Guide, and I cannot find any way to make the email notification for a promotion request more... dynamic. That is, why the heck doesn't the description for the promotion request get sent in the email notification? The generic message entered under the "activity tab" of a workflow process is less than helpful. You would think that the promotion request description would be included in the notification email - this way you can see just from the email where that falls on your priority list.

 

Is there a method to doing this OOTB? If not, does anyone have any recommendations on where to look to find code that might help?

 

Thanks in advance!

11 replies

jzupfer1-Visitor
1-Visitor
August 1, 2012

Hi, Ben,

The Windchill Customization Guide includes information about tailoring workflow notification. The chapter entitled "Customizing Workflow Administration" covers the following topics:

  • Customizing promotion request workflow processes
  • Enhanced promotion request
  • Workflow email notifications

The link I've included is to the 10.1 version of the guide on ptc.com. You can find other release versions there as well, and the customization documentation is also included in the 10.0 and 10.1 versions of the Windchill Help Center.

Please let me know if this documentation is helpful and if you have any feedback.

Jane

Jane Zupfer
VP, Windchill Publications
T 763.957.8299 E -

PTC.com

    RocketMan1-VisitorAuthor
    1-Visitor
    August 3, 2012

    Jane,

    Thanks very much for your response. Is there any form of test environment such that I can modify our current Promotion Approval Request workflow process without disrupting the whole system?

    The reason I ask is that it seems that it would be infinitely easier to use a test/demo environment than creating a whole new environment (Not only am I concerned with breaking the current operational environment, I'd like to prevent spamming management when I start testing approvals).

    My impression regarding setting up this system in a way that I can be free to test without breaking the system that is currently in place is to create a new version of each: workflow, lifecycle, team, context, promotion preference, etc. Is that accurate? This is why I ask about a test environment. If this isn't accurate, could you please point me in the right direction?

    Thanks!

    jzupfer1-Visitor
    1-Visitor
    August 3, 2012

    Ben,

    There is a System Validation Guide ,authored by the Enterprise Deployment Center, that describes how to set up a test system that can be used to pre-qualify a production environment or to qualify planned changes afer the production system has been deployed. Is this helpful?

    Jane

    MatthewKnight1-Visitor
    1-Visitor
    August 3, 2012

    I'm not sure which class or template you're looking at, but from what I remember, much of the notification stuff is hardcoded, and not even extendable through the use of a service, and there isn't much available through the template. Sometimes, you can extend a service and add or override methods to be used by a template, but I've found it easy to not use some of the OOTB notification options, and just add my own expression before the workflow activities and create my own emails.

      RocketMan1-VisitorAuthor
      1-Visitor
      August 21, 2012

      Thanks Matthew.

      I'll have to remember that last part.

      I was really referring to using the WC Customizer's guide in conjunction to the Promotion Request template to somehow save user-definable text as a variable which can then be included in a notification.

      Terms & ConditionsAccessibility statement