Chapter 8: Scoping with Try/Catch Error Handling
As the complexity of the logic grows, it would be sensible to divide the flowchart into different sections. The scope feature allows you to do this, reducing clutter on the flowchart. Output from a scope can also be obtained for debugging purposes. The scope feature has a further use of being able to focus the developer's attention on problematic code. Output and error messages from this section can be obtained and debugged, with further remedial actions taken when errors do occur.
In this chapter, you will learn how to do the following:
- Create a series of scope sections to simplify the logic into higher levels, enabling the overall flowchart to be easier to understand
- Manipulate and move existing actions into a scope to contain data in a sectional way
- Examine a Try scope's output for debugging data
- Triage error data to ensure the logic is more robust by adding extra logic when things go wrong