From 3504f680a73bb812574a7bb4f1b7f69ef36f45b4 Mon Sep 17 00:00:00 2001
From: Aaron Robinson <71637619+ARobinson26@users.noreply.github.com>
Date: Wed, 15 Nov 2023 15:16:24 +0000
Subject: [PATCH] Update ID and review date

---
 docs/standards/low-code-workflow-naming.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/standards/low-code-workflow-naming.md b/docs/standards/low-code-workflow-naming.md
index d0871e88..e0f3f02c 100644
--- a/docs/standards/low-code-workflow-naming.md
+++ b/docs/standards/low-code-workflow-naming.md
@@ -2,8 +2,8 @@
 layout: standard
 order: 1
 title: Low code workflow naming
-date: 2023-11-01 # this should be the date that the content was most recently amended or formally reviewed
-id: SEGAS-TBC # Set unique ID for standard
+date: 2023-11-15 # this should be the date that the content was most recently amended or formally reviewed
+id: SEGAS-00012 # Set unique ID for standard
 # use `tags: []` for no tags
 # Check https://ho-cto.github.io/engineering-guidance-and-standards/tags/ for existing tags
 # Note: tags must use sentence case capitalisation
@@ -67,4 +67,4 @@ Separating words using spaces makes workflow names more readable. In instances w
 
 Where a scope block is error handled, it should be prefixed with the word 'Try'. Where a scope block provides error handling, it should be prefixed with the word 'Catch'. This allows engineers to see easily, where error handling is applied within a workflow. Other naming standards should still be applied as normal.
 
----
\ No newline at end of file
+---