admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-05-17 15:35:34 +00:00
parent 6d76a73191
commit 16bee4eff8
2 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/8.0/ayanova/docs/svc-contracts.md
View File

@@ -13,5 +13,6 @@ NOTES FOR DOC
- PRECEDENCE: Tagged Contract price overrides take precedence over general Contract price overrides. For example, if a Contract has a general discount for Labor rates and also has a tag override for a Labor record and the tags match then the tag override is the one used and the general override is ignored. If no tags matched then the general price override would be applied.
Conflict - multiple potential matches:
Contract tagged items are checked against the object in order of the contract tagged override with the most tags to the contract override with the least tags. This is done to try to make the most specific possible tag match. For example, a contract with 3 tagged labor price overrides and their tags selected are: "green", "red, green, blue", "orange, green". AyaNova will attempt to match by starting with the contract labor override with the most tags: "red,green,blue" then "orange,green" and finally "green". If a record is saved tagged with "orange,red,yellow,green,black,blue" it will be matched to the first item tagged "red,green,blue" as it has the most terms that match and it's override terms will be used and the other two will not be used.
Contract tagged items are checked against the object in order of the Contract tagged override with the most tags to the Contract override with the least tags. This is done to try to make the most specific possible tag match. For example, a Contract with 3 tagged labor price overrides and their tags selected are: "green", "red, green, blue", "orange, green". AyaNova will attempt to match by starting with the Contract labor override with the most tags: "red,green,blue" then "orange,green" and finally "green". If a record is saved tagged with "orange,red,yellow,green,black,blue" it will be matched to the first item tagged "red,green,blue" as it has the most terms that match and it's override terms will be used and the other two will not be used.
- Expiration: Contract expiry dates are checked at the time of work order **creation**. If a work order is in progress and has items added after it's Contract has expired the Contract will still apply to that work order.

8
server/AyaNova/biz/WorkOrderBiz.cs
View File

@@ -86,7 +86,7 @@ namespace AyaNova.Biz
//(seeder or api user, not something AyaNova front end would do)
if (newObject.Items.Count > 0)//our front end will post the header alone on new so this indicates a fully populated wo was saved
{
await GetCurrentContractFromContractIdAsync(newObject.ContractId);
await GetCurrentContractFromContractIdAsync(newObject.ContractId);
await ProcessChangeOfContractAsync(newObject.Id);
}
@@ -235,7 +235,7 @@ namespace AyaNova.Biz
await WorkOrderValidateAsync(putObject, dbObject);
if (HasErrors)
return null;
// await WorkOrderBizActionsAsync(AyaEvent.Modified, putObject, dbObject, null);
await WorkOrderBizActionsAsync(AyaEvent.Modified, putObject, dbObject, null);
ct.Replace(dbObject, putObject);
try
{
@@ -328,7 +328,7 @@ namespace AyaNova.Biz
//CREATION ACTIONS
if (ayaEvent == AyaEvent.Created)
{
{ //applied at time of creation only
//CONTRACT AUTO SET
if (newObj.ContractId == null && newObj.CustomerId != 0)
{
@@ -509,7 +509,7 @@ namespace AyaNova.Biz
//If Contract has response time then set CompleteByDate
if (mContractInEffect.ResponseTime != TimeSpan.Zero)
if (mContractInEffect!=null && mContractInEffect.ResponseTime != TimeSpan.Zero)
{
wo.CompleteByDate = DateTime.UtcNow.Add(mContractInEffect.ResponseTime);
}