Document View Component not shown in Task Component

albion

Hi all experts,

We are facing an unespected behaviour with forms to associate with activites.

We are using xCP Developer Edition 1.5

Se we have Process Builder 6.6 and Form Builder 6.6

We have created:

2 custom types, a folder (zz_folder) and a document (zz_document)

a Document View for zz_document

a Folder View and Folder content for zz_folder

everything is working fine untill now.

After that we have created a Process in process manager

The process has:

2 packages, one for zz_folder and one for zz_document

3 SDT

1 variable

packages are not mandatory

We have creared a "Initiate Process" template that maps the SDTs attributes and linked to the initiate activity, it works.

For the others manual activites we wented to use a custom form and we created a "Task" component in forms builder.

The issue that we are facing is that in step 5 (where you can associate a Document View to show the package content) the Document View list is totally empty and we can't even see the default DocView (DefaultDocView and DefaultHiFiDocView).

All the DocViews are installed.

In addition in process builder in the data tab we can't see any form to associate to a package.

One last thing that i guess is importan

If I create a package with a dm_document type instead of zz_document in the drop down list i can see a form: "DefaultDmDocument" that is an ELECTRONIC FORM not a Document View!!!

can someone give me some hints?

Thank you

Andrea

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

albion

SOLVED!!

Well this looks weird, while I was going to take some screenshot that helps me to explain the situation I got a solution.

I used to call my packages with name_pkg

we find that if the package name has the PKG letters inside the document view selection in step 5 of task component will not work

We made some test and tryed

name_pkg

name_pgk

name_kgp

namePKG

pkg_name

naPKGme

and as long that those 3 letters are present we will not see any DocumentView in the list.

renaming the package will magically make it works.

We will forward this information to the support since we alredy have an open case.

Thank you all for your interest

All comments

DCTM_Guru

In your task form, did you include docviewer control?

albion

Hi Johnny,

the problem is on the top of the task form template contents.

What we can't solve is that during the task form template we don't see any "Document View" template available while we should see at least the ootb DefaultDocView and DefaultHiFiDocView.

We have tried installing from scratch a new developer edition on a new virtual machine and in the new machine we can see them.

albion

SOLVED!!

Well this looks weird, while I was going to take some screenshot that helps me to explain the situation I got a solution.

I used to call my packages with name_pkg

we find that if the package name has the PKG letters inside the document view selection in step 5 of task component will not work

We made some test and tryed

name_pkg

name_pgk

name_kgp

namePKG

pkg_name

naPKGme

and as long that those 3 letters are present we will not see any DocumentView in the list.

renaming the package will magically make it works.

We will forward this information to the support since we alredy have an open case.

Thank you all for your interest