Need Help with Extracting and Logging Errors in a ReFramework Project

Help Something Else
, , ,
1

Hi everyone,

I hope you’re all doing well. I’m currently working on a project using the ReFramework, and I’ve encountered a challenge that I’m hoping to get some guidance on.

In my project, I’m trying to implement a feature where any errors that occur during the execution of the workflow are extracted and logged into a variable. This logged error, along with its unique ID, will then be sent to a database for better tracking and control. Additionally, I’d like to set up an email notification system to alert both me and my partners whenever such an error occurs.

  1. I’m using the ReFramework, and my understanding is that errors are typically logged in the Output panel or written to the Orchestrator logs. However, I want to capture these errors programmatically in my workflow.
  2. Once the error is captured, I need to store it in a variable along with a unique identifier.
  3. I also want to understand how to send this error information to a database for storage and easy access.
  4. Lastly, I’d like to implement an email notification system that alerts me and my partners whenever such an error is logged.

I’ve looked through the ReFramework documentation and some related resources, but I couldn’t find a clear solution for programmatically capturing and logging errors in a variable. I’m not sure how to approach extracting the error details and associating them with a unique ID for database storage. As for the email notifications, I’m uncertain about the best practices to implement this within the ReFramework structure.

Thank you all in advance for your time and support. Looking forward to your valuable insights!

2

@Marc_Font

  1. two places you would need to capture the error…one is in process transaction state and other in end process state
  2. In the settransactionstatus.xaml you will have 3 sequences success,bus excep and sys excep…use the exception sequence to get the details about the exception and load to database …also in same sequence you can send mails
  3. For database you need to use datatable related activiites. exception.message will give the message and exception variable contains bunch of other options as well like getting stack trace etc…which can be leveraged
  4. One more place is in end process where the initialization and get transaction state exceptions cna be caught…in the main.xaml variables you will have bus excep and sys excep variables which can be used to capture the info in end process just like mentioned in step 2

Hope this helps

cheers

3

Hi @Anil_G !!

Thanks for the recommendations, that’s what i though that i would need to do,

I’m trying this and i come back if something doesn’t work.

Thanks!
cheers :smiley:

1 Like
4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.