Petals View

"En cours" status when an error occurs on a non-terminal flow step

Details

  • Type: Improvement Request Improvement Request
  • Status: New New
  • Resolution: Unresolved
  • Affects Version/s: 1.0
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    PetalsView displays the status "en cours" for non terminated flows as well as on the ones where one step is in error.

    The operator is required to go on the details of the flow to determine if it is really "en cours" or in error, which is a time consuming process. Simply display "error" when one step of a flow is in error would be a better idea.

    Show
    PetalsView displays the status "en cours" for non terminated flows as well as on the ones where one step is in error. The operator is required to go on the details of the flow to determine if it is really "en cours" or in error, which is a time consuming process. Simply display "error" when one step of a flow is in error would be a better idea.
  • Environment:
    PetalsView 0.9.3-SNAPSHOT
    Petals ESB 3.0.5
    Petals-SE-Notifications 1.0.2
    Petals-SE-KPI 1.0.2

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Christophe DENEUX added a comment - Tue, 31 Aug 2010 - 18:32:16 +0200 - edited

In my mind, it's better to be able to set an error level on each activity:

  • optional: the flow is flagged as pending,
  • critical: the flow is flagged as error
Show
Christophe DENEUX added a comment - Tue, 31 Aug 2010 - 18:32:16 +0200 - edited In my mind, it's better to be able to set an error level on each activity:
  • optional: the flow is flagged as pending,
  • critical: the flow is flagged as error
Hide
Permalink
Olivier Fabre added a comment - Tue, 31 Aug 2010 - 18:23:27 +0200

I think a solution could be to define the "Reception" step (first step) as the end step too. And to put this step in error if a error status or fault is recieved from an other step of the process.

Show
Olivier Fabre added a comment - Tue, 31 Aug 2010 - 18:23:27 +0200 I think a solution could be to define the "Reception" step (first step) as the end step too. And to put this step in error if a error status or fault is recieved from an other step of the process.
Hide
Permalink
Christophe DENEUX added a comment - Tue, 31 Aug 2010 - 17:57:38 +0200

Ok, and what is your proposal to this use case ?

Show
Christophe DENEUX added a comment - Tue, 31 Aug 2010 - 17:57:38 +0200 Ok, and what is your proposal to this use case ?
Hide
Permalink
Olivier Fabre added a comment - Tue, 31 Aug 2010 - 17:39:12 +0200

In some cases, you could have steps in error state but your flow isn't in error (non major steps). So we have decided to let users choose a step as final step. It's this step that drives the flow status. It's the responsability of the flow designer to choose the right step that will govern flow status.

Show
Olivier Fabre added a comment - Tue, 31 Aug 2010 - 17:39:12 +0200 In some cases, you could have steps in error state but your flow isn't in error (non major steps). So we have decided to let users choose a step as final step. It's this step that drives the flow status. It's the responsability of the flow designer to choose the right step that will govern flow status.

People

Dates

  • Created:
    Tue, 24 Aug 2010 - 16:28:54 +0200
    Updated:
    Tue, 31 Aug 2010 - 18:32:33 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.