Fleshing otu workorder
This commit is contained in:
@@ -1,7 +1,6 @@
|
||||
using System;
|
||||
using System.Collections.Generic;
|
||||
using AyaNova.Biz;
|
||||
using System.ComponentModel.DataAnnotations;
|
||||
using System.ComponentModel.DataAnnotations.Schema;
|
||||
using Newtonsoft.Json;
|
||||
|
||||
namespace AyaNova.Models
|
||||
@@ -23,6 +22,7 @@ namespace AyaNova.Models
|
||||
public List<string> Tags { get; set; }
|
||||
|
||||
//Principle
|
||||
[Required]//this required annotation should cause a cascade delete to happen automatically when wo is deleted, need to test that
|
||||
public int WorkorderId { get; set; }//fk
|
||||
public WorkOrder WorkOrder { get; set; }
|
||||
|
||||
@@ -33,6 +33,12 @@ namespace AyaNova.Models
|
||||
Tags = new List<string>();
|
||||
}
|
||||
|
||||
//Not persisted business properties
|
||||
//NOTE: this could be a common class applied to everything for common biz rule stuff
|
||||
//i.e. specific rights in situations based on rules, like candelete, canedit etc
|
||||
[NotMapped]
|
||||
public bool NonDataBaseExampleColumn { get; set; }//example of how to add a property that is not persisted but is used by both ends dynamically, should come up with a naming scheme so can see them at a glance
|
||||
|
||||
}//eoc
|
||||
|
||||
}//eons
|
||||
|
||||
Reference in New Issue
Block a user