This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DEVELOPERS FORUM - Creating New Change Management Module

jsnosal - Tuesday, March 26, 2013 11:52 AM:

I'm working on creating a module called an EPO. We are planning on using this for running prototypes. Inside the part life cycle I added "Released to Prototype" and I changed "Released" to "Released to Production." 

 I would like to use the Impact Matrix from the ECO. I have modified some of the code to get it to work with the name EPO. I'm having an issue when I'm going from In Planning to In Work. The error says "All Old Number items must be in Released State when Action is set to Revise. Part #### is in Released to Prototype state." Do you know where I can find the code that I need to modify? Do you have any suggestions on an easier way to go about this? Thank you for your help. 



zahar - Tuesday, March 26, 2013 2:14 PM:

Creating new ECO based on Express ECO is not an easy task. Most of the states are hard coded in method PE_ChangeItemTransition



jsnosal - Tuesday, March 26, 2013 4:36 PM:

Yeah its been a pretty painful process so far. Below are all of the methods that I've modified so far. I'm guessing its the ChangeItemTransistion that is giving me problems. I just can't find where this alert is being called out.

 

RefreshImpactGridForceServer

 

Express ECO Grid Function          

Express ECO ImpactMatrix Handler         

PE_ChangeItemTransistion        

PE_ChooseCMOptions_API

PE_CheckChangeItemUsage     

PE_update_has_change_pending          

PE_AffectedItemFloat   

 



zahar - Tuesday, March 26, 2013 5:47 PM:

The error message that you talk about is probably come from function (in PE_ChangeItemTransistion  method)

void IAffectedItemValidationRules.Is_AffectedId_InReleasedState(ResultStatus status)

 

About methods that need to be modified, here is my list:

 

 

  • Express ECO Grid Functn
  • Express ECO ImpactMatrix Handler
  • PE_AddChangeItem
  • PE_AffectedItemFloat
  • PE_ChangeItemTransition
  • PE_CheckChangeItemUsage
  • PE_ChooseCMItem_API
  • PE_update_has_change_pending
  • RefreshImpactGridForceServerCall
  • restrictAffectedType.
  • restrictAffectedTypeOnServer 
  • PE_ChooseCMOptions_API

 

Additional place to change are:

 

  • form "PE_ChooseCMOptions"
  • and file under <Innovator>ClientSolutionsPLMscriptsChangesChanges.html

 

I don't know with version of Aras you are using, you need to know there is IR-019911 that fix some issue in PE_ChangeItemTransistion. 

 



jsnosal - Wednesday, March 27, 2013 11:42 AM:

Thank you for your help. The void IAffectedItemValidationRules.Is_AffectedId_InReleasedState(ResultStatus status) was the issue I was having. I'm thinking about scrapping this idea and going down a different avenue. This was a much bigger task then I was expecting it to be. We aren't using the ECN for anything right now, so I'm thinking about renaming it to the EPO. We just won't be able to use the impact matrix.

I will just need to figure out how to write to the parts affected when the ECN is released. I'm going to create a new property inside the part that is called production or prototype. Does this still mean I'm going to have to modify the item transition method within the Lifecycle or is there another way to handle this? 

What I'm looking for as the final result

Express ECO Released - Part property set to Production

ECN Released - Part property set to Prototype

 

Thanks again for your help. Its greatly appreciated.