<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bolt Data Connect – Servitization</title>
    <link>/docs/salesforce/servitization/</link>
    <description>Recent content in Servitization on Bolt Data Connect</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sat, 15 Jan 2022 00:00:00 +0000</lastBuildDate>
    
	  <atom:link href="/docs/salesforce/servitization/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Docs: Servitization Testing</title>
      <link>/docs/salesforce/servitization/servitization-testing/</link>
      <pubDate>Fri, 05 May 2023 00:00:00 +0000</pubDate>
      
      <guid>/docs/salesforce/servitization/servitization-testing/</guid>
      <description>
        
        
        &lt;p&gt;Servitization Testing is typically a challenge due to long testing cycles (driven by Monthly / Quarterly output), complicated testing procedures, and error-prone manual entry of sensor / calculated values.&lt;/p&gt;
&lt;h2 id=&#34;testing-console&#34;&gt;Testing Console&lt;/h2&gt;
&lt;p&gt;On the Servitization Plan, the &lt;code&gt;Console&lt;/code&gt; tab provides a Testing Console to ease the testing effort, by automating the required steps and simplifying the process.&lt;/p&gt;
&lt;figure class=&#34;doc figure wide&#34;&gt;&lt;img src=&#34;/docs/salesforce/servitization/assets/servitization-test-console.png&#34;
         alt=&#34;Servitization Test Console&#34;/&gt;&lt;figcaption&gt;
            &lt;p&gt;Servitization Test Console&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;The following steps can be executed in a single click, and just a few minutes:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Post Device Values: By sending an IoT Command to the Gateway / Connector, the IoT Values from a specific Date/Time can be retrieved and reprocessed by the IoT Cloud. Simply select the dates and Covered Things desired. This allows the tester to &amp;ldquo;roll the clock back&amp;rdquo; and control the test without manual data entry (and possible human error).&lt;/li&gt;
&lt;li&gt;Run Sensor Data Job: Executes the Sensor Data Sync Job to download Sensor Data from the IoT Cloud into Salesforce, for the specific Covered Things selected. (See the IoT Setup &amp;gt; Sensor Data settings for details)&lt;/li&gt;
&lt;li&gt;Run Servitization Job: Executes the Servitization Job for this specific Plan and Target Date. (Similar to clicking the Execute button on the Plan)&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;iot-command-template-servitization-target-date&#34;&gt;IoT Command Template: Servitization Target Date&lt;/h3&gt;
&lt;p&gt;The IoT Command Template named &lt;code&gt;Servitization Target Date&lt;/code&gt; will be sent for each Covered Thing in Step 1 above. This template needs to be customized with specific values and the appropriate connector id.&lt;/p&gt;
&lt;dl&gt;
&lt;dt&gt;Topic&lt;/dt&gt;
&lt;dd&gt;Update with the appropriate MQTT Topic for the Connector in use&lt;/dd&gt;
&lt;dt&gt;Body&lt;/dt&gt;
&lt;dd&gt;Update with any custom fields / values needed by the Connector&lt;/dd&gt;
&lt;/dl&gt;
&lt;figure class=&#34;doc figure wide&#34;&gt;&lt;img src=&#34;/docs/salesforce/servitization/assets/iot-command-template.png&#34;
         alt=&#34;Servitization Target Date Command Template&#34;/&gt;&lt;figcaption&gt;
            &lt;p&gt;Servitization Target Date Command Template&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

      </description>
    </item>
    
  </channel>
</rss>
