cancel
Showing results for 
Search instead for 
Did you mean: 

After checkin activation failed due to code has some erros

Former Member
0 Kudos

Hi

we have developed new DC and tested sucessfully and then checkin the activity sucessfully .after that activation failed due some errors in the code.when we build local no errors found. errors as follows

-


dgen] [Error] com.hr.mss.term.Term --> ContextModelNode Zhr_Nter_Wd_Ucom_Input [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)

[wdgen] [Error] com.hr.mss.term.Term --> ContextModelNode ucomd_Output [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)

-


Here are the questions

1.If we create new activity and fix this errors and able to checkin and activate?

2.is all the changes done in old activity also moved when import it into Quality and production system with new activity? if not how to do it?

because we have done lot things in this activity like creating models mapping and coding part.

please advice us how to proceed ....

Thanks in advance

Gopal

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

>> 1.If we create new activity and fix this errors and able to checkin and activate?

Yes, you will be able to checkin and activate. When you activate your new activity containing the fixes, NWDS will indicate that there are predecessor activities which are not yet activated. So you will be forced to activate both the old and new activity together.

>> 2.is all the changes done in old activity also moved when import it into Quality and production system with new activity? if not how to do it?

Predecessor checks will ensure that the old activity is also transported along with the new one. You don't have to worry about this in any way.

- Girish

Former Member
0 Kudos

Thanks Girish.

Problem solved.

Answers (0)