The following errors were analyzed in the last commit
[ ] In TE-CreateNetworkInstantTest - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-CreateNetworkInstantTest - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-CreateSIPInstantTest - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-CreateSIPInstantTest - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-CreateSIPInstantTest - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-GetDetailedNWPathTrace - Custom Table Types - Failed - We do not recommend using tables to pass data between objects as they're inefficient and don't always scale well. It's better to exchange JSON instead
[ ] In TE-GetE2ENetworkMetrics - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-GetE2ENetworkMetrics - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-GetE2ENetworkMetrics - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-InstantTestRerun - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-InstantTestRerun - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-InstantTestRerun - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-ListTests - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-ListTests - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-ListTests - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-NetworkPathVisualisation - Custom Table Types - Failed - We do not recommend using tables to pass data between objects as they're inefficient and don't always scale well. It's better to exchange JSON instead
[ ] In TE-QueryAgentID - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-QueryAgentID - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-QueryAgentID - Account Keys - Failed (there should not be any hard-coded account keys) -
The following errors were analyzed in the last commit
[ ] In TE-CreateNetworkInstantTest - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-CreateNetworkInstantTest - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-CreateNetworkInstantTest - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-CreateSIPInstantTest - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-CreateSIPInstantTest - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-CreateSIPInstantTest - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-GetDetailedNWPathTrace - Custom Table Types - Failed - We do not recommend using tables to pass data between objects as they're inefficient and don't always scale well. It's better to exchange JSON instead
[ ] In TE-GetE2ENetworkMetrics - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-GetE2ENetworkMetrics - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-GetE2ENetworkMetrics - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-InstantTestRerun - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-InstantTestRerun - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-InstantTestRerun - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-ListTests - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-ListTests - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-ListTests - Account Keys - Failed (there should not be any hard-coded account keys) -
[ ] In TE-NetworkPathVisualisation - Custom Table Types - Failed - We do not recommend using tables to pass data between objects as they're inefficient and don't always scale well. It's better to exchange JSON instead
[ ] In TE-QueryAgentID - Target - Failed - All atomic actions should have their target set to "Specify Target On Workflow Start". This allows the atomic to be more portable since the workflow using it can specify the target
[ ] In TE-QueryAgentID - Targets - Failed - Workflows should not have any hard-coded targets
[ ] In TE-QueryAgentID - Account Keys - Failed (there should not be any hard-coded account keys) -