Page 1 of 1

5.1.8 Template problems?

PostPosted:Thu Dec 22, 2011 6:48 pm
by Nigel.pvg
Hello, initially I was going through the process to create a pdf template, register the property group and build the xml for it. Then on testing it was not working as I expected, so I implemented the Sample Template Form by creating the property group and xml. I used the uploaded file, and it also does not prompt for the input data when you use "Create from template".

Can anyone else confirm this behaviour or suggest what might be missing? Due to the FreeMarker update maybe?

Re: 5.1.8 Template problems?

PostPosted:Fri Dec 23, 2011 3:03 pm
by jllort
I've tested in our online demo without major problems, could you test there ?

Re: 5.1.8 Template problems?

PostPosted:Fri Dec 30, 2011 3:28 pm
by Nigel.pvg
Same behaviour, maybe it is a Chrome issue.

Tried the other template that is currently in the folder and it works fine, so it is not Chrome. I also can not verify that the tpl sample property groups have been added/exist in the demo, and I am not aware that it will give an error if they are missing.

Re: 5.1.8 Template problems?

PostPosted:Sun Jan 01, 2012 10:08 pm
by jllort
have you tested the property group ? and assigned to the document in template ? if it's the case attach the involved files here and we'll take a look about what could be happening.

Re: 5.1.8 Template problems?

PostPosted:Tue Jan 03, 2012 3:17 pm
by Nigel.pvg
To make things simple I am using the demo tpl from the wiki.

Assign to the template... maybe this is what I am missing, I do not recall reading about this step. Will re-read and check for it.

Re: 5.1.8 Template problems?

PostPosted:Wed Jan 04, 2012 4:17 pm
by Nigel.pvg
Assigning the property group to the template was exactly what I was missing!

It is curious as to why you would have to assign the property group to the templates as well as using the field scope nomenclature; unless this is a legacy assignment. On creating from template, it should be easy enough to query the database for the property group and return a notice if not found and maybe self index if found? Just a thought.

Re: 5.1.8 Template problems?

PostPosted:Thu Jan 05, 2012 4:31 pm
by jllort
Assigning property group or several to templates are indicating which data must be collected, that's the reason, it's more easiest and we're using at same time the same presenter wizard, that's the idea.

Re: 5.1.8 Template problems?

PostPosted:Mon Jan 09, 2012 3:50 pm
by Nigel.pvg
Does that not overlap the purpose of the property group name and group label nomenclature?

okp:tpl
okp:tpl.name

Sorry for the additional questions on the behaviour on this issue, it is just a strange concept to me as it seems inheritance needs to be assigned 3 times between the definition of the Property Group, the XML structure, and then additionally being required to manually assign the inheritance.

I do understand the purpose of the first two, but if a document is tagged as a template and its revision or creation date has changed, why not just automatically parse the template for the group name and label to index the data to be collected?

Re: 5.1.8 Template problems?

PostPosted:Tue Jan 10, 2012 7:42 am
by jllort
Template is registered by administrator, not by change date, could be some error or still not finished ( that's the idea why is on administrator hand decide to register it ).

Be care, first probably is okg: ( g -> group ) the second probably will be okp: ( p -> property into the group of properties ).