Our engineering standards are the things that we expect engineers to do. Look at the 'writing a standard' standard and provide some brief information below
What is the standard you are suggesting?
Naming conventions and standards for Low Code Workflows, such as Azure Logic Apps, Power Automate and AWS Step Functions.
What would be the benefit to the Home Office of adopting this standard?
Standardisation of how to name variety of components within low-code workflow technologies. Primarily benefits maintainability by making things easier to read/understand.
How might people follow it
Ensure components such as workflow names, actions/steps, scope blocks etc are all named consistently and appropriately.
Additional information
Please confirm the below
[x] I have looked at the writing-a-standard standard and think this would meet the standard
[x] I have looked through our existing standards and think this is not covered elsewhere
[x] I have checked through the open issues on the repository and this standard has not already been suggested
Our engineering standards are the things that we expect engineers to do. Look at the 'writing a standard' standard and provide some brief information below
What is the standard you are suggesting? Naming conventions and standards for Low Code Workflows, such as Azure Logic Apps, Power Automate and AWS Step Functions.
What would be the benefit to the Home Office of adopting this standard? Standardisation of how to name variety of components within low-code workflow technologies. Primarily benefits maintainability by making things easier to read/understand.
How might people follow it Ensure components such as workflow names, actions/steps, scope blocks etc are all named consistently and appropriately.
Additional information
Please confirm the below