Intralink 8 M050: Rivese objects using promotion request

[sachinnet]

Dear all,

I am trying to revise object using lifecycle transition " Revise" through promotion request.

e.g.

Part is available as "abc.prt" under "Released" state with Version 1.0 & user want to promote using promotion request in Intralink 8 to "Development" & Version "2.0"

Using above life cycle user could able to promote from released to development but revision doesn't change automatically after promotion approval.

Please refer attached PDF for basic lifecycle & OIR which I am using for implementation. Please suggest solution.

Thanks in advance!!!!

-Sachin

[MikeLockwood]

Fundamentally cannot approach this way.

State change only: Use Promotion Request

Version change (likely with Modify then state change): Use ECN. After the Audit assignment in an ECN workflow, the robot "setChangeablesToReleased" essentially does what a Promotion Request does - for all objects on the Resulting Objects table.

[MikeLockwood]

Simple concepts but hopelessy confusing from PTC's diagrams (good for consultants)...


This diagram as provided by PTC everywhere (guaranteed confusion):

[cid:272065419@27032009-28F0]


Needs to be this diagram in order to show what Promote and Revise do (Promote changes the state of one iteration; Revise is a metadata save-as operation, leaving the original alone):

[cid:272065419@27032009-28BF]

To complete the diagram, add "Change" transition. The "change" transition is essentially Promote but only used within an ECN:

[cid:272065419@27032009-28C6]

I read and reread the documentation on this 4 years ago and just got a bigger and bigger headache each time - it never became clear until I started making two-dimensional instead of one-dimensional diagrams.

But - good for consultants who know the secrets...$$$

[ptc-571495]

Sachin,

The Promote and Revise transitions are independent of each other. The
Promotion process does not perform a revise operation only a set state
operation as a part of its workflow. The Revise transition describes what
should happen when a user performs a manual 'New Revision' action.

To accomplish your scenario, the user would navigate to the RELEASED CAD
Document and create a new revision (i.e. Version 2.1) . Your transition
should then specify that a revision from RELEASED should go to the
Development state. The user works on the CAD doc(s) until they are ready to
promote it. Then they create a Promotion Request and select RELEASED as the
target state.


H. Lewis Kennebrew, II
Vice-President, Operations
ProductSpace Solutions, Inc.
"Your Products to the Nth Power"

2021 Midwest Road, Suite 200
Oak Brook, IL 60523
Work: 630-495-2999x8101
Fax: 1-877-562-5144


> Revise" through promotion request.
>
> e.g.
>
> Part is available as "abc.prt" under "Released" state with Version 1.0 &
> user want to promote using promotion request in Intralink 8 to "Development"
> & Version "2.0"
>
> Using above life cycle user could able to promote from released to
> development but ...