liveapicreator-admin-cli

Version:

The NodeJS command line utility for 'CA Live API Creator' DevOps Administration from CA Technologies

github.com/EspressoLogicCafe/CALiveAPICreatorAdminCLI

EspressoLogicCafe/CALiveAPICreatorAdminCLI

16 lines • 5.15 kB

JSON

[ { "ts": "2017-12-19T23:07:06+00:00", "name": "Audit Orders", "color": "#00fcee", "summary": "If amount changes", "description": "This examples illustrates that your logic is a combination of Reactive Programming Rules, and JavaScript.\n\nNote your JavaScript can use LIbraries of Java/JavaScript code.  Upload these to your project in Project properties.\n\n \n" }, { "ts": "2017-12-19T23:07:06+00:00", "name": "Check Credit", "color": "#96f90d", "summary": "Ensure the balance does not exceed the credit limit.", "description": "<h2>Business Context</h2>\n\nStory: Place Order.  \n\nTask/Requirement: Check Credit.  (or, your methodology / terminology).\n\n \n\n<h2>Business view</h2>\n\nWhen placing an order, check credit - elaborated as follows (the <cite>"cocktail napkin spec"</cite>)... \n\n<ul>\n\t<li>the Balance must be less than or equal to the Credit Limit, where...  (step-wise definition of terms)</li>\n\t<li>the Balance is the sum of the unpaid Order Amount Totals, where...</li>\n\t<li>the Amount Total is the sum of the LineItem Amounts, where...</li>\n\t<li>the Amount is the discounted Price * Quantity, where...</li>\n\t<li>the Price is obtained from the Product</li>\n</ul>\n\nA good spec - clear, concise.\n\n \n\n<hr />\n<h2>Conventional Design</h2>\n\nIn a conventional approach, you might design the following pseudocode:\n\n<ol>\n\t<li>Compute the LineItem.amount\n\t<ol>\n\t\t<li>Read the Product to get the Price</li>\n\t\t<li>Multiply by qty_ordered to compute the amount</li>\n\t</ol>\n\t</li>\n\t<li>Update the PurchaseOrder.amount_total\n\t<ol>\n\t\t<li>Read the PurchaseOrder</li>\n\t\t<li>Increase the amount_total</li>\n\t\t<li>Update the PurchaseOrder (to cache)</li>\n\t</ol>\n\t</li>\n\t<li>Update the Customer.balance\n\t<ol>\n\t\t<li>Read the Customer,</li>\n\t\t<li>Increase the balance</li>\n\t\t<li>Update the Customer (to cache)</li>\n\t</ol>\n\t</li>\n\t<li>Check that balance <= credit_limit\n\t<ol>\n\t\t<li>Throw exception with error message for UI handling</li>\n\t\t<li>Rollback the transaction</li>\n\t</ol>\n\t</li>\n</ol>\n\nBut Place Order is just one Story.  We need analogous logic for all the related Stories (Detete Order, Pay Order, etc etc).\n\n \n\n<hr />\n<h2>Reactive Rule Approach</h2>\n\nAnd that's the power of declarative reactive logic.  You simply state the rules below (nearly the same as the cocktail napkin).\n\n \n\n<h2>Reactive Rule Execution: Watch, React and Chain</h2>\n\nAnd (as in a spreadsheet), the rules are automatically applied to all incoming transactions:\n\n<ol>\n\t<li>They watch for changes in data referenced by rules</li>\n\t<li>They react to changes in referenced data.  Execution order is dictated by dependencies.  </li>\n\t<li>They chain - including across tables.  So changes to line items affect their order, which affect their customer</li>\n</ol>\n\nNote it works across tables.  Consider the customer balance - the sum of the unpaid order amounts. \nIt works rather like a spreadsheet.  Order changes are watched, and the balance is\n\n<ul>\n\t<li>increased when order inserted</li>\n\t<li>decreased when order deleted... or paid</li>\n\t<li>adjusted when the order amount total is changed... or assigned to a new customer... or the line items are altered</li>\n</ul>\n\nObserve persistence is automated (no need to read/write the customer, or deal with transactions).  And it's optimized:\n\n<ul>\n\t<li>adjustments are 1 row updates, not select sum queries</li>\n\t<li>sql is averted if the watched data is not changed</li>\n\t<li>caching is provided (inserting multiple line items results in just 1 adjustment to order and customer)</li>\n</ul>\n\n \n\n<hr />\n<h2>Bottom Line</h2>\n\nThat means the following Stories are automatically addressed with our 5 "cocktail napkin" rules:\n\n<ul>\n\t<li>Delete Order - the balance is reduced</li>\n\t<li>Pay Order - the balance is reduced</li>\n\t<li>UnPay the Order - balance is increased</li>\n\t<li>Reassign Order to a new customer - new customer balance increased, old balance decreased (for unpaid Orders)</li>\n\t<li>Reassign a Line Item to a different Product - adjusts the order's amount total</li>\n\t<li>Add a Line Item</li>\n\t<li>Delete a Line Item</li>\n\t<li>Change Line Item Quantity</li>\n\t<li>Reassign Product to Line Item</li>\n\t<li>Do multiple of these, in combination ("no, 2 hammers, not 1 shovel")</li>\n</ul>\n\nA conventional approach would require hundreds of lines of code, might easily miss corner cases, and be tedious to maintain.\n\n \n" } ]