Workflow - Created new workflow process(CO)

Question

I created a new workflow called "CO".&nbsp; It was working fine last week.

As I was making changes I forgot to check in or unlock the Item.

I have checked in the Item or Unlocked the item and when I create a new CO, I cannot save it.

I get the following error: Aras.Server.Core.ItemIsLockedException

Buffer:

-&lt;SOAP-ENV:Envelope&gt;

-&lt;SOAP-ENV:Body&gt;

-&lt;SOAP-ENV:Fault&gt;

&lt; faultcode &gt; SOAP-ENV:Server.ItemIsLockedException &lt;/ faultcode &gt;

&lt; faultstring &gt; Aras.Server.Core.ItemIsLockedException &lt;/ faultstring &gt;

-&lt;detail&gt;

&lt; af:legacy_detail &gt; Aras.Server.Core.ItemIsLockedException &lt;/ af:legacy_detail &gt;

&lt; af:exception message =" Aras.Server.Core.ItemIsLockedException " type =" Aras.Server.Core.ItemIsLockedException " /&gt;

&lt; af:item type =" CO " id =" 3996DE7B25BE4BE8BD95083B381D0F56 " /&gt;

&lt;/detail&gt;

&lt;/SOAP-ENV:Fault&gt;

&lt;/SOAP-ENV:Body&gt;

&lt;/SOAP-ENV:Envelope&gt;

yoann_maingon · Answer

can you precise the steps you process.

Today, you create a CO, you save it directly and it raises this issue?

Did you try to put a promotion on the first step of the workflow? did you uncheck the automated start state?

former_member · Answer

Yoann,

I have it on the second step, here is my process it is simple.

Start -&gt; In Work -&gt; In Review -&gt; Prototype Released

@In Work it branches to Cancelled

Here is what I discovered, if I create the CO Item and save without selecting my Classification which is either Prototype Release or Production Released it saves.&nbsp; Then I can select my Classification.&nbsp; When I do these steps it creates two workflows of the same number, which&nbsp;is not right.

yoann_maingon · Answer

how do you launch your workflow? in the lifecycle or by just making the workflow default in the itemtype configuration? A wild guess would be that on a specific classification you start a workflow from the lifecycle which would interfere with the default one.

former_member · Answer

Yoann,

You are correct I had set the workflow to the default; so I uncheck it as the default and all is working corretly now.

Since you mentioned that statement to me I went back to an email I sent to Connie Burk where she told me not to set it as the default.

So thank you for jogging my memory and reviewing my notes.&nbsp; Mission accomplished...

former_member · Answer

Yoaan,

I seem to have revisited this problem. I am creating my own PRs lifecycle and workflows. Following the advice here, I unchecked default from my PR's new work flow (I removed the default). I set my lifecycle start to run my workflow WC PR Workflow. I unchecked default.

Still receiving&nbsp;&nbsp;Aras.Server.Core.ItemIsLockedException

When I modified the default PR lifecycles and workflows, I didn't have any of these problems. Thought I was helping myself by preserving the original workflows and processes.

Now sure where to go with this one now.

&nbsp;

Thanks,

Tom

Forum Discussion

Workflow - Created new workflow process(CO)

6 Replies

Recent Discussions

Solid Edge derived part (Part Copy of a Part Copy) → empty 3D viewable, conversion task "Succeeded"

virtualGetForm 404 when accessing Aras through Nginx

[ARAS 14] Change display order of authentication options

aras plm 11.0 -Authorization code verification failed(AP-00006...)

Exception of type 'Aras.Server.Core.InnovatorServerException' was thrown.