1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162 |
- using System;
- using System.ComponentModel.DataAnnotations;
- namespace Dfs.WayneChina.PosModelMini
- {
- public class SiteDevice
- {
- /// <summary>
- /// Unique id of the site device.
- /// </summary>
- public Guid Id { get; set; }
- /// <summary>
- /// Site device type.
- /// </summary>
- public SiteDeviceType DeviceType { get; set; }
- /// <summary>
- /// Description of the site device.
- /// </summary>
- public string Description { get; set; }
- /// <summary>
- /// Brand of the site device, such as Sunmi.
- /// </summary>
- [MaxLength(100)]
- public string Brand { get; set; }
- /// <summary>
- /// like Summi T1 or Summi V1.
- /// </summary>
- [MaxLength(100)]
- public string Model { get; set; }
- /// <summary>
- /// An id string which correlated with Device hardware, should be global unique, and could not be changed.
- /// server may use this to authenticate a device.
- /// </summary>
- public string HardwareIdentity { get; set; }
- /// <summary>
- /// Use this field as the argument of only POS device,
- /// and will be passed in to talk with FDC server,
- /// so this value must be unique in one site(one fusion per site).
- /// </summary>
- public string PosDeviceFdcClientId { get; set; }
- /// <summary>
- /// Associate this site device to a business unit id.
- /// </summary>
- public virtual Guid AsSubjectOfBusinessUnitId { get; set; }
- /// <summary>
- /// A device acts as a subject of a business unit, all other user priviledge control are all
- /// based on the device it operates.
- /// think about a case, a pos machine belong to a site(businessUnit with type site), and then we can set an
- /// user with restricted in this site, then the user restriction is actually checked with the user's log in
- /// operation in this pos machine.
- /// </summary>
- public virtual BusinessUnit AsSubjectOfBusinessUnit { get; set; }
- }
- }
|