Rename to on-device decisioning (#3)

Co-authored-by: Sam Fung <[email protected]>

Author: 5amfung

README.md

@@ -28,7 +28,7 @@ when the test is started on the server side and then it is handed off to at.js o
 Node.js SDK API calls when processing a client request, sharing the same ECID instance.
 - [multiple-mbox-ecid-analytics-atjs-integration](multiple-mbox-ecid-analytics-atjs-integration) - shows how Target 
 Node.js SDK can be used to request content for multiple mboxes in the same Target call.
-- [local-execution](local-execution) - shows how Target Node.js SDK can be used in local execution mode
+- [on-device-decisioning](on-device-decisioning) - shows how Target Node.js SDK can be used in on-device decisioning method
 - [feature-flag](feature-flag) - shows how Target Node.js SDK can be easily used for feature flags
 
 For Target Node.js SDK documentation, see [Target Node.js SDK NPM page](https://www.npmjs.com/package/@adobe/target-nodejs-sdk).

feature-flag/README.md

@@ -86,4 +86,4 @@ And the `asObject` method is used to get a plain old JSON representation of the
 
 ```
 
-Note: This sample uses local execution mode.  But the `getAttributes` method can be used in any execution mode.
+Note: This sample uses on-device decisioning method.  But the `getAttributes` method can be used in any decisioning method.

feature-flag/package-lock.json

@@ -1,7 +1,7 @@
 {
-  "name": "target-local-execution",
+  "name": "target-on-device-decisioning",
   "version": "1.0.0",
-  "description": "Adobe Target Node.js SDK, target local execution sample",
+  "description": "Adobe Target Node.js SDK, target on-device decisioning sample",
   "main": "index.js",
   "scripts": {
     "start": "node server.js"
@@ -20,7 +20,7 @@
     "ECID",
     "Visitor",
     "Delivery",
-    "target-local-execution"
+    "target-on-device-decisioning"
   ],
   "author": "Adobe Systems Inc.",
   "license": "Apache-2.0",

feature-flag/package.json

@@ -18,7 +18,7 @@ const Handlebars = require("handlebars");
 const TargetClient = require("@adobe/target-nodejs-sdk");
 const { getSearchProvider } = require("./provider");
 
-const PAGE_TITLE = "Target Local Sample";
+const PAGE_TITLE = "Target On-Device Decisioning Sample";
 // Load the template of the HTML page returned in the response
 const TEMPLATE = fs.readFileSync(`${__dirname}/index.handlebars`).toString();
 const handlebarsTemplate = Handlebars.compile(TEMPLATE);
@@ -70,7 +70,7 @@ function sendErrorResponse(res, error) {
 const CONFIG = {
   client: "adobesummit2018",
   organizationId: "65453EA95A70434F0A495D34@AdobeOrg",
-  executionMode: "local",
+  decisioningMethod: "on-device",
   artifactPayload: require("./sampleRules"),
   events: {
     clientReady: startExpressApp

feature-flag/server.js

@@ -1,4 +1,4 @@
-# Target Local execution sample
+# Target on-device decisioning sample
 
 ## Overview
 
@@ -22,7 +22,7 @@ For this sample, we first created a simple AB activity for the `demo-marketing-o
 
 As you can see, each experience has a different filename set in the `asset` property.
 
-When run, the app server makes a getOffers call, requesting the `demo-marketing-offer1` mbox.  But the SDK has been configured to use local execution mode to determine the outcome of the call rather than send a request to the target delivery API.
+When run, the app server makes a getOffers call, requesting the `demo-marketing-offer1` mbox.  But the SDK has been configured to use on-device decisioning method to determine the outcome of the call rather than send a request to the target delivery API.
 
 When the page is loaded in a browser, an image is shown at the top of the page.  This image comes from one of the two experiences in the activity defined above.  The target response is also shown on the page.
 
@@ -34,22 +34,22 @@ When the page is loaded in a browser, an image is shown at the top of the page.
 
 ## How it works
 
-This sample utilizes local execution mode to determine target experiences.  By default, the SDK always makes a request to the target delivery API for each `getOffers` call.  But you can configure the SDK to use local execution mode instead.  This mode downloads target activity rules on initialization.   The rules are then used to determine which experiences to return when `getOffers` is called, rather than make a request to the delivery API each time.
+This sample utilizes on-device decisioning method to determine target experiences.  By default, the SDK always makes a request to the target delivery API for each `getOffers` call.  But you can configure the SDK to use on-device decisioning method instead.  This mode downloads target activity rules on initialization.   The rules are then used to determine which experiences to return when `getOffers` is called, rather than make a request to the delivery API each time.
 
-There are four main properties to keep in mind when using local execution mode:
+There are four main properties to keep in mind when using on-device decisioning method:
 
 | Name                      | Description                                                                         |
 |---------------------------|-------------------------------------------------------------------------------------|
-| executionMode             | The execution mode the SDK will run in.  Can be `local`, `remote`, or `hybrid`. Defaults to `remote`      |
+| decisioningMethod         | The decisioning method the SDK will run in.  Can be `on-device`, `server-side`, or `hybrid`. Defaults to `server-side`      |
 | artifactLocation          | This is a fully qualified url to the rules definition file that will be used to determine outcomes locally.  |
 | artifactPayload           | A target decisioning JSON artifact. If specified, it is used instead of requesting one from a URL. |
 | events                    |  Object.<String, Function>  | No      | None          | An optional object with event name keys and callback function values. |
 
-NOTE: You must specify an `artifactLocation` or `artifactPayload` during the alpha release for local execution mode to work.
+NOTE: You must specify an `artifactLocation` or `artifactPayload` during the alpha release for on-device decisioning method to work.
 
 ```js
 const CONFIG = {
-    executionMode: "local",
+    decisioningMethod: "on-device",
     artifactPayload: require("sampleRules"),
     events: { clientReady: targetReady }
 };

local-execution/README.md renamed to on-device-decisioning/README.md

@@ -20,7 +20,7 @@
     "ECID",
     "Visitor",
     "Delivery",
-    "target-local-execution"
+    "target-on-device-decisioning"
   ],
   "author": "Adobe Systems Inc.",
   "license": "Apache-2.0",