We recently ran into an issue where a complex Visio was crashing our DMA. We’re currently transitioning the functionality into a Low Code App, but for the future we’re hoping to determine if there are certain features that should not be combined or are taxing on the system and should not be performed many times within a page.

Here is a list of all shape data fields we used. The specific Visio has already been checked and no apparent syntax errors or misuses were found:

• Multiple Pages
• InitVar
• Element
• Parameter
• Variable
• Tooltip
• Page
• Options: NoAlarmColorFill, HighlightStyle, AllowCustomIndex
• Children(ROW)/ChildrenSource/ChildrenSort/ChildrenPanel
• ChildType/ChildMargin
• SetVar/SetVarOptions
• SubscriptionFilter(VALUE) – using placeholders and *
• ParameterSubscriptionFilter(VALUE) – using placeholders and *
• Execute(SCRIPT/SET)
• Basic and Extended Conditionals (Show/Hide/Highlight/FillColor)
• Placeholders: [var:]/[param:]/[RegexReplace:]

Here is a description of how the fields were used:

• 2x Children=ROW for the same table w/ different VALUE Subscription filters w/ * wildcards and ChildrenSorted Display Key TableColumn
• A link to another Page of the same Visio that also performs a SetVar, nested w/in the outer Children=ROW
• Nested Children=ROW w/ a Subscription filter using the parent Children’s [tableIndex]
• Multiple parameter shapes w/in the inner Children=ROW group
• Nested RegexReplace statements using [parentTableIndex] w/in the inner Children=ROW group
• A parameter shape using a ParameterSubscriptionFilter (w/ a [param:] placeholder and AllowCustomIndex option) w/in the inner Children=ROW group
• A FilterComboBox SetVar using custom DisplayColumn/SetColumn and SubscriptionFilter w/ * wildcard (And a [sep::;] due to : in the values).
• An array session var using RegexReplace in SetVar to create a kind of ‘map’ separating entries w/ & and keys/values w/ < (SelectedStreams:[RegexReplace:[parentTableIndex]<[^&]+&|(?<![parentTableIndex].*)$,[var:SelectedStreams],[parentTableIndex]<[tableIndex]&])
• A shape w/in a nested Children=ROW object that contains a Shape SetVar (See prior bullet), Tooltip, Parameter Basic Condition (FillColor) and Highlight extended condition (Changing Line color/width to match a single Options=HighlightStyle shape).
• Buttons w/in a Children=ROW that have a Tooltip, NoAlarmColorFill option and triggers a script with Execute, using [tableIndex] as an input parameter, that updates a session variable. Uses NoCofirmation option.
• A Button that triggers a script with Execute, using a session variable as input, that makes an API call and updates element parameters as well as session variables. Uses NoCofirmation and NoSetCheck options.
• Shapes w/in Children=ROW inner groups that show/hide based on Session Variable (Basic Condition) and table parameter (Extended condition)
• NOTE: Most Children=ROW groups are referencing Partial Tables that contain 100s+ of entries, filtered down to ~10 rows using a SubscriptionFilter typically with a param/var placeholder and * wildcard matcher.

Some examples of what I’m interested in learning would be “Visios are inefficient when performing many Regex operations on a single page” or “You should not nest ROW Children beyond 1 level”, etc. but any advice of how to optimize or prevent slow load times in the future would be greatly appreciated.

Thanks!