Function Validate previous service: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{LegacyContent
| explanation=field [[Previous_Service]] was retired
| content=
{{Data Integrity Check
{{Data Integrity Check
|DIC_summary=Validates [[Previous Service field]]: can't be empty/blank
|DIC_summary=Validates [[Previous Service field]]: can't be empty/blank
|DIC_related_concepts=Previous Service field
|DIC_related_concepts=Previous Service field
|DIC_firmness=hard check
|DIC_firmness=hard check
|DIC_coding=function ''Validate previous service ''
|DIC_coding=function ''Validate_previous_service ''
|DIC_implementation_date=2016-05-01
|DIC_implementation_date=2016-05-01
|DIC_status=retired
|DIC_status=retired
Line 14: Line 18:
{{Related Articles}}
{{Related Articles}}


[[Category:Registry checks]]
[[Category:Legacy Registry check]]
}}

Latest revision as of 14:56, 7 September 2022

Legacy Content

This page contains Legacy Content.

  • Explanation: field Previous_Service was retired
  • Successor: No successor was entered

Click Expand to show legacy content.

Data Integrity Checks
Summary: Validates Previous Service field: can't be empty/blank
Related: Previous Service field
Firmness: hard check
Timing: always
App: CCMDB.accdb
Coding: function Validate_previous_service
Uses L Problem table: not relevant for this app
Status: retired
Implementation Date: 2016-05-01
Backlogged: No
  • Cargo


  • SMW


  • Categories:  
  • form:

Retired as part of retiring the Previous_Service field

Related articles

Related articles: