Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Low Code Workflow Naming Standard #338

Closed
3 tasks done
ARobinson26 opened this issue Nov 7, 2023 · 0 comments · Fixed by #339
Closed
3 tasks done

Low Code Workflow Naming Standard #338

ARobinson26 opened this issue Nov 7, 2023 · 0 comments · Fixed by #339
Assignees

Comments

@ARobinson26
Copy link
Contributor

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

  • I have looked at the writing-a-standard standard and think this would meet the standard
  • I have looked through our existing standards and think this is not covered elsewhere
  • I have checked through the open issues on the repository and this standard has not already been suggested
@ARobinson26 ARobinson26 self-assigned this Nov 7, 2023
@ARobinson26 ARobinson26 linked a pull request Nov 7, 2023 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant