Business Process Management Software Resources

Catching errors using error intermediate events For BPDs, you can attach an error intermediate event to an activity and connect that event to an error handling flow or activity. The attached error event is known as a error boundary event. To determine whether to use error immediate events, consider the following points: If an error occurs while a process is running an activity with an attached error event at the boundary, the process flows along the sequence line that is attached to the error event. Errors are handled in the flow and then proceed with the normal processing. Error intermediate events must be attached to an activity. You can have multiple error events for an activity, but only one catches the error. Consider specifying the error data to catch specific errors, filtering on the error code for the types of errors that are caught, and mapping to a variable after the errors are caught. When all errors are caught, or if only an error code is specified, the error data is captured in an XMLElement in the tw.system.step.error variable. To handle validation errors in a save service for shared business objects, catch the error BPMBOSaveFailedError that is available in the list of specific errors. This error is only available on nodes that save the execution context, either automatically (for example, coaches) or explicitly by enabling the Save execution context option Catching errors using error event subprocesses An event subprocess is a specialized type of subprocess that is not part of the normal sequence flow of its parent process. An error event subprocess is an event subprocess that contains an error start event. The event subprocess is not connected by sequence flow and runs only if the start event in the event subprocess is triggered. You can use error event subprocesses to handle errors in your BPD. To determine whether to use error event subprocesses, consider the following points: Define a readable process by locating the error event in the event subprocess instead of defining it in the process. To reuse the error-handling flow for multiple tasks in your process, use event subprocesses. To reuse an error-handling flow using attached events, you must attach an intermediate event for each of the tasks and then connect those events to the error-handling flow. Define data objects that you can access only from within the event subprocess. You can define only those data objects that belong to a subprocess. The parent process is not cluttered with unnecessary variables.

Go to reports / app specific reports then choose the app to get reports specific to that app. you can then create a custom report and save the template to be ran at any time. It can then be exported and brought into excel if necessary. As an example, we create reports and drop in an Excel template and then summarize in another tab before importing into Quickbooks. For all apps go to reports / All items and drill into what you need. You can then export those reports as well.

I used this video which helped with customized reports. https://help.kissflow.com/en/articles/364480-create-a-new-report Hope this helps!

i'm a Financial Advisor and I make $60,000 monthly in passive income without a blog, without investing on ads or building my authority on social media. It took me around 6 months to make consistent money (and not lose what I made). I will teach you how to trade and use a crypto trading platform that guarantees successful trades and help you stay protected and avoid losing money. Irrespective of the amount you wish to start with, Bitcoin and digital earnings have been established to be a very good means of generating passive income. You can get very rich investing in Crypto. If you are interested to know how I make so much money from crypto trading you can write me a message via WhatsApp +1 (484)401 9355 I am always here to help anyone that wants to pursue their dreams to be wealthy in this lifetime. Good Luck!