Creating custom WTDocument numbering using two wizard steps

[RG_10893406]

The following steps which we have followed to create custom WTDocument numbering using two wizard steps

1. custom action and action model

2 Main wizard

3. Wizard step one and two

4. Error message 

com.ptc.core.components.jsp.JspUtils wcadmin - java.lang.NullPointerException java.lang.NullPointerException
at com.ptc.core.components.tags.components.InitializeItemTag.doTag(InitializeItemTag.java:371)
at org.apache.jsp.netmarkets.jsp.doc.Second_005fWizard_jsp._jspx_meth_jca_005finitializeItem_005f1(Second_005fWizard_jsp.java:1939)
at org.apache.jsp.netmarkets.jsp.doc.Second_005fWizard_jsp._jspx_meth_c_005fotherwise_005f1(Second_005fWizard_jsp.java:1903)
at org.apache.jsp.netmarkets.jsp.doc.Second_005fWizard_jsp._jspx_meth_c_005fchoose_005f1(Second_005fWizard_jsp.java:1808)

Earlier we have tried the same activity using single wizard page, it was working as expected.

[RG_10893406]

Please let us know if anybody aware of it.  

[Daniel_Ada]

In the first action try to set the windowType to "wizard step"

[RG_10893406]

Yes i tried the same, windowType to "wizard step". The issue is same

[Daniel_Ada]

https://www.ptc.com/cn/support/article/CS242901 , I tested your code, this article will fix the error, but the interface won't show anything, if you want to add custom steps when creating a document, I think you should modify the /netmarkets/jsp/document/create.jspf,this is just my personal suggestion, because I didn't come across a button that needs to create a custom document

[HelesicPetr]

Hi @Daniel_Ada 

Your issue is connected with a component that you would like to show but it does not work. 

Try @RG_10893406 suggestion based on the article

here is an example how to define it

<jca:initializeItem baseTypeName="wt.doc.WTDocument" operation="${createBean.create}" attributePopulatorClass="com.ptc.core.components.forms.DefaultAttributePopulator"/>

btw you can not define two same jsp steps. 

first step should define different jspf then  the seccond one create.jspf 

so I guess there could be the issue, where one jsp tries to overwrite something in the second one. 

Share the create.jspf and try to use own jspf page. 

PetrH