1 2 Previous Next 22 Replies Latest reply on Jul 24, 2019 12:08 PM by Melisa Kommala

    How to chain many ''Build Input Set'' elements in bmc DWP?

    Zi Sang
      Share This:

      I want to connect 3 Build Input Set with Create Remedy Work Order, and I have 18 input Variables (Variable Type is Text),

      However, a single Build Input Set activity provides fields to create only 10 key=value pairs, so only 10 key=value pairs are not enough for me.

       

      In the following link, it shows ''People can chain Build Input Set elements to create any number of parameters.''  

      Defining custom parameters - Documentation for BMC Digital Workplace Advanced 3.5 - BMC Documentation

       

      I can chain 2 Build Input Set without any problem. What i did, is the setting in the second ''Build Input Set'':

      Input Map  -> click Edit of ''Input Set1'', and then choose Output of the first  ''Build Input Set''

       

       

      Also, i went to the ''Create Remedy Work Order'', in Detail and Detail2, i enter the Input from the first ''Build Input Set'' and the Input from the second ''Build Input Set''.

       

      And all the Variables from both ''Build Input Set'' will be shown in Remedy Ticket.

       

      Part of my Workflow is shown as follows:

       

       

       

      HOWEVER, when i chain 3 ''Build Input Set'' together, only the variables from the first ''Build Input Set'' will be shown.

      How can i chain 3 or more ''Build Input Set''  together??  Tony Chung

       

       

       

      Thank you!

        • 2. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
          Hugh Fairfield

          Hello,

           

          Instead of using the outputs of the previous input sets, please use the inputs to pass to the next input et like so:

          Screen Shot 2018-06-11 at 11.53.55 AM.png

           

          That will resolve your issue.

           

          Cheers,

           

          Hugh

          • 3. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
            Zi Sang

            Hi Hugh,

             

            thank you, i have tested it, but it doesn't work. In the Work Order, only the values of the 1st Build Input Set are there, the value from the 2nd and 3rd are not there.

             

            Did you have the same case as me? Are there any other details may cause the problem?

             

            Regards,

            Zi Sang

            • 4. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
              Amita Sharma

              John Gallagher : Hi John ,

                                                                     Could you please help here.I'm facing the problem of chaining 3 build input set but above solution doesn't work .Appreciate if you can guide on same .

               

              Thanks,

              Amita

              • 5. Re: How to chain many ''Build Input Set'' elements in bmc DWP?

                Hi Amita Sharma,

                 

                Here is a simple way to understand how to chain multiple build input sets.

                 

                In the following workflow, I use three Build Input Sets leading to a Create Remedy Work Order With Identifiers:

                • For WO Inputs 1 - 10, I completed all key (field name) and value pairs.
                • For WO Inputs 11 - 20, I completed all key (field name) and value pairs.

                 

                In WO Inputs 21 - 23 - MERGE, I assign the Output > Inputs as shown:

                Then I added an additional 3 key (field name) and value pairs. The activity WO Inputs 21 - 23 - MERGE combines the first two Build Input Set activities with the additional key/value pairs to produce an object that contains 23 key/value pairs.

                 

                In WO Create, I insert the object with 23 key/value pairs into the first Detail field only. You do not need to use both Detail and Detail2 fields:

                 

                Based on this understanding, you should be able to create multiple build input sets that suit your needs.

                 

                When submitting values to the Work Order Detail fields, ensure that the value's data type matches the specific Detail/Details2 field data types. I tried to explain it as best that I could when I wrote this original documentation page, but the concept is more easily understood in practice than through the written word.

                Remedy connector configuration and usage - Documentation for BMC Digital Workplace Advanced 3.5 - BMC Documentation

                2 of 2 people found this helpful
                • 6. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
                  Marek Ceizel

                  Hi Tony Chung,

                   

                  Does this mean you can use Input Set in any Create Element ?

                  I mean e.g.

                  - for Set Entry you put Inputs into Field Values

                  - for Create WO you put Inputes into Detail (btw-when is the Detail2 used?)

                  - but where can I put the inputs for Create Incident ?

                   

                  thanks

                  Marek

                  • 7. Re: How to chain many ''Build Input Set'' elements in bmc DWP?

                    > for Set Entry you put Inputs into Field Values

                    Yes... when you use Set Entry you build the key/value pairs (using database field id as the key) and insert them into the Field Values field to update an existing record.

                     

                    > but where can I put the inputs for Create Incident ?

                    You have to Create Incident (use Create Incident With Identifiers) first and then update the created incident with Set Entry, as John demonstrated. Alternatively, you can use Build Input Set to map all the required incident form fields, and then use Create Entry to post into HPD:Help Desk or another incident form.

                     

                    > for Create WO you put Inputes into Detail (btw-when is the Detail2 used?)

                    The Detail and Detail2 fields were created to mimic the layout of the WOI:WorkOrder fields. However, the implementation is such that you can use Detail, Detail2, or both, as long as the fields you post into the Work Order are arranged in order based on the data types.

                     

                    Both Detail and Detail2 work the same way. You could create the work order in my example by inserting the build input set into Detail2 instead of Detail. You could also map the merged input sets "1 - 10" and "11 - 20" into Detail, and "21 - 23" into Detail2. The key is that the fields must all be in order.

                     

                    This might be another way to explain chaining:

                     

                    1. Start with one Build Input Set to map 10 fields

                     

                    2. Insert the output > inputs of the first build input set into the second Build Input Set. Then map 10 more fields to this input set.

                     

                    Effectively, this merges the new input set with the items from the previous input set.

                    3.  Insert the output > inputs of the second build input set into the third Build Input Set. Then map the remaining fields.

                     

                    Continue chaining input sets in this manner, where each input set adds to the inputs from the previous input set.

                    4. Finally, insert the output > inputs of the last Build Input Set into the Detail field, to send the merged list of inputs > 10 to the work order.

                     

                    The difference between the input sets in work orders vs Create Entry/Set Entry is that the Create Entry/Set Entry requires that the keys relate to specific database fields, otherwise the operation will error.

                     

                    However, the difficulty of build input sets in work orders (as mentioned above) is that field values must be supplied in order of the data types that Remedy Detail/Detail2 tabs expect.

                    4 of 4 people found this helpful
                    • 8. Re: How to chain many ''Build Input Set'' elements in bmc DWP?

                      Hi Zi Sang. I am so sorry that you tagged me on this question 8 months ago and I didn't respond. I haven't worked with BMC for almost a year, and just recently returned to the world of BMC Digital Workplace Catalog consulting.

                       

                      For anyone else who reads this page, I wanted to raise an additional concern based on your use case of 18 fields of Text data type. When you assign key/value pairs to the Build Input Sets, you must not assign text values to non-text data fields. Because WO Type Field 01 to 05 and 10 to 23 are all Text data type, there is a block between 06 to 09 that you will have to skip, or fill with the correct data type.

                       

                      One way we've been solving this use case is to label the fields as "Unused xx" (all labels must be unique).

                       

                      So assuming that you have questions mapped to values that capture answers into variables as in the following example:

                      • First Name / [Text Value 01]
                      • Last Name / [Text Value 02]
                      • Job Title / [Text Value 03]
                      • Job Function / [Text Value 04]
                      • Contact Number / [Text Value 05]
                      • Work Location / [Text Value 06]

                       

                      You would map the Build Input Set as follows:

                       

                      • Key1: "First Name"
                      • Value1: [Text Value 01]

                       

                      • Key2: "Last Name"
                      • Value2: [Text Value 02]

                       

                      • Key3: "Job Title"
                      • Value3: [Text Value 03]

                       

                      • Key4: "Job Function"
                      • Value4: [Text Value 04]

                       

                      • Key5: "Contact Number"
                      • Value5: [Text Value 05]

                       

                      (Skip this next batch of fields that are not Text data type)

                      • Key6: "Unused 06"
                      • Key7: "Unused 07"
                      • Key8: "Unused 08"
                      • Key9: "Unused 09"

                       

                      • Key10: "Work Location"
                      • Value10: [Text Value 06]

                       

                      Then you can proceed with the remaining 12 text fields without needing to skip any more.

                       

                      Hope this helps!

                       

                      -Tony

                       

                      ** Edit: Wrapped the Key names in double quotes, like you would in a Build Input Set.

                      4 of 4 people found this helpful
                      • 9. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
                        Zi Sang

                        Hi Tony Chung,

                         

                        thank you very much for your reply, that is very helpful to us!

                        As we sometimes need a lot of field in a WO.

                         

                        Wish you all the best!

                         

                        Best regards,

                        Zi Sang

                        • 10. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
                          Amita Sharma

                          Hi Tony Chung

                           

                                   Thanks for the solution and detailed Explanation.

                           

                          Best Regards,

                          Amita

                          • 11. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
                            Stefan Koenig

                            Hi everyone,

                             

                            first of all, thanks to you Tony Chung for your insight into this.

                            I got one additional question. Can anyone explain to me how to use WO Type Fields 1 to 5 AND WO Type Fields 48 and 50?

                            Anytime I try this, I either have the information in the wrong fields, or no information at all.

                             

                            I'm going crazy about this, please help me!

                            • 12. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
                              Tony Chung

                              Hi Stefan!

                               

                              For your use case

                              If you are using Create Remedy Work Order/Create Remedy Work Order With Identifiers

                              You must chain together multiple Build Input Set elements as I described, where you insert unused field labels for WO Type Field 6 to 30, and 32.

                               

                              Remember this example, where we inserted "Unused XX" as the labels for empty fields:

                               

                              (Skip this next batch of fields that are not Text data type)

                              • Key6: "Unused 06"
                              • Key7: "Unused 07"
                              • Key8: "Unused 08"
                              • Key9: "Unused 09"
                              • ...

                               

                              How this could look with your use case, and to ensure that all input sets are create a merged list in the order that the work order requires:

                              • Build Input Set 1
                                • Key 1 to 5: Key/Value pairs [this will populate WO Type Field 1 to WO Type Field 5]
                                • Key 6 to 10: "Unused XX" (replace XX with number)
                              • Build Input Set 2
                                • Input Set 1: (output > inputs from Build Input Set 1)
                                • Key 1 to 10: "Unused XX" (replace XX with numbers 11 to 20)
                              • Build Input Set 3
                                • Input Set 1: (output > inputs from Build Input Set 2)
                                • Key 1 to 10: "Unused XX" (replace XX with numbers 21 to 30)
                              • Build Input Set 4
                                • Input Set 1: (output > inputs from Build Input Set 3)
                                • Key 1: Key/Value pair [this will populate WO Type Field 48]
                                • Key 2: "Unused 32"
                                • Key 3: Key/Value pair [this will populate WO Type Field 50]
                              • Create Work Order With Identifiers
                                • (standard values for contact/customer)
                                • Details: (output > inputs from Build Input Set 4)

                               

                              If you are using Create Entry to create a Remedy object (Incident, WO, etc.) manually

                              • Build Input Set (as many as required)
                                All inputs use DB field names, so you only need to directly address
                                • (Fields required to create the artifact)
                                • WO Type Field 01
                                • WO Type Field 02
                                • WO Type Field 03
                                • WO Type Field 04
                                • WO Type Field 05
                                • WO Type Field 48
                                • WO Type Field 50

                               

                              I hope this helps.

                               

                              -Tony

                              2 of 2 people found this helpful
                              • 13. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
                                Tony Chung

                                To close the loop - I think Marek and I discussed this on another thread. But in the cases where the DWP Remedy connector activity doesn't have a field for "Inputs", then you need to create the artifact first, then use Set Entry with Build Input Set to update the additional fields.

                                 

                                This works sufficiently well for Incident and Change. However, you cannot update the Work Order Assignment fields after creating a Work Order, which is why I had to use Create Entry to write to WOI:WorkOrderInterface_Create and manually set the Work Order Assignment fields (and all the other fields) by using multiple Build Input Sets.

                                 

                                -Tony

                                2 of 2 people found this helpful
                                • 14. Re: How to chain many ''Build Input Set'' elements in bmc DWP?
                                  John Kraft

                                  I've been trying to pass values to the details field of a second Work Order and am not having much luck, perhaps Set Entry would work here too? The use case is I pass the values using an Input set to a Work Order (no problem), the agent changes some of these during the resolution of the case, I pull those back using Get Entry by query (again no problem thanks to some help from here) I then want to pass those to the details tab of a second WO and have limited success. I know the process variables are set, I can pass them to an in app notification or even to the description of the second work order, but not to the Details. I can also create a second Input set but it will not allow me to pass again to Fields 1-10, I can chain them and pass to 11-20 but that's not really how I need it to work. Is there a way with Set Entry? Or does anyone have any ideas on how to accomplish this?

                                   

                                  Thanks in advance,

                                  John

                                  1 2 Previous Next