{'fraction_non_alphanumeric': 0.02054054054054054, 'fraction_numerical': 0.0, 'mean_word_length': 5.256756756756757, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
The method for e-business exception handling

Business success depends on strong relationships with clients. As information technologies keep evolving and people entrust them with more and more every day tasks, e-business is becoming one of the quickest and easiest ways to reach the consumer. As e-business processes are constructed using workflow methods, which usually lack real-world deviation handling capabilities, exception handling is becoming one of the most important aspects of these processes. Of these exceptions, the most dangerous are run-time exceptions and deviations. They are difficult to catch, their impact to the process can be detrimental to achieving the process' goals, and of course they are annoying to users. The purpose of this paper is to discuss an approach for a universal exception handling mechanism, which would help achieve business process transparency and exception handling flexibility.