start workflow from Electronic Form

stefano.morando

i need to start a workFlow from an Electronic Form (added from tabs configuration as Generic Form).

Which is the best way to do this?

which package must i declare in the Process Builder (XFORM or dm_customdocument)?

i'm trying with adaptor. if i click on submit buttom, the system return "Error occurred processing submission: null"

Many Thanks

Find more posts tagged with

Comments

parasj

I had exactly the same error in this use-case and another use-case when I tried to trigger a workflow after a TaskSpace importer.

The reason for this error in the TaskSpace importer use-case is because the content transfer happens asynchronously - so the adaptor fires before the content has been transferred. This was acknowledged as a 'documentation defect' and product limitation by EMC.

Since the error message in both the use-cases above was the same - I concluded that something similar would be happening when a custom form is used under a Generic Tab - perhaps the new instances of the custom form (after you press the submit/save button) is created in a different thread and the adaptor is triggered in a different thread.

Let me know if you find anything different

stefano.morando

Hi Paras,

i found only a workaround.

first I use an importer to add the object,

after that i use anc action to start the workflow with the selected object

parasj

good to know you found a workaround that suits your business requirements.

Do you start the workflow manually after the document has been imported?

There is a post-processor adaptor (OOTB) that can start a workflow - but it suffers from the same limitation that I have described above.

Let us know

regards

- Paras

stefano.morando

Hi,

yes i start the workflow manually after the document has been imported.

documentum1

We used adaptor to start a workflow when submitting electronic form.

We created an adaptor of type 'document process' and in Initial parameter , set the Name as workflowTemplateId and value as the object Id of the process.

The adaptor is mapped on the form template properties > post submission.

It worked fine.

note : Type of form and package in the workflow should match to start the process.

parasj

Hi,

Are you able to describe your use-case in a little more detail.

The circumstances in which we hit this limitation were

1. post-processor adaptor in the doc-view form of a TaskSpace importer

2. when submiting a form displayed in a 'generic taskspace template'

-----

The post-processor start workflow adaptor works as expected when viewing a form/document that is already stored in the repository in a custom TaskSpace DocView form