Function Validate previous service: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| 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 | ||
| Line 14: | Line 18: | ||
{{Related Articles}} | {{Related Articles}} | ||
[[Category:Registry | [[Category:Legacy Registry check]] | ||
}} | |||
Latest revision as of 15:56, 2022 September 7
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 |
Retired as part of retiring the Previous_Service field
Related articles
| Related articles: |