Service - Unit Standard - Revision history

Sven the Barbarian: /* Units that track costing properties */

2025-09-02T23:18:14Z

Units that track costing properties

← Older revision		Revision as of 23:18, 2 September 2025
Line 24:		Line 24:

	* The cost of Units passing through the supply chain can also be handled using unitTrackedProperty		* The cost of Units passing through the supply chain can also be handled using unitTrackedProperty
	* each raw material has a unitTrackedProperty that is it's cost or cost per unitTrackedProperty value (eg costPerYard)		* each raw material has a unitTrackedProperty that is it's cost (eg costPerBag) or cost per unitTrackedProperty value (eg costPerYard)
	* example 1 tracked Unit of a bag of 1000 buttons would have a remainingCost unitTrackedProperty for it's full cost		* example 1 tracked Unit of a bag of 1000 buttons would have a remainingCost unitTrackedProperty for it's full cost
	* calculatedProperties in transformUnits can spread that cost (and all other materials used) across the new tracked Units created, saving the total into a new property in the outputUnits		* calculatedProperties in transformUnits can spread that cost (and all other materials used) across the new tracked Units created, saving the total into a new property in the outputUnits

Sven the Barbarian: /* Units that track costing properties */

2025-09-02T23:17:37Z

Units that track costing properties

← Older revision		Revision as of 23:17, 2 September 2025
Line 24:		Line 24:

	* The cost of Units passing through the supply chain can also be handled using unitTrackedProperty		* The cost of Units passing through the supply chain can also be handled using unitTrackedProperty
	* each raw material has a unitTrackedProperty that is it's cost		* each raw material has a unitTrackedProperty that is it's cost or cost per unitTrackedProperty value (eg costPerYard)
	* example 1 tracked Unit of a bag of 1000 buttons would have a remainingCost unitTrackedProperty for it's full cost		* example 1 tracked Unit of a bag of 1000 buttons would have a remainingCost unitTrackedProperty for it's full cost
	* calculatedProperties in transformUnits can spread that cost (and all other materials used) across the new tracked Units created, saving the total into a new property in the outputUnits		* calculatedProperties in transformUnits can spread that cost (and all other materials used) across the new tracked Units created, saving the total into a new property in the outputUnits
	* remainingCost would need to be updated according to how many units remain, so additional transformUnits calculate correctly

	= objectSchemas =		= objectSchemas =

Sven the Barbarian at 22:52, 2 September 2025

2025-09-02T22:52:01Z

← Older revision		Revision as of 22:52, 2 September 2025
Line 14:		Line 14:
	* the unitTrackedProperty can then be used in [[Service - Transform Units]] to break down any number of individual Units into any number of other Units. This allows for changing a roll with unitTrackedProperty of yards into multiple yard Units, or different raw material Units into a group of clothing Units		* the unitTrackedProperty can then be used in [[Service - Transform Units]] to break down any number of individual Units into any number of other Units. This allows for changing a roll with unitTrackedProperty of yards into multiple yard Units, or different raw material Units into a group of clothing Units
	* eg if have 1 tracked bag of 1000 buttons can transform into 10 shirts (100 buttons each shirt), the bag is one tracked Unit, and gets transformed into 10 tracked Unit shirts along with any other raw material		* eg if have 1 tracked bag of 1000 buttons can transform into 10 shirts (100 buttons each shirt), the bag is one tracked Unit, and gets transformed into 10 tracked Unit shirts along with any other raw material

			== Making Inactive ==

			* Although Izara Supply does not manage stock levels, Units can be set to active/inactive so old or sold out Units can be marked as inactive, making queries easier to return only in stock Units
			* For example a roll of fabric is out of stock/inactive when it's unitTrackedProperty of yards reaches 0
			* Achieve this by setting inactiveIfZero in yards unitTrackedProperty

	= Units that track costing properties =		= Units that track costing properties =
