Many Change Notices for a single part, same version

[mdebower]

Hey...

For example.

-marc

CAD / PLM Systems Manager

TriMark Corporation

[rjones]

The Wt Part, CAD model, and drawing for 12345 version 2.5 should be on the
first CN in the affected objects table. This will provide a flag to the
users that a change is in process.
If version 2.5 is the latest "In Work" version then it should be on the
Resulting objects table again flagging users that a change is in process;
version 1.x would be in the Affected Objects table.

On Wed, Jan 28, 2015 at 3:19 PM, Marc DeBower <->
wrote:

> Hey...
>
>
>
> Does anyone know of a method to prevent multiple change notices being
> created for the same version of a WTPart or CAD Document? Lacking that,
> how do you handle this situation?
>
>
>
> For example.
>
>
>
> - I have a WTPart, CAD Model, and Drawing for part 12345 version 2.5
> - A change request and change notice for one issue gets written
> against that set of data at that version.
> - The change notice is still in process when... Days later, a second
> change request and change notice without knowledge of the first change
> notice, is written for a different issue, against the same version of the
> objects as the first.
>
>
>
>
>
> Two questions:
>
> 1. How do you handle such a situation?
> 2. Can it be prevented in the software?
>
>
>
>
>
>
>
> -marc
>
> CAD / PLM Systems Manager
>
> TriMark Corporation
>

[DonSenchuk]

Any part, PRT, DRW or ASM that is already on a change notice has a little orange/red triangle shown when a search is done, like this: [cid:image001.png@01D03B0E.619D15D0] . (This can also be seen when browsing in the Product or Library Context.)

This should mean that users notice this icon and they know to track down who has the open CN and add their changes to that one.

Aside from encouraging user awareness, I’m not sure there is a way to prevent it.

[mdebower]

Russ and Don....

You are 100% correct. Evidently some users don't pay that icon any attention, or think that the flag is there because of the CR / CN they are creating...

Subtlety is lost on some, I would like a big honking warning message or something. Of course they wouldn't read that either.

-marc

[gnatesan]

1.Try with business rules option(wc 10.x)
2. Add listener rule



Regards
Gangadharan N

>

[atre.shreyas]

You can write UI Action validator for change notice wizard to prevent creation of change notice.

or write expression in workflow just after workflow starts, to check if affected object included in change notice is/are already included in any other open change notice.

See below link for require API’s

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS63182&posno=3&q=ChangeHelper2.service.getAffectingChangeActivities&source=search

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS55955&posno=1&q=api%20get%20affected%20object&source=search

Hope it helps!!

Thanks

Shreyas

[giridhar82]

You can utilize Business Rule validations to handle these.


On Thu, Jan 29, 2015 at 3:03 AM, Shreyas Atre <->
wrote:

> You can write UI Action validator for change notice wizard to prevent
> creation of change notice.
>
> or write expression in workflow just after workflow starts, to check if
> affected object included in change notice is/are already included in any
> other open change notice.
>
> See below link for require API’s
>
>
>
>
>
>
>