Quick Change pdf update.

[Marcin.Szklarek]

Hi!

I am having problems with pdf of dwg. When I revert released file to quick change and then back to released I can't get vault to update PDF. I have set it in lifecycle( vault settings, behaviors, lifecycles) under flexible release process and changed transition quick-change - released( in transitions it is set to update view and pdf). No change. What makes me wonder is that PDF is in released state and does not have quick change state.

Any ideas?

[Marcin.Szklarek]

As you see there is some problem I cannot trace.

[smilinger]

1. You are not supposed to change the state of the pdf file.
2. pdf files are not supposed to have quick change state.
3. pdf files are supposed in the Design Representation category.

[cbenner]

@smilinger 

All valid, but I think the OP was trying to figure out how to get the pdf to update now that he has already used Quick Change on the file.

At this point, I wonder if it would not be best to simply delete the existing pdf and generate a new one (in the correct category)?

Thoughts?

[Marcin.Szklarek]

Exactly. Say you have made a spelling mistake or missed a dimension and it was released. On the quick- change you can change all that without up issuing the model- drawing. Now  the problem I have is that you can have the  instruction to update pdf in transfers but the pdf itself does not update as it is in release state. Why then have quick-change if that does not update the most crucial thing   -PDF?

[Marcin.Szklarek]

Deleting existing PDF  and commencing with Quick -Change does not force to produce new one. The only way so far is to up issue and then it is producing new pdf with updated. I think this is a big bug of Quick-Change making it useless.

[smilinger]

It's too soon to think it as a bug. Try to make some real change to your dwg in the quick change state, then release again, and do not change the state of pdf files. A screenshot of the files list (show their states, revs, categories, etc.) may be helpful.

[Marcin.Szklarek]

I did exactly waht you suggest before.

Procedure:

Create ipt. 

create dwg.

Release both.

Initialise Job processor to create PDF.

Put ipt and dwg in quick-change status.

Change dwg ( additional annotation)

Change the state from quick change to released.

Initialise Job processor.

The error from post one comes on and no changes in  PDF.

[smilinger]

The third error in your screenshot looks like triggered by incorrectly change state of pdf files. Do you get all these errors with the same message?

Another thing to consider: do you have same revision scheme for you dwg and pdf? If one is letter based and the other is number then it cause error.

[Marcin.Szklarek]

I do not understand what you are suggesting. I gave you the step by step procedure, the PDF is generated by Job processor, so it must share the dwg issue type. 

Anybody  can help?

[gandhey]

Hello,

I believe what is smilinger asking which is not very clear to me too - how is the 'Synchronize Properties' job triggered for your pdf files ?  I guess you would have set this on some LC transition for the 'Design Representation Process' - however I am wandering as the 'Quick Change' state is unavailable in the 'Design Representation Process' - in which LC transition are you setting this for the pdf files ?

May I know Vault version you are using please ?

Regards,

Yogeshwar

(Vault team)

[Marcin.Szklarek]

That is exactly what I am asking as there is no Quick-Change state for design representation process.

How to make in Lifecycle the pdf to update. On transition from released to work in progres it bumps up revision.

Vault 2018.3.2 build 23.3.21.0

[smilinger]

You don't change the state of pdf to make it update. When you re-release your dwg, new version of pdf is generated again in the released state.

However you should use a special admin use to login and run the job processor, this user should have write access to the pdf in the released state.

[smilinger]

Read this:

http://help.autodesk.com/view/VAULT/2018/ENU/?guid=GUID-F05BFEAF-A362-4070-BBA6-F3A74602967E

[Marcin.Szklarek]

I understand what you are saying and i have read the read me you suggested. All my setting are according to what it says and it is not producing a "fresh" pdf and that is my problem as was from begining.

At the moment I am administrator user.

[YounesYammouri]

@Marcin.Szklarek , I tried the workflow with the quick change and PDF creation. It works well on my side. They might be some configuration issues (e.g. security tab for lifecycle state for PDF (Design Representation lifecycle definition) in your environment to get this up and running properly. Here is a video showing how this work with quick change transition: https://www.screencast.com/t/3iUfa1EKA2h

[Marcin.Szklarek]

---

@YounesYammouri 

Thank you, but there is significant difference you are using Vault 2020 I am on 2018.

[Tony_Yates]

Hi Marcin,

Did you ever sort this problem out?

We have the same issue with vault pro 2019.

Just not updating the pdf after a quick change.

Cheers

Tony

[tschaeferZNBXX]

@Marcin.Szklarek 

Have you looked at the lifecycle for pdfs?

I have received similar errors when a user created the PDF and did not allow the job processor to do so.  We have ran into issues with users creating a PDF adding it to Vault then changing the states to "Released".  It really sounds like it is an issue with the process your users are using not Vault itself.

[Marcin.Szklarek · Accepted solution]

Hi!

I did not managed to get the Vault produce proper Quick change updates with pdf update. I guess we need to get 2020 version as it works ok there it seems.