SecureX Orchestration Workflow Analyzer analyzed your last commit. An itemized list of issues found in checks that ran are grouped by workflow name (click â–¶ to expand) & presented below as 'tasks' for your review.
🎯 Pro Tip: You can covert each task on this list into an issue of it's own to break down work and to assign to others. Check out this video for more!
TE-CreateNetworkInstantTest [link]
### 😞 Failed
- [ ] 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
- [ ] Targets - Failed - Workflows should not have any hard-coded targets
- [ ] Account Keys - Failed (there should not be any hard-coded account keys) -
### 😶 Warnings
- [ ] Description datatype.string - No description - All variables should have a meaningful description to help the end user understand its purpose and, if a value needs to be provided, where the user should get it
- [ ] Test Name datatype.string - No description - All variables should have a meaningful description to help the end user understand its purpose and, if a value needs to be provided, where the user should get it
- [ ] Output datatype.string - No description - All variables should have a meaningful description to help the end user understand its purpose and, if a value needs to be provided, where the user should get it
- [ ] Port datatype.integer - No description - All variables should have a meaningful description to help the end user understand its purpose and, if a value needs to be provided, where the user should get it
- [ ] Parse Test ID corejava.jsonpathquery - "Continue Workflow Execution on Failure" is not checked - If the JSON path query you look for isn't found, the activity will fail and your workflow will fail with it. If you want to avoid this, you can check continue on failure and use a Condition Block to check if the path query was successful
### 🥳 Passed
- [x] Description - Passed -
- [x] Workflow Instance Cleanup - Passed - "Clean up after successful execution" is not checked (which is what we typically recommend)
- [x] Account Key - Passed - The default account key for whatever target the parent workflow provides at runtime will be used
- [x] Global Variables - Passed - The workflow does not appear to be using any global variables
- [x] Custom Table Types - Passed - The workflow does not appear to be using any custom table types
SecureX Orchestration Workflow Analyzer analyzed your last commit. An itemized list of issues found in checks that ran are grouped by workflow name (click â–¶ to expand) & presented below as 'tasks' for your review.
TE-CreateNetworkInstantTest [link]
### 😞 Failed - [ ] 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 - [ ] Targets - Failed - Workflows should not have any hard-coded targets - [ ] Account Keys - Failed (there should not be any hard-coded account keys) - ### 😶 Warnings - [ ] Descriptiondatatype.string - No description - All variables should have a meaningful description to help the end user understand its purpose and, if a value needs to be provided, where the user should get it - [ ] Test Name
datatype.string - No description - All variables should have a meaningful description to help the end user understand its purpose and, if a value needs to be provided, where the user should get it - [ ] Output
datatype.string - No description - All variables should have a meaningful description to help the end user understand its purpose and, if a value needs to be provided, where the user should get it - [ ] Port
datatype.integer - No description - All variables should have a meaningful description to help the end user understand its purpose and, if a value needs to be provided, where the user should get it - [ ] Parse Test ID
corejava.jsonpathquery - "Continue Workflow Execution on Failure" is not checked - If the JSON path query you look for isn't found, the activity will fail and your workflow will fail with it. If you want to avoid this, you can check continue on failure and use a Condition Block to check if the path query was successful ### 🥳 Passed - [x] Description - Passed - - [x] Workflow Instance Cleanup - Passed - "Clean up after successful execution" is not checked (which is what we typically recommend) - [x] Account Key - Passed - The default account key for whatever target the parent workflow provides at runtime will be used - [x] Global Variables - Passed - The workflow does not appear to be using any global variables - [x] Custom Table Types - Passed - The workflow does not appear to be using any custom table types