Our 3D CAD supplier models have been moved to 3Dfindit.com, the new visual search engine for 3D CAD, CAE & BIM models.
You can log in there with your existing account of this site.
The content remains free of charge.
This block contains the specification how the single status of ACTIVE_STATE and REQUESTED_STATE columns should be adjusted during the update process.
#:VALS_S ;active_state: ;0: locked ;1: released ;2: expired ;requested_state: ;0: - ;1: updated ;2: expired ;3: new
There is no key for WORKFLOW_OK_ACT_STATE_NEW. We copy this state from the old part.
WORKFLOW_OLD_ASTATE0=2 WORKFLOW_OLD_RSTATE0=0 WORKFLOW_NEW_ASTATE0=1 WORKFLOW_NEW_RSTATE0=0
Old parts will be set to the indicated values. The dirty parts in the new projects will be deleted.
WORKFLOW_OLD_ASTATE1=0 WORKFLOW_OLD_RSTATE1=2 WORKFLOW_NEW_ASTATE1=0 WORKFLOW_NEW_RSTATE1=1
Set parts in deleted projects to the indicated values.
WORKFLOW_OLD_ASTATE2=0 WORKFLOW_OLD_RSTATE2=2
[WORKFLOW] CUSTOMUPDATESCRIPT=
A custom updatescript (vbs) can be attached. It is called twice after the user decided what is to be done with the new version: first with the old dataset, second with the new dataset.
This is useful e.g. for extended PDM update processes.
The callback funktion is defined like this:
Zurück | Nach oben | Weiter |
1.1.6.7.25. plinkupdatemgr.cfg | Zum Anfang | 1.1.6.7.26. plinkusers.cfg |