New Global Variable -- "RS_Previous_Step"

Idea ID 1634163

New Global Variable -- "RS_Previous_Step"

OO has the ability to use some standard (global) variables, like RS_Previous_Transition_Annotation and execution_userid. We would like a new standard variable called something like "RS_Previous_Step_Name". This variable should contain the name of the previous step that was executed. This will help in standardizing exception handling in OO workflows.

Tags (1)
9 Comments
Outstanding Contributor.
Outstanding Contributor.

Hi,

This sounds like a nice idea too. Can you provide more info around how exactly your are standardizing the error handling today and how exactly the step name will help you.

If can only assume it is capturing the step name and the error too but I want to make sure I have the entire picture

Thank you,

Account_Closed
Not applicable

Hello, I request that the author follow the user-story format as laid out in the submittal guidelines - it is possible to edit the question.

Account_Closed
Not applicable
 
Super Contributor.
Super Contributor.

@Rabobank 

Is your aim to create the equivalent of a stack trace?  ie - capture the name of the steps that failed and return them (somehow) to your operations people?

 

Using RS_Previous_Transition_Annotaiton allows you to return exception information from flows by adding a description onto the transition (which allows you to return the reason for the failure).  The only detriment to this is that if you delete the transition or drag it to another step, the values on that transition are lost.   I've seen many flows get broken because a developer had to add a new step, moved some operations around and then lost all of the error handling on the flow because the transitions had changed.

Micro Focus Expert
Micro Focus Expert

Fully aligned with @Rabobank on this.  When developing workflows today it's very hard to report pack the step that failed. 

What some authors are doing when the flow fails we take the run id and try to query for details via REST API.  Still, this is error prone and creates authoring issues that a MAGIC variable like step_name will solve.

Respected Contributor.
Respected Contributor.

@David Fidler 

yes sort of, we want to use the variable in combination with a variable like "RS_Current_Flow" (another ER is made for this feature) variable. This way we can standardise our exception handling. With the following format of exception messages we always know where to look if an error occured during execution. 

Flow: ${Flow name}
Step: ${Step name}
Error: ${Error message}

The mentioned issue about broken transitions is fixed in our current OO version (10.70)

Frequent Contributor.
Frequent Contributor.

@Thijs de With - I think that this is an excellent idea.  We log currently log messages to GrayLog and being able to get this information without having to set it on every flow would be really useful.

 

 

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Under Consideration

The idea received enough support from the community to be considered for prioritization in our future development planing.

We will continue to monitor the idea so please expect further updates.

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Accepted

This idea is accepted to be implemented as part of additional global variables support for CloudSlang based flows.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.