Loading
Industries Order Management
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Set Up Non Case-Specific and Case-Specific Components

          Set Up Non Case-Specific and Case-Specific Components

          A common approach for setting up components for updating records during order fulfillment includes setting up five non-case specific artifacts only once, and then consuming them through two case-specific artifacts as you go.

          You do not need to make any changes to non-case-specific artifacts. However, this capability is not part of the product and you have to install the components manually.

          Setting Up Non Case-Specific Components

          You set up these components only once.

          1. Create a new field for Orchestration Item and Orchestration Item Definition objects. This field will specify which load DataRaptor to invoke during the fulfillment process.

            • Name: DataRaptor to Invoke

            • Field name: Dataraptor_to_Invoke

            • Type: Text

          2. Create a new Custom_AutoTaskInvokeDR Apex class using Apex code.

          3. To Invoke DataRaptor, create a new Custom_AutoTaskPostDR Apex class using Apex code.

          4. Create a new InvokeDRUpsert auto-task item implementation.

            Item Implementation example: InvokeDRUpsert.
          5. Import the Integration Procedure and the DataRaptor using the Integration Procedure for DR Update.json datapack.

          Setting Up Case-Specific Components

          You set up these components for each scenario.

          1. Based on your requirements, create a DataRaptor to update or create records in Salesforce. Input for this DataRaptor is provided by the AutoTaskExtractObject Dataraptor configured previously.

            As a reference, you can use this sample DataRaptor that updates customer account effective date. DataRaptor input has the following format, so you can easily update one of these records.

            {
             "customerAccount": {
              "Name": "Eleanor Coleman Subscription 1",
              "Id": "0019E00000nP7wqQAC"
             },
             "order": {
              "Id": "8019E000000WvQGQA0",
              "OrderNumber": "00004310"
             },
             "orchestrationPlan": {
              "Name": "Plan0001322",
              "Id": "a2Q9E000000RkLoUAK"
             },
             "fulfillmentRequest": {
              "Name": "FR0011539",
              "Id": "a1j9E000000SKeuQAG"
             },
             "orchestrationItemDefinition": {
              "Id": "a2N9E000000LRDUUA4",
              "Name": "Disconnect Offer"
             },
             "orchestrationItem": {
              "Id": "a2O9E000000HUnYUAW",
              "Name": "Disconnect Offer"
             },
             "fulfillmentRequestLine": {
              "Name": "FRL0025937",
              "Id": "a1i9E000000N30NQAS",
              "productName": "Offer Provisioning RFS Spec",
              "productId": "01t9E000003AohVQAS"
             }
            }
          2. Follow a standard process to configure a new auto-task in your orchestration plan definition. Note the two critical elements:

            • Item Implementation: Set to InvokeDRUpsert

            • Dataraptor to Invoke: Set to your case-specific DataRaptor as indicated in the previous step.

              Orchestration Item Definition example: Update Target MDN.

          Results

          The components are created.

           
          Loading
          Salesforce Help | Article