{'fraction_non_alphanumeric': 0.018261504747991233, 'fraction_numerical': 0.0, 'mean_word_length': 5.523809523809524, '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}}
Office Activity Procedure Exception Handling Realization Difficulties

Office activity procedure automation is getting very popular in major organizations. During the automation then workflow method is chosen frequently, because of its possibility to reflect real world business processes in a transparent and informative way. By automating such activities, organization gains a possibility to share resources between distant company departments, shortens the activity fulfillment time, and reaches work efficiency. It’s a pity, but workflow doesn’t support real world deviations, which often occur during document or project preparation. Every possible exception or deviation must be foreseen during the process build-time. The most difficult to solve are run-time exceptions. They are difficult to catch, their impact to the process can be determinant to the final goal and they irritate the user most of all. This paper focuses on the business process, modeled using workflow exception handling, and exception impact to the business process and user reliance on the system. The proposed decomposed workflow method shows how an office activity automation application could reach flexibility and support run-time exceptions. Combining the solutions of all mentioned above problems into a consistent solution, the exception handling could be achieved in a flexible way.