Workflow error customize
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2012 08:26 AM
How is it possible to change the text in the pop-up window, when workflow can't move to the other transition.
Here is an example of what I get in pop-up, when there is an error during action in workflow
Also is it possible to have different texts, for different exceptions inside the same action.
So for example in one of actions in my workflow, this exception could happen because of missing metadata on document, or beacuse
we are moving file during action in a folder that already contains this name. How do I differentiate between these 2 possible errors ?
Thank you for your answers.
Here is an example of what I get in pop-up, when there is an error during action in workflow
org.alfresco.service.cmr.workflow.WorkflowException: 09010602 Failed to signal transition approve from workflow task jbpm$3264.
So how does one change this text, I am especially interested when the exception comes in javascript code for an action.Also is it possible to have different texts, for different exceptions inside the same action.
So for example in one of actions in my workflow, this exception could happen because of missing metadata on document, or beacuse
we are moving file during action in a folder that already contains this name. How do I differentiate between these 2 possible errors ?
Thank you for your answers.
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2012 04:32 AM
Hello,
the main problem here is that any exception from inside the workflow, wether it is a script exception or service exception, is ultimately turned into a generic JBPM exception which looks like this. Along this way, all detail information is lost, so the message is always similar and without any added value. Apart from modifying the core Alfresco JBPM integration, I see no way to pass the actual exception details to the client in an understandable message.
Regards
Axel
the main problem here is that any exception from inside the workflow, wether it is a script exception or service exception, is ultimately turned into a generic JBPM exception which looks like this. Along this way, all detail information is lost, so the message is always similar and without any added value. Apart from modifying the core Alfresco JBPM integration, I see no way to pass the actual exception details to the client in an understandable message.
Regards
Axel
