@ind-rcg/modeler-sfdx-cli-plugin 246.1046.0 → 246.1048.0

package/README.md

@@ -1,7 +1,7 @@
 modeler-sfdx-cli-plugin
 =======================
 
-This plugin is an enhancement of the sfdx cli and provide you features to customize the Consumer Goods Cloud Mobility application. This version will be the replacement for the Consumer Goods Mobile Modeler which was hosted on a Windows Server machine. 
+This plugin is an enhancement of the salesforce cli and provide you features to customize the Consumer Goods Cloud Mobility application. This version will be the replacement for the Consumer Goods Mobile Modeler which was hosted on a Windows Server machine. 
 
 ## Getting Started
 

package/oclif.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "246.1046.0",
+  "version": "246.1048.0",
   "commands": {
     "modeler:workspace:add": {
       "id": "modeler:workspace:add",

package/package.json

@@ -1,14 +1,14 @@
 {
     "name": "@ind-rcg/modeler-sfdx-cli-plugin",
     "displayName": "modeler-sfdx-cli-plugin",
-    "version": "246.1046.0",
+    "version": "246.1048.0",
     "author": "Salesforce",
     "license": "BSD-3-Clause",
     "description": "This plugin is an enhancement of the sfdx cli and provide you features to customize the Consumer Goods Cloud Mobility application. This version will be the replacement for the Consumer Goods Mobile Modeler which was hosted on a Windows Server machine.",
     "dependencies": {
         "@ind-rcg/backend": "246.1008.0",
         "@ind-rcg/framework": "246.1015.0",
-        "@ind-rcg/generator": "246.1019.0",
+        "@ind-rcg/generator": "246.1021.0",
         "@oclif/core": "2.9.4",
         "@salesforce/core": "4.1.0",
         "@salesforce/sf-plugins-core": "3.1.3",
@@ -101,7 +101,7 @@
         "uglify": "uglifyjs-folder lib -e -x .js -o lib --log-level error"
     },
     "sfdx": {
-        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@ind-rcg/modeler-sfdx-cli-plugin/246.1046.0.crt",
-        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@ind-rcg/modeler-sfdx-cli-plugin/246.1046.0.sig"
+        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@ind-rcg/modeler-sfdx-cli-plugin/246.1048.0.crt",
+        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@ind-rcg/modeler-sfdx-cli-plugin/246.1048.0.sig"
     }
 }

package/templates/contractTemplates/YourModule Section/BO/LO_ListObject/Lo${NAME}/Li${NAME}.listitem.xml

@@ -0,0 +1,5 @@
+<ListItem name="Li${NAME}">
+  <SimpleProperties>
+      <!-- You can use <workspaceRoot>/contractSnippets/YourModule Section/BO/LO_ListObject/snippets/ListItemSimplePropertiesSimplePropertySnipp.xml as template for your case -->
+  </SimpleProperties>
+</ListItem>

package/templates/contractTemplates/{LU_LookupObject/Lu${NAME}/Lu${NAME}.lookupobject.xml → YourModule Section/BO/LU_LookupObject/Lu${NAME}/Lu${NAME}.lookupobject.xml }

@@ -2,7 +2,7 @@
   <!--In case lookup does not require datasource, let name of datasource property empty-->
   <DataSource name="${DATASOURCE_REFERENCE}" />
   <SimpleProperties>
-    <!-- You can use LookupObjectSimplePropertiesSimplePropertySnipp.xml as template (workingFolder->templates->snippets->LU_LookupObject->snippets) for your case/-->
+    <!-- You can use LookupObjectSimplePropertiesSimplePropertySnipp.xml as template (workingFolder->contractSnippets->YourModule Section->BO->LU_LookupObject->snippets) for your case/-->
   </SimpleProperties>
   <Methods>
     <Method name="afterLoadAsync" />

package/templates/contractTemplates/YourModule Section/BO/Methods_or_BusinessLogic/${REFERENCE_OBJECT}.${NAME}.bl.js

@@ -0,0 +1,53 @@
+"use strict";
+
+///////////////////////////////////////////////////////////////////////////////////////////////
+//                 IMPORTANT - DO NOT MODIFY AUTO-GENERATED CODE OR COMMENTS                 //
+//Parts of this file are auto-generated and modifications to those sections will be          //
+//overwritten. You are allowed to modify:                                                    //
+// - the tags in the jsDoc as described in the corresponding section                         //
+// - the function name and its parameters                                                    //
+// - the function body between the insertion ranges                                          //
+//         "Add your customizing javaScript code below / above"                              //
+//                                                                                           //
+///////////////////////////////////////////////////////////////////////////////////////////////
+
+/**
+ * Use the following jsDoc tags to describe the BL function. Setting these tags will
+ * change the runtime behavior in the mobile app. The values specified in the tags determine
+ * the name of the contract file. The filename format is “@this . @function .bl.js”.
+ * For example, LoVisit.BeforeLoadAsync.bl.js
+ * -> function: Name of the businessLogic function.
+ * -> this: The LO, BO, or LU object that this function belongs to (and it is part of the filename).
+ * -> kind: Type of object this function belongs to. Most common value is "businessobject".
+ * -> async: If declared as async then the function should return a promise.
+ * -> param: List of parameters the function accepts. Make sure the parameters match the function signature.
+ * -> namespace: Use CORE or CUSTOM. If you are a Salesforce client or an implementation partner, always use CUSTOM to enable a seamless release upgrade.
+ * -> extends: Base class of the LO, BO, and LU objects that this function belongs to.
+ * -> maxRuntime: Maximum time this function is allowed to run, takes integer value in ms. If the max time is exceeded, error is logged.
+ * -> returns: Type and variable name in which the return value is stored.
+ * @function ${METHOD_NAME}
+ * @this ${REFERENCE_OBJECT}
+ * @kind ${REFERENCE_OBJECT_BASE_TYPE}
+ * @namespace ${NAMESPACE}
+ */
+function ${METHOD_NAME}(){
+    var me = this;
+    ///////////////////////////////////////////////////////////////////////////////////////////////
+    //                                                                                           //
+    //               Add your customizing javaScript code below.                                 //
+    //                                                                                           //
+    ///////////////////////////////////////////////////////////////////////////////////////////////
+    
+    
+    
+		
+   
+  
+    ///////////////////////////////////////////////////////////////////////////////////////////////
+    //                                                                                           //
+    //               Add your customizing javaScript code above.                                 //
+    //                                                                                           //
+    ///////////////////////////////////////////////////////////////////////////////////////////////
+
+    
+}

package/templates/contractTemplates/YourModule Section/BO/Methods_or_BusinessLogic/${REFERENCE_OBJECT}.${NAME}Async.bl.js

@@ -0,0 +1,52 @@
+"use strict";
+
+///////////////////////////////////////////////////////////////////////////////////////////////
+//                 IMPORTANT - DO NOT MODIFY AUTO-GENERATED CODE OR COMMENTS                 //
+//Parts of this file are auto-generated and modifications to those sections will be          //
+//overwritten. You are allowed to modify:                                                    //
+// - the tags in the jsDoc as described in the corresponding section                         //
+// - the function name and its parameters                                                    //
+// - the function body between the insertion ranges                                          //
+//         "Add your customizing javaScript code below / above"                              //
+//                                                                                           //
+///////////////////////////////////////////////////////////////////////////////////////////////
+
+/**
+ * Use the following jsDoc tags to describe the BL function. Setting these tags will
+ * change the runtime behavior in the mobile app. The values specified in the tags determine
+ * the name of the contract file. The filename format is “@this . @function .bl.js”.
+ * For example, LoVisit.BeforeLoadAsync.bl.js
+ * -> function: Name of the businessLogic function.
+ * -> this: The LO, BO, or LU object that this function belongs to (and it is part of the filename).
+ * -> kind: Type of object this function belongs to. Most common value is "businessobject".
+ * -> async: If declared as async then the function should return a promise.
+ * -> param: List of parameters the function accepts. Make sure the parameters match the function signature.
+ * -> namespace: Use CORE or CUSTOM. If you are a Salesforce client or an implementation partner, always use CUSTOM to enable a seamless release upgrade.
+ * -> extends: Base class of the LO, BO, and LU objects that this function belongs to.
+ * -> maxRuntime: Maximum time this function is allowed to run, takes integer value in ms. If the max time is exceeded, error is logged.
+ * -> returns: Type and variable name in which the return value is stored.
+ * @function ${METHOD_NAME}
+ * @this ${REFERENCE_OBJECT}
+ * @kind ${REFERENCE_OBJECT_BASE_TYPE}
+ * @async
+ * @namespace ${NAMESPACE}
+ * @returns promise
+ */
+function ${METHOD_NAME}(){
+    var me = this;
+    ///////////////////////////////////////////////////////////////////////////////////////////////
+    //                                                                                           //
+    //               Add your customizing javaScript code below.                                 //
+    //                                                                                           //
+    ///////////////////////////////////////////////////////////////////////////////////////////////
+    
+    var promise=when.resolve();
+
+    ///////////////////////////////////////////////////////////////////////////////////////////////
+    //                                                                                           //
+    //               Add your customizing javaScript code above.                                 //
+    //                                                                                           //
+    ///////////////////////////////////////////////////////////////////////////////////////////////
+
+    return promise;
+}

package/templates/contractTemplates/YourModule Section/BO/Methods_or_BusinessLogic/BusinessLogic.md

@@ -0,0 +1,4 @@
+# Business Logic (BL) Contract Definition
+
+## Description
+The Business Logic Contract specifies a Method used by any of the Business Objects (BO, LO, LU) in the Mobility Application.

package/templates/contractTemplates/{DS_DataSource/DataSource.md → YourModule Section/DS/DS_DataSource/DataSource.md }

@@ -1,5 +1,23 @@
 # DataSource (DS) Contract Definition
 
+## Table of Content
+- [Description](#description)
+- [Attribute Section](#attributes)
+  - [Standard Attribute](#attribute-most-common)
+  - [Derivied Attribute](#derivedattribute)
+  - [DateTime Attribute](#datetimeattribute)
+  - [PivotItems (rarely used)](#pivotitems)
+- [Entity Section](#entities)
+  - [Join](#join)
+  - [SimpleJoin](#simplejoin-condition)
+  - [ComplexJoin](#complexjoin-condition)
+- [QueryCondition Section](#querycondition)
+- [OrderCriteria Section](#orderciteria)
+- [GroupBy Section](#groupby)
+- [Macros](#macros)
+  - [Framework Macros](#framework-macros)
+  - [Parameter Macros](#parameter-macros)
+
 ## Description
 DataSource Contracts are design time artifacts describing a common way for data access and manipulation of existing enterprise information system.
 The main goal of this document is to have a common understanding of the different elements that constitute a definition of a DataSource Contract.
@@ -217,7 +235,7 @@ Parameters are modeled and can be used in the JOIN and the QUERY Conditions to f
 |name|String|no|||	 
 |baseType|String|yes|Date, Time or DateTime||
 |type|String|yes|SQLite type (NULL, INTEGER, REAL, TEXT, LIST)||
-|treatAs|String|no|can be set to "sqlSnippet" to include the parameter directly into the statement (not as parameter)||
+|treatAs|String|yes|can be set to "sqlSnippet" to include the parameter directly into the statement (not as parameter)||
 
 Type "LIST" is used for parameters used in "IN" conditions. All items of the list (Array or comma separated list in a string) must be the same type (string or numeric).
 

package/templates/contractTemplates/{DS_DataSource/Ds${NAME}_sf.datasource.xml → YourModule Section/DS/DS_DataSource/Ds${NAME}_sf.datasource.xml }

@@ -1,4 +1,5 @@
 <DataSource name="Ds${NAME}" backendSystem="sf" businessObjectClass="${REFERENCE_OBJECT}" external="false" editableEntity="" schemaVersion="2.0">
+  <!-- For more information about the supported properties and nodes see corresponding DataSource.md file under ~Workspace/contractSnippets/YourModuel Section/DS/DS_DataSource -->
   <Attributes>
     <Attribute name="" table="" column="" />
   </Attributes>

package/templates/contractTemplates/YourModule Section/PR/PR_Process_&_UI/_snippets/Process/ProcessCockpitCardSnipp.xml

@@ -0,0 +1,56 @@
+<!-- 
+This snippet will help you to quickly add a new cockpit card to an existing cockpit. For the UI part see $WORKINGFOLDER/contractSnippets/YourModule Section/PR/PR_Process_&_UI/snippets/UI/CockpitCardContainer.xml 
+Add these parts into your existing Process contract of your UI you will enhance for a new Cockpit Card
+
+The parts with ${YOUR.....} needs to be replaced by your names you will use. The name of the card is configured in the UI contract in property "name" of the corresponding CardContainer
+eg. "${YOUR_CARDNANE}_DataLoaded" -> "CardDisplay_DataLoaded"
+-->
+
+<!-- Declarations Section (Process->Entry->ProcessContext->Declarations -->
+<!-- vvvvvvvvvvvvvvv    start section to copy (incl. the comment tags)     vvvvvvvvvvvvvv -->
+
+        <!-- Card: <YOUR CARDNAME> -->
+        <Declaration name="${YOUR_CARDNANE}_DataLoaded" type="DomBool"/>
+        <Declaration name="${YOUR_CARDNANE}_SubComponentName" type="String"/>
+        <Declaration name="${YOUR_CARDNAME}_DisplayList" type="<YOUR_LO_YOU_WILL_USE_TO_DISPLAY>"/>
+
+<!-- ^^^^^^^^^^^^^^^                 end section to copy                   ^^^^^^^^^^^^^^ -->
+
+#############################################################################################################
+
+<!-- Declarations Section (Process->Body->Actions->Action (name="ShowCockpit")->Events -->
+<!-- vvvvvvvvvvvvvvv    start section to copy (incl. the comment tags)     vvvvvvvvvvvvvv -->
+
+          <!-- Card: Display -->
+          <Event name="${YOUR_CARDNANE}_loadData" action="${YOUR_CARDNANE}_loadData" />
+        
+<!-- ^^^^^^^^^^^^^^^                 end section to copy                   ^^^^^^^^^^^^^^ -->
+
+#############################################################################################################
+
+<!-- Declarations Section (Process->Body->Actions -->
+<!-- vvvvvvvvvvvvvvv    start section to copy (incl. the comment tags)     vvvvvvvvvvvvvv -->
+
+      <!-- Card: Display  START-->
+      <Action name="${YOUR_CARDNANE}_loadData" actionType="LOAD" type="LoMyDisplays" > 
+        <Return name="ProcessContext::${YOUR_CARDNANE}_DisplayList" />
+        <TransitionTo action="${YOUR_CARDNANE}_setSubcomponentName"/>
+      </Action>
+      <Action name="${YOUR_CARDNANE}_setSubcomponentName" actionType="LOGIC" call="ProcessContext::CardController.getDisplayedSubcomponentName"> 
+        <Parameters>
+          <Input name="loItems" value="ProcessContext::${YOUR_CARDNANE}_DisplayList"/>
+          <Input name="type" value="Display" type="Literal" />
+        </Parameters>
+        <Return name="ProcessContext::${YOUR_CARDNANE}_SubComponentName" />
+        <TransitionTo action="${YOUR_CARDNANE}_setDataLoaded"/>
+      </Action>
+      <Action name="${YOUR_CARDNANE}_setDataLoaded" actionType="LOGIC" call="Utils.identity"> 
+        <Parameters>
+          <Input name="value" value="1" type="Literal" />
+        </Parameters>
+        <Return name="ProcessContext::${YOUR_CARDNANE}_DataLoaded" />
+      </Action>
+      <!-- Card: Display  END-->
+        
+<!-- ^^^^^^^^^^^^^^^                 end section to copy                   ^^^^^^^^^^^^^^ -->
+                    

package/templates/contractTemplates/YourModule Section/PR/PR_Process_&_UI/_snippets/UI/Cockpit/CockpitCardContainer.xml

@@ -0,0 +1,83 @@
+<!--To add a new card to a dashboard some steps are neccessary
+1. Adapt the UI and add the section for your card
+1.1
+2. Adapt the corresponding Process contract of your UI card
+2.1 Declare a varialbe to store the information if card data are loaded
+2.2 Declare a variable to store the information for the SubComponent name. Text which is displayed in case there are no data found
+3. Maintain utils class we reuse from several places to identify is a card should be visible or collapsible. You can use your own function or you adjust the available helper business object
+3.1 modify the  isCollapsible function
+3.2 modify the isVisisble function
+3.3 to store the values for isCollapsible and isVisible you need to create two simple properties to host the current value
+-->
+<CardContainer name="${NAME}">
+    <Bindings>
+      <!-- Title and counter -->
+      <Resource target="Title" type="Label" id="${NAME}Title" defaultLabel="<YOUR DEFAULT LABEL IN CASE No LOCALE ENTRY>" />
+      <Resource target="Information" type="Label" id="${NAME}Info" defaultLabel="<YOUR DEFAULT LABLE IN CASE No LOCALE ENTRY>" />
+      <!-- Data loaded flag (by setting this card gets rendered) -->
+      <Binding target="IsReadyToLoad" type="Text" binding="ProcessContext::${NAME}_DataLoaded>" bindingMode="ONE_WAY" />
+      <!-- Defines id card is visible or hidden. ProcessContext::CardController is an instance of object BoSalesCockpitHelper which host some convenience function we can reuse -->
+      <!-- As default of this function is false we comment out this section. When the section is not there or commented out it is visible -->
+      <!--
+      <Binding type="Visible" target="Visible" call="ProcessContext::CardController.isCardVisible" />
+        <Parameters>
+          <Input name="cardName" type="Literal" value="${NAME}" />
+        </Parameters>
+      -->
+      <!-- Defines id card is collapsible.  ProcessContext::CardController is an instance of object BoSalesCockpitHelper which host some convenience function we can reuse
+      The isCardCollapsible functions need to be adapted and a new simple property collpaseState_${NAME} (e.g. collapseState_CardDisplay ) has to be defined to persist the current status -->
+      <Binding type="Text" target="IsCollapsible" call="ProcessContext::CardController.isCardCollapsible>" bindingMode="ONE_WAY">
+        <Parameters>
+          <Input name="cardName" type="Literal" value="${NAME}" />
+        </Parameters>
+      </Binding>
+      <!-- Defines this card is maximizable. ProcessContext::CardController is an instance of object BoSalesCockpitHelper which host some convenience function we can reuse -->
+      <Binding type="Text" target="ShowMaximizeButton" call="ProcessContext::CardController.isCardMaximizable">
+        <Parameters>
+          <Input name="cardName" type="Literal" value="${NAME}" />
+        </Parameters>
+      </Binding>
+      <!-- This is a binding to a simple property out of the BoSalesCockpitHelper to store the information if card was collapsed or not -->
+      <Binding target="CollapseState" type="Text" binding="ProcessContext::CardController.collapseState_CardDisplay" bindingMode="TWO_WAY" />
+      <!-- Subcomponent (e.g. used for no data message) -->
+      <Binding target="DisplayedSubcomponentName" type="Text" binding="ProcessContext::${NAME}_SubComponentName" bindingMode="ONE_WAY" />
+    </Bindings>
+    <VisibilityRoles allRoles="true" />
+    <Events>
+      <LoadContainerData event="${NAME}_loadData" />
+    </Events>
+    <!-- No Data Message Subcomponent. We reuse an existing UIplugin and only handover the information-->
+    <NoDataMessage name="CardNoDataMessageUiPlugin">
+      <Bindings>
+        <Resource target="maintext" type="Label" id="${NAME}NoDataMainText" defaultLabel="No data available, " />
+        <Resource target="subtext" type="Label" id="${NAME}NoDataSubText" defaultLabel="relax and enjoy the sun!" />
+        <Resource target="infoIcon" type="Image" id="Done" />
+      </Bindings>
+    </NoDataMessage>
+    <CockpitList name="Display" hasBorder="false" dataSource="ProcessContext::${NAME}_DisplayList.Items[]">
+      <Items name="Items" itemPattern="${NAME}Items">
+        <ItemListLayout>
+          <Tablet>
+            <Default>
+              <Col flex="1">
+                <Row layoutType="itemIdentifierCockpit" bindingId="Row_Name" />
+                <Row layoutType="itemSecondaryCockpit" bindingId="Row_Description" />
+              </Col>
+            </Default>
+          </Tablet>
+          <Phone>
+            <Default>
+              <Col flex="1">
+                <Row layoutType="itemIdentifierCockpit" bindingId="Name" />
+              </Col>
+            </Default>
+          </Phone>
+        </ItemListLayout>
+        <Bindings>
+          <!-- bindings in list are referenced with a leading dot (.) in front of the name. eg. .description -->
+          <Binding target="Row_Name" type="Text" binding=".<YOUR BINDING TO THE SimpleProperty OF THE ListItem OF THE DATASOURCE SPECIFIED ABOVE AS ATTRIBUTE OF CickpitList NODE>" bindingMode="ONE_WAY" />
+          <Binding target="Row_Description" type="Text" binding=".<YOUR BINDING TO THE SimpleProperty OF THE ListItem OF THE DATASOURCE SPECIFIED ABOVE AS ATTRIBUTE OF CickpitList NODE>" bindingMode="ONE_WAY" />
+        </Bindings>
+      </Items>
+    </CockpitList>
+  </CardContainer>

package/templates/contractTemplates/{PR_Process_&_UI/snippets/UI/Page/MasterDetail/Page_MasterDetail_WithDetailGroupsSnipp.xml → YourModule Section/PR/PR_Process_&_UI/_snippets/UI/Page/MasterDetail/Page_MasterDetail_WithDetailGroupsSnipp.xml }

@@ -9,7 +9,7 @@
 			<GroupedList name="MasterList" searchable="${#searchable#}" groupBy="${#groupBy#}" sortBy="${#sortBy#}" master="true" dataSource="${#dataSource#}" direction="${#direction#}" indexBar="${#indexBar#}" swipe="${#swipe#}" hasBorder="${#hasBorder#}" onItemDisclosure="${#onItemDisclosure#}">
 				<Items name="Items" itemPattern="${#itemPattern#}">
 					<!-- 
-						ItemListLayout Node is required. Please press CTRL-Space to select an appropriate snippet
+						ItemListLayout Node is required. 
 						<ItemListLayout></ItemListLayout>
 					-->
 					<Bindings>

package/templates/contractTemplates/{PR_Process_&_UI/snippets/UI/Page/MasterDetail/Page_MasterDetail_WithDetailListSnipp.xml → YourModule Section/PR/PR_Process_&_UI/_snippets/UI/Page/MasterDetail/Page_MasterDetail_WithDetailListSnipp.xml }

@@ -9,7 +9,7 @@
 			<GroupedList name="MasterList" searchable="${#searchable#}" groupBy="${#groupBy#}" sortBy="${#sortBy#}" master="true" dataSource="${#dataSource#}" direction="${#direction#}" indexBar="${#indexBar#}" swipe="${#swipe#}" hasBorder="${#hasBorder#}" onItemDisclosure="${#onItemDisclosure#}">
 				<Items name="Items" itemPattern="${#itemPattern#}">
 					<!-- 
-						ItemListLayout Node is required. Please press CTRL-Space to select an appropriate snippet
+						ItemListLayout Node is required. 
 						<ItemListLayout></ItemListLayout>
 					-->
 					<Bindings>
@@ -31,7 +31,7 @@
 			<GroupedList name="${#name1#}" searchable="${#searchable1#}" groupBy="${#groupBy1#}" sortBy="${#sortBy1#}" dataSource="${#dataSource1#}" direction="${#direction1#}" indexBar="${#indexBar1#}" swipe="${#swipe1#}" hasBorder="${#hasBorder1#}" onItemDisclosure="${#onItemDisclosure1#}" >
 				<Items name="Items">
 					<!-- 
-						ItemListLayout Node is required. Please press CTRL-Space to select an appropriate snippet
+						ItemListLayout Node is required. 
 						<ItemListLayout></ItemListLayout>
 					-->
 					<Bindings>

package/templates/contractTemplates/{PR_Process_&_UI/snippets/UI/Page/MasterDetail/Page_MasterDetail_WithDetailTabsSnipp.xml → YourModule Section/PR/PR_Process_&_UI/_snippets/UI/Page/MasterDetail/Page_MasterDetail_WithDetailTabsSnipp.xml }

@@ -12,7 +12,7 @@
 			<GroupedList name="MasterList" searchable="${#searchable#}" groupBy="${#groupBy#}" sortBy="${#sortBy#}" master="true" dataSource="${#dataSource#}" direction="${#direction#}" indexBar="${#indexBar#}" swipe="${#swipe#}" hasBorder="${#hasBorder#}" onItemDisclosure="${#onItemDisclosure#}">
 				<Items name="Items" itemPattern="${#itemPattern#}">
 					<!-- 
-						ItemListLayout Node is required. Please press CTRL-Space to select an appropriate snippet
+						ItemListLayout Node is required. 
 						<ItemListLayout></ItemListLayout>
 					-->
 					<Bindings>

package/templates/contractTemplates/{PR_Process_&_UI/snippets/UI/Page/MasterDetail/Page_MasterDetail_WithExtendedDetailSnipp.xml → YourModule Section/PR/PR_Process_&_UI/_snippets/UI/Page/MasterDetail/Page_MasterDetail_WithExtendedDetailSnipp.xml }

@@ -9,7 +9,7 @@
 			<GroupedList name="MasterList" searchable="${#searchable#}" groupBy="${#groupBy#}" sortBy="${#sortBy#}" master="true" dataSource="${#dataSource#}" direction="${#direction#}" indexBar="${#indexBar#}" swipe="${#swipe#}" hasBorder="${#hasBorder#}" onItemDisclosure="${#onItemDisclosure#}">
 				<Items name="Items" itemPattern="${#itemPattern#}">
 					<!-- 
-						ItemListLayout Node is required. Please press CTRL-Space to select an appropriate snippet
+						ItemListLayout Node is required. 
 						<ItemListLayout></ItemListLayout>
 					-->
 					<Bindings>

package/templates/contractTemplates/{PR_Process_&_UI/snippets/UI/Page/SingleSection/Page_SingleSectionScreens_ListSnipp.xml → YourModule Section/PR/PR_Process_&_UI/_snippets/UI/Page/SingleSection/Page_SingleSectionScreens_ListSnipp.xml }

@@ -23,7 +23,9 @@
 		<Area areaName="mainArea" areaPattern="SingleElementArea">
 			<GroupedList name="MasterList" searchable="${#searchable#}" groupBy="${#groupBy#}" sortBy="${#sortBy#}" master="true" dataSource="${#dataSource#}" direction="${#direction#}" indexBar="${#indexBar#}" swipe="${#swipe#}" hasBorder="${#hasBorder#}" onItemDisclosure="${#onItemDisclosure#}">
 				<Items name="Items" itemPattern="${#itemPattern#}">
-					<!-- ItemListLayout Node is required. Please press CTRL-Space to select an appropriate snippet<ItemListLayout></ItemListLayout>-->
+					<!-- ItemListLayout Node is required.
+						<ItemListLayout></ItemListLayout>
+					-->
 					<Bindings>
 						<Binding target="${#target#}" type="Text" binding="${#binding#}" bindingMode="ONE_WAY" />
 					</Bindings>

package/templates/templateDefinitions.json

@@ -48,7 +48,7 @@
                 "resources": [
                     {
                         "type": "tree",
-                        "source": "BO_BusinessObject/businessobject/Bo${NAME}",
+                        "source": "YourModule Section/BO/BO_BusinessObject/businessobject/Bo${NAME}",
                         "target": "${MODULE}/BO/${FULL_NAME}"
                     }
                 ],
@@ -82,7 +82,7 @@
                 "resources": [
                     {
                         "type": "tree",
-                        "source": "LO_Listobject/Lo${NAME}",
+                        "source": "YourModule Section/BO/LO_Listobject/Lo${NAME}",
                         "target": "${MODULE}/BO/${FULL_NAME}"
                     }
                 ],
@@ -116,7 +116,7 @@
                 "resources": [
                     {
                         "type": "tree",
-                        "source": "LU_LookupObject/Lu${NAME}",
+                        "source": "YourModule Section/BO/LU_LookupObject/Lu${NAME}",
                         "target": "${MODULE}/BO/${FULL_NAME}"
                     }
                 ],
@@ -157,7 +157,7 @@
                     },
                     {
                         "type": "file",
-                        "source": "DS_DataSource/Ds${NAME}_sf.datasource.xml",
+                        "source": "YourModule Section/DS/DS_DataSource/Ds${NAME}_sf.datasource.xml",
                         "target": "${MODULE}/DS/${FULL_NAME}_sf.datasource.xml"
                     }
                 ]
@@ -196,7 +196,7 @@
                     "FULL_NAME": "${REFERENCE_OBJECT}.${METHOD_FILE_NAME}",
                     "MV": {
                         "fn"    : "getReferenceObjectMethodFolder",
-                        "args"  : ["${TYPE}", "${REFERENCE_OBJECT}"]
+                        "args"  : ["${MODULE}", "${REFERENCE_OBJECT}"]
                     },
                     "REFERENCE_OBJECT_BASE_TYPE": {
                         "fn"    : "getReferenceObjectBaseType",
@@ -210,7 +210,7 @@
                     },
                     {
                         "type": "file",
-                        "source": "BL_BusinessLogic/${REFERENCE_OBJECT}.${NAME}.bl.js",
+                        "source": "YourModule Section/BO/Methods_or_BusinessLogic/${REFERENCE_OBJECT}.${NAME}.bl.js",
                         "target": "${MODULE}/BO/${REFERENCE_OBJECT}/${MV}/${FULL_NAME}.bl.js"
                     },
                     {
@@ -253,7 +253,7 @@
                     "FULL_NAME": "${REFERENCE_OBJECT}.${METHOD_FILE_NAME}",
                     "MV": {
                         "fn"    : "getReferenceObjectMethodFolder",
-                        "args"  : ["${TYPE}", "${REFERENCE_OBJECT}"]
+                        "args"  : ["${MODULE}", "${REFERENCE_OBJECT}"]
                     },
                     "REFERENCE_OBJECT_BASE_TYPE": {
                         "fn"    : "getReferenceObjectBaseType",
@@ -267,7 +267,7 @@
                     },
                     {
                         "type": "file",
-                        "source": "BL_BusinessLogic/${REFERENCE_OBJECT}.${NAME}Async.bl.js",
+                        "source": "YourModule Section/BO/Methods_or_BusinessLogic/${REFERENCE_OBJECT}.${NAME}Async.bl.js",
                         "target": "${MODULE}/BO/${REFERENCE_OBJECT}/${MV}/${FULL_NAME}.bl.js"
                     },
                     {

package/templates/contractTemplates/LO_ListObject/Lo${NAME}/Li${NAME}.listitem.xml

@@ -1,5 +0,0 @@
-<ListItem name="Li${NAME}">
-  <SimpleProperties>
-      <!-- You can use <workspaceRoot>/contractSnippets/LO_ListObject/snippets/ListItemSimplePropertiesSimplePropertySnipp.xml as template for your case -->
-  </SimpleProperties>
-</ListItem>