cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Create Document & Workflow

Highlighted
Regular Member

Create Document & Workflow

I have a workflow that is going to be kicked off on the creation of a
new document from a template. One of the issues I'm running in to is,
if a user selects "Checkout and Download" on the document create
wizard, it will cause an error in the workflow when the workflow tries
to Set State to In Work.

I'm wondering how others have handled this?

I'm assuming you could undo checkout through some Java code on the
PBO. I wish there was an undo checkout method robot.
5 REPLIES 5
Highlighted

Create Document & Workflow

When a document is first created, its state is In Work. There should be
no need to change it. You can put a check before the robot if you do
need it to see if its checked out and sync (wait) until is checked in.
Careful also with the workflows in the initial state. I believe it you
revise it or set the state back to the initial state, it will trigger
another instance of the workflow.
Highlighted

Create Document & Workflow

Sorry, my initial state is Open, to avoid the additional workflows
from instantiating on a Revise.

My issue is I don't want a user to Check it out at Open. Thought, I
might be able to take away Modify at Open that could prevent the
abilitiy to Check Out on create.

Steve D.

Quoting "Villanueva, Antonio" <->:

> When a document is first created, its state is In Work. There should be
> no need to change it. You can put a check before the robot if you do
> need it to see if its checked out and sync (wait) until is checked in.
> Careful also with the workflows in the initial state. I believe it you
> revise it or set the state back to the initial state, it will trigger
> another instance of the workflow.
>
Highlighted

Create Document & Workflow

We check the object status before every set state robot. If the object is checked out, we assign a task to the user to check it back in. This avoids the disabled/aborted set state robots.

Dax Williams
Business Administrator, Windchill
Lifetime Products, Inc.
Highlighted

Create Document & Workflow

That's a good suggestion Dax.

For this case, since the object state is Open and I don't want any
iterations of Open, I'm removing the ability to Modify the object. So
now if they do select "Check out and download" on the Document create
wizard, the document will not check out.

My workflow can now Set State and also the next step will check out
the object for the Creator at In Work.

Steve D.

Quoting Dax Williams <->:

> We check the object status before every set state robot. If the
> object is checked out, we assign a task to the user to check it back
> in. This avoids the disabled/aborted set state robots.
>
> Dax Williams
> Business Administrator, Windchill
> Lifetime Products, Inc.
Highlighted

Create Document & Workflow

We do the same thing. Before any setState robot we check to make sure the
object is not checked out. If it is checked out the user is sent a task.
We also do this before our robot that adds object to a CA as a resulting
item.

David

"Dax Williams"
<dwilliams@lifeti <br="/> me.com> To
"Villanueva, Antonio"
03/02/2009 12:40 <->,
PM Stephen Drzewiczewski
<steve@stevedandrebecca.com>,
"-"
Please respond to <->
"Dax Williams" cc
<dwilliams@lifeti <br="/> me.com> Subject
[solutions] - RE: Create Document &
Workflow










We check the object status before every set state robot. If the object is
checked out, we assign a task to the user to check it back in. This avoids
the disabled/aborted set state robots.

Dax Williams
Business Administrator, Windchill
Lifetime Products, Inc.
Announcements