INTRALINK pending objects

[peppinu]

To INTRALINK gurus,
We have just upgraded to Intralink 3.3, does anyone know how to check in stuff in commonspace with a pending status? We have an issue where we want to check in objects that need yet to be released before anyone can use. In the PDM days there was a "pending" state which let you submit but everyone new that they were not final.

Joe Borg

http://www.methode-eur.com

 

[dakeb]

Use version numbers for pending, and for final release set the revision to 1. So if a file is revision 0 version 3 for instance, you will know it is pending. Released drawings should always be version 0.

 

[peppinu]

Maybe I wasn't clear enough. What I meant was a modification to the same object

Joe Borg

http://www.methode-eur.com

 

[Tofflemire]

Hi Joeborg1,

Have you used Intralink before? It sounds like you have not, so I will start off by stating that you need to get the admin side of it established first before you start using it. That means defining your release levels, rev's, vault tree, naming convention, user levels and administrator, and most importantly your rules for use.

I will offer a couple of options to you to assist in your problem, and you and your co-workers should decide which fits your needs.

You can set a release level in the admin of Intralink. IE Production release, Engineering release and Pending. You can Promote or demote parts or assemblies.

You can also set warnings or common space status that other user see that the part/assy has changed by picking a part/assy and right clicking, then choose change status and pick common space status tab, choose what option best fits.

There is also another option which my coworkers would not buy into which was email notification for review and voting for promotion.

The above options all have to be reviewed by you and looked into the pro's and con's of how to use them. The Intralink help should be a good place to start.

Tofflemire

 

[peppinu]

Tofflemire,
We have been using Intralink for about 4 years with 120 GB of data. In the old PDM days we could submit with a pending approval status and it will stay like that until it was approved. It would show clearly that the object was really pending. With release levels users are not prohibited to check out the unreleased objects and use the data to create molds, jigs, gauges etc. The best solution I have come up with so far, is to set a release level with "no access" to the world and force them to check out a previous version/revision if needed. I was wondering if there was a better solution.

Joe Borg

http://www.methode-eur.com

 

[looslib]

Intralink release levels, roles and authorizations are very critical to get the operation to work the way you describe, but it can be done. You need to map out the release levels and user roles into the your folder authorizations so that parts cannot be seen at the pending release level.


"Wildfires are dangerous, hard to control, and economically catastrophic."
"Fixed in the next release" should replace "Product First" as the PTC slogan.

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

 

[fighterpilot]

Remember this about Intralink as opposed to Pro/PDM. Intralink doesn't care about what has been checked-in (submitted) only what moves from one release level to the next. Just checking something in won't trigger a pending state but promoting to a release level will. Setup your system with this in mind.