Automatic Check in of File during creation

[pkennedy]

Is there a way to have PDM standard automatically check in a file when it's first added to the vault?

[Diaval]

Unfortunately no. To force the check in on adding a file to the vault would probably require using Dispatch or some other API hook on the add file action that can't be done in a Standard vault.

This would be a nice enhancement for both Standard and Pro, though. So many things rely on that initial check in that it feels like it should be default option to force the initial check in when a file is added to the vault.

[pkennedy]

That's what I figured, maybe thought someone had a work around by chance.

[jcapriotti]

Technically it already does this. If you drag a file in, it automatically uploads a version 1 of the file. It's in a private state so no one but the user and admin sees it unless you unable it for other users. The others users will see it but not be able to open it until that first check in. The admin can open it though.

[Diaval]

Technically it already does this. If you drag a file in, it automatically uploads a version 1 of the file. It's in a private state so no one but the user and admin sees it unless you unable it for other users. The others users will see it but not be able to open it until that first check in. The admin can open it though.

What you describe here is the add file process. While the file is added to the vault with a copy uploaded to the archive server, there are a lot of things that don't happen with the file until the initial check in.

The initial add will:

• Create the document entry in the Documents table of the Db

• Extract the mapped variable metadata and store the variable values in the Db

• Generate and write Default variable data based on the card setup - including generation of serial numbers

• Upload a copy of the file to the appropriate archive folder based on the Document ID from the Db

• Extract a thumbnail of the file and store it with the archive for certain file types

• Create the index.xml for the document in the archive

The initial check in will:

• Assign a category based on category conditions

• Transition the file into a workflow based on workflow conditions

• Populate the XRefs table to get reference tree data (this is why you do not see any BOM, Contains, Where used data for private state files)

• Extract SolidWorks BOMs

• Make the file available for other users with appropriate folder and state permissions

I can understand why some users may want to use private state files as a way to manage things that are "work in progress" to keep others from seeing/using it prematurely, but a better practice is to use folder and state permissions to control visibility.

[majo]

You can use dispatch for this. If you want an example, feel free to contact me.

Cheers Mario

[Diaval]

You can use dispatch for this. If you want an example, feel free to contact me.

Cheers Mario

Dispatch can't be used in a PDM Standard vault.