True Modified Date on objects

[ybagul]

Currently 'I guess', "Last Modified" date changes when object is created or checked in. When object state changes (via promotion etc) or effectivity is assigned, "Last Modified" date does not change. It would be helpful if there would be a way that captures timestamp for changes like above (and may be more).

[GregoryPERASSO]

‌hi

for state change , you have maturity history table

[JeffZemsky]

I closed the idea as No Plans to Implement.  Modified captures the checkin/checkout date as that is when a change to the definition and content can happen.  A change to the state is captured within the Life Cycle History for the item and is available today.

[ybagul]

I agree that the information exist, just in multiple places. Our use case is... when "anything" changes for products in Windchill, it should be updated in downstream system with daily or on-demand loads. State change or adding effectivity is considered a change in our system which needs to be propagated downstream. A special case is, adding effectivity to latest version may change effectivity on non-latest revision in case its overlapping. It would be nice if there is one way to check (without customization) to get modified products and load into downstream system.

[DonSenchuk]

Well, I'd give you an up-vote, but...

... it appears there is no way to do so.

[dgschaefer]

Wow, 4 days from idea created to a denial from PTC.  That's got to be a record - or a mistake. Ryan Kelley‌, care to comment? 

When PTC says no,it'd be nice to have a reason why.

[DonSenchuk]

Especially when the idea makes sense and just gathers data that already exists.

[JeffZemsky]

As I replied above that information is already available within the system.  The Life Cycle History already carries this information to be used today.

[JeffZemsky]

Yogesh - if  you use change mgmt to do the updates to Effectivity this can be pushed to your ERP system using existing capabilities.  The integrations will pass not only new change info (eg effectivity), but updates to existing effectivity statements.

[dgschaefer]

Did you mark it as "No Plans to Implement"?

[ybagul]

Jeff,

I should have mentioned this, information exist for change in state, not when effectivity was applied. We use Change Management, but disabled OOTB product release and apply effectivity upon CN audit. CN actually has a task to promote Products and another one to apply effectivity (why? lets say business process) after a QA task. We created a separate tool for users to set effectivity. So the dates when a product gets modified (via checkin), promoted (via promotion) and effectivity (via in house tool) are completely different. Our downstream system needs to get all these updates via incremental loads.

[JeffZemsky]

Yes Doug.

[DonSenchuk]

Must... resist... replying... with... snark.

[JeffZemsky]

Yogesh - I don't think that itself would preclude using those methods to send the updated information to ERP.  I don't remember if we support Promotion itself via the ERP integrations, but there are ways to support the others today.

[dgschaefer]

You know what, I just realized that, though it's been several years, my brain still thinks of you as working for Plug Power, not PTC. I also see that you said that your response above says as much and I somehow missed it.

I think I must be loosing my mind. Sorry folks, nothing to see here.

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.