High Fidelity Form problem

Hi All,

My aim is to update and then store a hi-fi form in docbase so that the user can see the form in Taskspace's default hi-fi form view.

I created and installed a high fidelity form using Form builder. All my versions are 6.5 SP2. I then want to use that form in a workflow and read/write data from/to that hi-fi form. The workflow has a package which is of the type "XML Instance" for this hi-fi form. First I use "FTP Read" activity to get the hi-fi form in the 'XML Instance' type package of the work flow from a specific location. I attach the hi-fi form in the content->data node of the 'XML Instance' data-type package in the activity 'FTP Read' and give the format as 'odt'. Then in the source pane of the activity "Process Data Mapping" I try to read some value from the form elements to some process variables. But when I debug the process, the process variables are still empty. I can see the content of the 'XML Instance' package in debug mode and the hi-fi form is present there.

Again, when I try to write data using "Process Data Mapping" activity (from process variable to hi-fi form elements), (this hi-fi form imported by the 'FTP Read' activity in the previus step as in picture), I get the following error .

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Caused by: DfException:: THREAD: http-0.0.0.0-9080-5; MSG: Error in setting value of package schema data : /Packages/abb_form_view/content/data/[-1,S]ABBForm/[1,S]Document_Number, 09de75d1800047b9; ERRORCODE: ff; NEXT: null
at com.documentum.bps.utils.PackageUtils.setContentInfo(PackageUtils.java:648)
at com.documentum.bps.utils.PackageUtils.setNodeValue(PackageUtils.java:604)
at com.documentum.bps.utils.PackageUtils.setPackageNodeValue(PackageUtils.java:491)
at com.documentum.bps.utils.PackageUtils.setPersistentNodeValue(PackageUtils.java:431)
at com.documentum.bps.utils.DocbaseUtils.setProcessDataValue(DocbaseUtils.java:199)
at com.documentum.bps.pkgcopy.runtime.PackageCopyService.setInputNodeValue(PackageCopyService.java:42)
at com.documentum.bps.outbound.AbstractService.executeInputMappingRules(AbstractService.java:146)
at com.documentum.bps.outbound.AbstractService.execute(AbstractService.java:66)
... 30 more
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:98)
at com.documentum.bps.utils.XMLUtils.parse(XMLUtils.java:221)
at com.documentum.bps.utils.XMLUtils.parse(XMLUtils.java:216)
at com.documentum.bps.utils.PackageUtils.getContentAsDocument(PackageUtils.java:251)
at com.documentum.bps.utils.PackageUtils.getDocumentFromContext(PackageUtils.java:215)
at com.documentum.bps.utils.PackageUtils.setContentInfo(PackageUtils.java:637)
... 37 more

_---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Strange is that If I do not use the 'FTP Read' activity and just attach on the fly the hi-fi form in the 'XML Instance' package in the 'Process Data Mapping' activity, then it can write to the form fields. But there is one problem in that case also. I save this form as a dm_xfm_instance in the docbase for users to see this hi-fi form from Task Space's 'Default hi-fi form view'. When I see this hi-fi form in taskspace, I see it just as a xml file in the hi-fi form view template and not as a hi-fi form. I want to see it as hi-fi form.

Please help.

Thanks a lot,

Raj Sen

untitled.bmp

Find more posts tagged with

Comments

DCTM_Guru

I have noticed that the debugger doesnt work in all situations. Have you tried just running the workflow in normal mode?

"When I see this hi-fi form in taskspace, I see it just as a xml file in the hi-fi form view template and not as a hi-fi form. I want to see it as hi-fi form. "

Did you associate this form with the manual activity in the process? There is option to associate form at the bottom of the first tab (I think its called General) for a manual activity.

rajarshisen

Hi Johnny,

Thanks a lot for your prompt and valuable help!.

I tried to run the workflow in normal mode as well. Same exception was getting thrown whenever the 'Process Data Mapping' activity, which maps data from process variable to high fidelity form's elements, was getting executed. I have tried with two kind of 'Process Data Mapping' activity templates.

Map the data from hi-fi form to process variables. (in this case the process variables are populated with blank value but workflow does not throw error)
Map the data from process variable to hi-fi form of the package ('XML Instance')content. In this case, the Saxparser exception is thrown by the work flow.

I created a 'task template' type of taskspace form from the Form builder and attached the manual activity of the process to that form. So when the user opens the manual activity in taskspace, he should expect to see the hi-fi form on the view window pane in taskspace. But the document he views is a xml content. I have opened the content of the document through back end dfc. And it actually is a simple xml document. So what the user sees is correct.

My question is when I specify an installed hi-fi form as the content of a 'XML Content' type package, does not that automatically create a hi-fi format form? I also mentioned the format of the content as 'odt' in the activity and it correctly shows the format as well. Only the content created is a xml file and not a hi-fi document.
Also why cannot I read data from a hi-fi form added as a 'XMl Instance' package to the workflow?

Now I am confused. I was trying to use a similar concept EMC's Grant Management Application uses. The Create Grant Request workflow was reading from a hi-fi form which was attached to the work flow as a package and then setting the attributes of grant_request object from the hi-fi form data. I tested that workflow in the same environment and it worked perfectly. But when I try to create a workflow using the same concept, it does not copy the data from the form. I opened the hi-fi form in Open Doc and the datastructure also looks same like the Grant Application form.

Please help.

Thanks a lot,

Raj Sen

DCTM_Guru

"I created a 'task template' type of taskspace form from the Form builder and attached the manual activity of the process to that form. So when the user opens the manual activity in taskspace, he should expect to see the hi-fi form on the view window pane in taskspace."

- Actually, by attaching task template form, when the user opens the manual activity, he should see your cusotm task template form. He wont see the hi-fi form until he open/clicks on the task.

- Have you tried associating the hi-fi form to a normal manual activity (without custom task template form)?

rajarshisen

Hi Johnny,

Thanks a lo for your prompt reply. I tried attaching the hi-fi form to a normal manual activity. I also save the hi-fi form workflow package (as dm_xfm_instance) in a folder for the users to view that. So if the user opens the default 'My Folder' view in the Task space and navigates to the folder and selects the form, they should see the hi-fi form saved in that folder. What they see is a xml document when they click on the hi-fi form. This form was created if I get rid of the 'FTP Read' activity and just attach a hi-fi form in the content-data node of the 'XML Instance' type package of the workflow. The form attached in the workflow is the hi-fi form, but when it's saved it's a xml document.

I have attached two pictures to show what I mean by this.

Thanks again for your support.

Raj Sen

DCTM_Guru

Does this happen only when you try to import Hi-fi form? What happens if you try to create one from template? See the "Create a new High Fidelity form" section in the Taskspace Configuration guide.

rajarshisen

Hi Johnny,

I finally managed to show the hi-fi form in the correct format. The mistake I was doing was that I was not the form type to my hi-fi form in the package definition of the workflow. Once I did that, it worked like a charm. Thanks a lot for your time and prompt support every time.

Thanks a lot,

Raj Sen

DCTM_Guru

Hi Raj,

Thanks for posting your resolution as well. This way anyone who encounters a similar problem can search on your post for the resolution.

-Johnny