Line 19:		Line 25:
	* The cost of Units passing through the supply chain can also be handled using unitTrackedProperty		* The cost of Units passing through the supply chain can also be handled using unitTrackedProperty
	* each raw material has a unitTrackedProperty that is it's cost		* each raw material has a unitTrackedProperty that is it's cost
	* example 1 tracked Unit of a bag of 1000 buttons would have a ~~cost~~ unitTrackedProperty for it's full cost		* example 1 tracked Unit of a bag of 1000 buttons would have a remainingCost unitTrackedProperty for it's full cost
	* calculatedProperties in transformUnits can spread that cost (and all other materials used) across the new tracked Units created, saving the total into a new property in the outputUnits		* calculatedProperties in transformUnits can spread that cost (and all other materials used) across the new tracked Units created, saving the total into a new property in the outputUnits
			* remainingCost would need to be updated according to how many units remain, so additional transformUnits calculate correctly

	= objectSchemas =		= objectSchemas =

Sven the Barbarian at 07:08, 16 February 2025

2025-02-16T07:08:05Z

@@ Line 45: / Line 45: @@
 },
 </syntaxhighlight>
 = Working documents =

Sven the Barbarian at 17:13, 15 February 2025

2025-02-15T17:13:32Z

Show changes

Sven the Barbarian at 12:29, 6 August 2023

2023-08-06T12:29:53Z

← Older revision		Revision as of 12:29, 6 August 2023
Line 32:		Line 32:

	[[Standard LogicalResults Per Service]]		[[Standard LogicalResults Per Service]]

			= Units that contain quantities =

			* Izara Supply is not used for stock management, but used to follow units we want to track, which in some cases might themselves have a quantity inside them (example bag of 1000 buttons or 200 yard roll of fabric)
			* instead of tracking each button or each yard (or inch) we track the bag or roll only
			* user can use a unitTrackedProperty to record the quantity inside the tracked Unit
			* the unitTrackedProperty can then be used in [[Service - Transform Units]] to break down into individual units or multiple used to create other tracked Units
			* eg if use 1 tracked back of 1000 buttons to make 10 shirts (100 buttons each shirt), the bag is one tracked Unit, and gets transformed into 10 tracked Unit shirts

			= Units that track costing =

			* The cost of Units passing through the supply chain can also be managed using unitTrackedProperty
			* each material has a unitTrackedProperty that is it's cost
			* example 1 tracked Unit of a bag of 1000 buttons would have a cost unitTrackedProperty for it's full cost
			* calculatedProperties in transformUnits can spread that cost (and all other materials used) across the new tracked Units created, saving the total into a new property in the outputUnits

	= Graph database =		= Graph database =

Sven the Barbarian at 09:41, 6 August 2023

2023-08-06T09:41:50Z

← Older revision		Revision as of 09:41, 6 August 2023
Line 52:		Line 52:

	=== Relationships ===		=== Relationships ===

	~~<syntaxhighlight lang="JavaScript">~~
	{
	~~relationshipType: "{unitStandardLib.IS_UNITTYPE_GRAPH_REL_TYPE}", // "is_unitType"~~
	~~schema: {~~
	~~elementCanBeRemoved: false,~~
	~~allPropertiesImmutable: true,~~
	~~restrictProperties: true,~~
	~~properties: {~~
	~~originTimestamp: //timestamp the request to create/change this relationship was sent~~
	},
	}
	}
	~~</syntaxhighlight>~~
	* links a standard unit to a unit type

	<syntaxhighlight lang="JavaScript">		<syntaxhighlight lang="JavaScript">

Sven the Barbarian at 08:19, 6 August 2023

2023-08-06T08:19:41Z

@@ Line 67: / Line 67: @@
 </syntaxhighlight>
 * links a standard unit to a unit type
 = Working documents =

Sven the Barbarian at 07:23, 6 August 2023

2023-08-06T07:23:41Z

