How to stop email notifications when Project "state" is changed to "running" by START

[sking]

We want to change the "state" for select number of Projects without emails being sent out. We don't want to impact other unrelated notifications\emails from being sent. Can the email queue be emptied before disabling without impacting other notidcations in the queue?

[soerton]

Set State or a Promotion with no notifications?

Stephen Oerton

Windchill Process Specialist

[ddemay]

My gut tells me this notification is hard coded in the Project Link net
markets library like replacing folks on roles. You may need a spam filter
to catch them?

A database triggered update might bypass this subroutine.

David

[sking]

Stephen Oerton- Changing states of the ProjectLink Project itself forces you through "Start" which then sends notification to all team members.

[sking]

David DeMay- A spam filter may be a viable option... I'll look into that.

[soerton]

Thought you were meant PDMLink.

In Reply to Steve King:

Stephen Oerton- Changing states of the ProjectLink Project itself forces you through "Start" which then sends notification to all team members.

Stephen Oerton

Windchill Process Specialist

[sm]

I don't have a solution for this, but it would be great to get a Product Idea submitted for more control over the email notifications sent by ProjectLink. At a minimum, it would be nice to have a checkbox in the UI to allow the initiator the choice of whether or not notifications should be sent.

-Scott

[tgudobba]

Steve,

We had this same issue.

Use xconfmanager to update the wt.properties file on the server.

Set this;

wt.inf.team.sendInvitationEmail=False

[ddemay]

This will disable all functionality related to invitations if that is what
is desired.



On Wed, Mar 11, 2015 at 11:23 AM, Tim Gudobba <->
wrote:

> Steve,
>
> We had this same issue.
>
> Use xconfmanager to update the wt.properties file on the server.
>
> Set this;
>
> wt.inf.team.sendInvitationEmail=False
>

[tgudobba]

In our case, that was desired. We have enough other notifications occuring through various workflows to suffice. From what we gather, we use ProjectLink much different than other Windchill customers.

[sking]

Yes! This is what we need. Thank you!

[sking]

Tim and others- We will be testing this out for sure. Thanks again. We have several thousand users that would get the emails, so I am being a bit over cautious, so given that fact. Do you know how the flag works? Does it suppress the creation of the email completely or are they queued up but just not sent? I would only be temporarily setting this to False. So, we would use xconfmanagaer, restart to propagate, make the changes to the state of the Projects stepping it through the Start bit, re-set the flag again with xconfmanager, restart to propagate. If they were simply queued up then they may go out after we set the flag back to True.

[ddemay]

Sounds feasible, but a restart may not be required if you login with the
jconsole to change properties hot for that MethodServer JVM instance.


On Wed, Mar 11, 2015 at 12:10 PM, Steve King <->
wrote:

> Tim and others- We will be testing this out for sure. *Thanks again*.
> We have several thousand users that would get the emails, so I am being a
> bit over cautious, so given that fact. Do you know how the flag works?
> Does it suppress the creation of the email completely or are they queued up
> but just not sent? I would only be temporarily setting this to False. So,
> we would use xconfmanagaer, restart to propagate, make the changes to the
> state of the Projects stepping it through the Start bit, re-set the flag
> again with xconfmanager, restart to propagate. If they were simply queued
> up then they may go out after we set the flag back to True.
>

[ddemay]

Also forgot to mention, it will not queue up the messages, they just will
not be generated by the subroutine that checks this property.

On Wed, Mar 11, 2015 at 12:38 PM, DeMay, David <->
wrote:

> Sounds feasible, but a restart may not be required if you login with the
> jconsole to change properties hot for that MethodServer JVM instance.
>
>
> On Wed, Mar 11, 2015 at 12:10 PM, Steve King <->
> wrote:
>
>> Tim and others- We will be testing this out for sure. *Thanks again*.
>> We have several thousand users that would get the emails, so I am being a
>> bit over cautious, so given that fact. Do you know how the flag works?
>> Does it suppress the creation of the email completely or are they queued up
>> but just not sent? I would only be temporarily setting this to False. So,
>> we would use xconfmanagaer, restart to propagate, make the changes to the
>> state of the Projects stepping it through the Start bit, re-set the flag
>> again with xconfmanager, restart to propagate. If they were simply queued
>> up then they may go out after we set the flag back to True.
>>
>

[sm]

Thanks Tim!

To point everyone to a common source, information on this property is included in PTC CS Article CS114839.

-Scott

[sking]

Scott- I logged the product improvement suggestion. Thanks

https://community.ptc.com/t5/Windchill-Ideas/User-control-to-allow-or-prevent-sending-invitations-to-the-team/idi-p/468808