SEGAS-00012 - Low code workflow naming

More information about SEGAS-00012

More information can be found on the engineering website about SEGAS-00012

Does this codebase pass the following requirement: Naming conventions MUST be consistent?

More information about Naming conventions MUST be consistent

More information can be found on the engineering website about Naming conventions MUST be consistent

Does this codebase pass the following requirement: Acronyms or uncommon abbreviations MUST be defined in a central or project glossary?

More information about Acronyms or uncommon abbreviations MUST be defined in a central or project glossary

More information can be found on the engineering website about Acronyms or uncommon abbreviations MUST be defined in a central or project glossary

Does this codebase pass the following requirement: Workflow, action step and scope block names MUST be descriptive and convey the purpose or objective?

More information about Workflow, action step and scope block names MUST be descriptive and convey the purpose or objective

More information can be found on the engineering website about Workflow, action step and scope block names MUST be descriptive and convey the purpose or objective

Does this codebase pass the following requirement: Workflow, action step and scope block names MUST begin with a verb to describe the function, followed by the subject of the verb?

More information about Workflow, action step and scope block names MUST begin with a verb to describe the function, followed by the subject of the verb

More information can be found on the engineering website about Workflow, action step and scope block names MUST begin with a verb to describe the function, followed by the subject of the verb

Does this codebase pass the following requirement: Words in a workflow name MUST be separated by a space where possible?

More information about Words in a workflow name MUST be separated by a space where possible

More information can be found on the engineering website about Words in a workflow name MUST be separated by a space where possible

Does this codebase pass the following requirement: Scope blocks that are used for error handling MUST be prefixed with the word ‘Try’ or ‘Catch’?

More information about Scope blocks that are used for error handling MUST be prefixed with the word ‘Try’ or ‘Catch’

More information can be found on the engineering website about Scope blocks that are used for error handling MUST be prefixed with the word ‘Try’ or ‘Catch’