openpss / com.hendraanggrian.openpss.db.schemas / Invoice

Invoice

data class Invoice : Document<Invoices>, Numbered

Types

DigitalJob	`data class DigitalJob : TypedJob`
Job	`interface Job`
OffsetJob	`data class OffsetJob : TypedJob`
OtherJob	`data class OtherJob : Job`
PlateJob	`data class PlateJob : TypedJob`
TypedJob	`interface TypedJob : Job`

Constructors

<init>

Invoice(no: Int, employeeId: Id<String, Employees>, customerId: Id<String, Customers>, dateTime: DateTime, offsetJobs: List<OffsetJob>, digitalJobs: List<DigitalJob>, plateJobs: List<PlateJob>, otherJobs: List<OtherJob>, note: String, printed: Boolean, isPaid: Boolean, isDone: Boolean)

Properties

customerId	`val customerId: Id<String, Customers>`
dateTime	`val dateTime: DateTime`
digitalJobs	`var digitalJobs: List<DigitalJob>`
employeeId	`val employeeId: Id<String, Employees>`
id	`lateinit var id: Id<String, Invoices>` NoSQL object identifier.
isDone	`val isDone: Boolean`
isPaid	`val isPaid: Boolean`
jobs	`val jobs: List<Job>`
no	`val no: Int` Since `id` is reserved in Document, `no` is direct replacement. Basically means the same thing.
note	`var note: String`
offsetJobs	`var offsetJobs: List<OffsetJob>`
otherJobs	`var otherJobs: List<OtherJob>`
plateJobs	`var plateJobs: List<PlateJob>`
printed	`val printed: Boolean`
total	`val total: Double`

Companion Object Functions

new	`fun new(employeeId: Id<String, Employees>, customerId: Id<String, Customers>, dateTime: DateTime, offsetJobs: List<OffsetJob>, digitalJobs: List<DigitalJob>, plateJobs: List<PlateJob>, otherJobs: List<OtherJob>, note: String): Invoice`
no	`fun no(resources: Resources, no: Number?): String?`