← Older revision		Revision as of 07:23, 6 August 2023
Line 38:		Line 38:

	=== Nodes ===		=== Nodes ===

	~~<syntaxhighlight lang="JavaScript">~~
	{
	~~nodeLabel: "{UnitSharedLib.UNIT_GRAPH_NODE_LABEL}", // stored in shared npm, shared by all unit Handlers~~
	~~schema: {~~
	~~identifier: true,~~
	~~restrictProperties: true,~~
	~~restrictRelationships: true,~~
	~~properties: {~~
	~~unitId: {~~
	~~identifier: true, //(random uuid)~~
	},
	~~unitHandlerServiceNameTag: {~~
	~~immutable: true,~~
	},
	},
	}
	}
	~~</syntaxhighlight>~~

	=== Versioned data ===		=== Versioned data ===

Sven the Barbarian: Created page with "= Overview = Handler service for the standard unit that tracks a single item. = Repository = https://bitbucket.org/izara-supply-units/izara-supply-units-unit-standard = DynamoDB tables = == Standard Config Table Per Service == === Configuration tags === { configTag: "SupplyGraphServiceName" configKey: "SupplyGraphServiceName" configValue: xxx // eg: "SupplyGraph" } {..."

2023-08-06T07:16:37Z

Created page with "= Overview = Handler service for the standard unit that tracks a single item. = Repository = https://bitbucket.org/izara-supply-units/izara-supply-units-unit-standard = DynamoDB tables = == Standard Config Table Per Service == === Configuration tags === <syntaxhighlight lang="JavaScript"> { configTag: "SupplyGraphServiceName" configKey: "SupplyGraphServiceName" configValue: xxx // eg: "SupplyGraph" } </syntaxhighlight> <syntaxhighlight lang="JavaScript"> {..."

New page

= Overview =

Handler service for the standard unit that tracks a single item.

= Repository =

https://bitbucket.org/izara-supply-units/izara-supply-units-unit-standard

= DynamoDB tables =

== [[Standard Config Table Per Service]] ==

=== Configuration tags ===

<syntaxhighlight lang="JavaScript">
{
configTag: "SupplyGraphServiceName"
configKey: "SupplyGraphServiceName"
configValue: xxx // eg: "SupplyGraph"
}
</syntaxhighlight>

<syntaxhighlight lang="JavaScript">
{
configTag: "UnitManagerServiceName"
configKey: "UnitManagerServiceName"
configValue: xxx // eg: "UnitManager"
}
</syntaxhighlight>

== LogicalResults ==

[[Standard LogicalResults Per Service]]

= Graph database =

== [[Service - Supply Graph]]==

=== Nodes ===

<syntaxhighlight lang="JavaScript">
{
nodeLabel: "{UnitSharedLib.UNIT_GRAPH_NODE_LABEL}", // stored in shared npm, shared by all unit Handlers
schema: {
identifier: true,
restrictProperties: true,
restrictRelationships: true,
properties: {
unitId: {
identifier: true, //(random uuid)
},
unitHandlerServiceNameTag: {
immutable: true,
},
},
}
}
</syntaxhighlight>

=== Versioned data ===

==== unitSettings ====

<syntaxhighlight lang="JavaScript">
{
properties: {
// some are controlled by unitType, others can be added as needed case by case, not controlled
},
}
</syntaxhighlight>

=== Relationships ===

<syntaxhighlight lang="JavaScript">
{
relationshipType: "{unitStandardLib.IS_UNITTYPE_GRAPH_REL_TYPE}", // "is_unitType"
schema: {
elementCanBeRemoved: false,
allPropertiesImmutable: true,
restrictProperties: true,
properties: {
originTimestamp: //timestamp the request to create/change this relationship was sent
},
}
}
</syntaxhighlight>
* links a standard unit to a unit type

= Working documents =

[[:Category:Working_documents - Unit Standard|Unit Standard]]

[[Category:Backend services| Unit Standard]]