spolen - Tuesday, February 5, 2008 7:38 AM:
I am still having problems when promoting and ECN past the Planning Phase, I am getting an error "Error during the promotion. Failed to get the transition to promote from in Planning to to Approved". I have reviewed other work flows and see no differences, so can anyone tell me what I am doing wrong, or what I need to get this promoted. I am the CM Specialist I tasked with moving this along, so it is in my Inbasket to complete.
Thanks,
Sue
SamsAn - Wednesday, February 6, 2008 4:04 AM:
Hi.
I guess the problem is broken correspondence between ECN Life Cycle Map states and ECN Workflow Map activities. I.e. the system tries to promote the ecn instance from Planning to Approved, but ECN Life Cycle Map does not have such paths. How it works.
For example, consider Update Documents activity of ECN Workflow Map of the standard PLM solution. The activity has Workflow Promote Server Event (see Server Events tab). So, if you complete ECN Planning activity (from InBasket) then Update Documents activity is activated and then the method automatically promotes the ecn instance from Planning to In Work state.
So, if you use standard PLM solution then the correspondence had been broken for the ecn instance in some way (for example using Reset Life Cycle state or like that).
If you use modified standard PLM solution (especially ECN Life Cycle Map or ECN Workflow Map) then please check carefully the correspondence between ECN Life Cycle Map states and ECN Workflow Map activities that is based on Workflow Promotions items.
SamsAn.
spolen - Wednesday, February 6, 2008 8:29 AM:
Hi SamsAn,
I checked the workflow map and the activity for the server event shows workflow promote. I also looked at the lifecycle Map and it shows the same activities.
The work flow shows:
Start - Path "go" - Submit ECN - Path "Submit" - ECN Planning - Path "Complete - Update Documents - Path "Complete" - Review Documents - Path "Approve" - ECN Audit - Path " Complete" - ECN Released.
Each shows the server event shows as workflow promote.
The Lifecycle Map and the following path is shown:
State - new - transition aras plm - In planning - transition aras plm - In work - transition aras plm - In review - transition aras plm - Released
I may have tried to reset the default lifecycle in trying to get this to promote. Is there a way to fix this? I'm sorry to keep being such a pain, but I have numerous ECN's that need to be processed and am stuck until I can get this issue fixed.
Thanks,
Sue
SamsAn - Wednesday, February 6, 2008 8:57 AM:
Which of activities (please give its name) is displayed for you in InBasket?
Which of states the ecn instance has in your case?
Did you change Workflow Promotions instances of the standard PLM solution?
Anyway, if you are sure that your data model is correct but just the correspondence between the states and activities had been broken only then you can do the following. Login as admin, select Change ManagementECNs in Main Tree, highlight the ecn instance, click Promote Item icon to promote to the next state. Do promote until you get the required state setup for the ecn. Please note, you may use ToolsAdminReset Lifecycle State main menu command to put the ecn in New state.
spolen - Wednesday, February 6, 2008 10:00 AM:
Inbasket shows activity as ECN Planning, Status is Active and I am logging on as the administrator and have tried to promote, but it gives me the error that I stated before.
The ECN instance is Change Specialist I as being the participant for the ECN Planning Activity.
The only thing I changed was the tasks for each activity, and I had an Aras Instructor here with me when we did this. I did go to the ECN and promote to in work, then in review, but of course this does not clear up the issue with the break in the workflow and finding where it is.
SamsAn - Wednesday, February 6, 2008 10:20 AM:
The ECN should be in In Planning state when your are trying to complete ECN Planning activity in InBasket (but it is In Review as displayed in your post). Thus just reset Lifecycle State for the ECN and promote it to Planning state manually (described in my previous post).SamsAn - Wednesday, February 6, 2008 10:30 AM:
Please, note - i suspect you have a Workflow Promotion where Activity is Update Documents and State is Approved. It does not correspond to the standard solution and to the WFM and LCM. Thus the promote is failed. Please, confirm about the Workflow Promotion.
spolen - Wednesday, February 13, 2008 9:30 AM:
There are no work flow promotions in either Update Documents or State is Approved. Actually, I'm not seeing any workflow promotion on any states or paths. I am to the point of pulling my hair out. I have gone back through the training material that Aras provided when they came down here, and just would like a snap shot of what the original ECN workflow, lifecycle and workflow promotions SHOULD look like to see where the descrepancies lie in our system.
I appreciate all your help and sorry to keep going on this specific area, but I am stumped. Also the can add where you answered on the another question, I did am still having problems there also. This was an area that in the TOC under documents that an Aras Rep customized, and I am trying to replicate, but have been unsuccessful.
Thanks,
Sue
SamsAn - Wednesday, February 13, 2008 9:44 AM:
Please note, if you use 8.1 Innovator version then you can find Workflow Promotions under Administration in TOC. If a later version is used then see Promotions tab for an activity of a Workflow Map.spolen - Wednesday, February 13, 2008 10:30 AM:
We are using Innovator 8, not 8.1, and I have looked under the Workflow promotions and see no differences. Maybe I should have IT do a back up of our current database and reinstall the newer version?
Sue
SamsAn - Wednesday, February 13, 2008 10:42 AM:
Please, specify the exact version and the build (it is like "Version: 8.2.0; Build: 5419" in right lower corner of the login page).
Anyway, if you install newer version or reinstall the version used by you then the original behavior is supposed with Workflow/Lifecycle Maps for the installed database.
spolen - Wednesday, February 13, 2008 3:00 PM:
The version is 8.1.1; Build 5357, and I imagine what you are saying is even if we reinstall it will take on the same behavior as it did previously?
