Setting a property – Echo Method

This Post has been viewed : 43,169 Times


22 Responses to Setting a property – Echo Method

  1. Hi,

    I checked the Use of Set Property, but what i am observing is that :

    Rest of all propeties are not comming as Output(SiebelMessage) , which we are not setting some LITERAL values in Input Arguments.
    Can you please tell me, is this correct or i am making some mistake in WF.

    Let me know if my question is not clear to You guys

    Piyush

  2. Hi,

    I checked the Use of Set Property, but what i am observing is that :

    Rest of all propeties are not comming as Output(SiebelMessage) , which we are not setting some LITERAL values in Input Arguments.
    Can you please tell me, is this correct or i am making some mistake in WF.

    Let me know if my question is not clear to You guys

    Piyush

  3. I don’t quite understand your question.

    You mean that only the properties that you are trying to set are remaining in property set and rest others are gone?

  4. I don’t quite understand your question.

    You mean that only the properties that you are trying to set are remaining in property set and rest others are gone?

  5. I don’t quite understand your question.

    You mean that only the properties that you are trying to set are remaining in property set and rest others are gone?

  6. Yes Neel … In the output of Workflow Utilities block i am getting only the properties that i am trying to set, and rest others are gone.
    Do you have any idea why it is happening like this

    Thanks
    Piyush

  7. Yes Neel … In the output of Workflow Utilities block i am getting only the properties that i am trying to set, and rest others are gone.
    Do you have any idea why it is happening like this

    Thanks
    Piyush

  8. I will not be able to answer that questions without looking at input and output arugments of workflow.

    but most probably you are passing a different input and catching it in different output resulting in creation of a new propertyset with only the values that you have passed as input.

    send the XML of workflow in email and I will try to look at it.

  9. I will not be able to answer that questions without looking at input and output arugments of workflow.

    but most probably you are passing a different input and catching it in different output resulting in creation of a new propertyset with only the values that you have passed as input.

    send the XML of workflow in email and I will try to look at it.

  10. I will not be able to answer that questions without looking at input and output arugments of workflow.

    but most probably you are passing a different input and catching it in different output resulting in creation of a new propertyset with only the values that you have passed as input.

    send the XML of workflow in email and I will try to look at it.

  11. Hi Neel.
    I am facing same problem as piyush is facing. What I did was just query on IO and set the one of property in parent IC.

  12. Hi Neel.
    I am facing same problem as piyush is facing. What I did was just query on IO and set the one of property in parent IC.

  13. Hi Neel.
    I am facing same problem as piyush is facing. What I did was just query on IO and set the one of property in parent IC.

  14. It seems everybody who is facing problem is using Siebel 8.0. I implemented this in Siebel 7.7. I am in process of getting hands on Siebel 8.0, will try to see what is causing this behavior.

  15. It seems everybody who is facing problem is using Siebel 8.0. I implemented this in Siebel 7.7. I am in process of getting hands on Siebel 8.0, will try to see what is causing this behavior.

  16. Hi All

    Thanks to Neel for posting this, it’s very useful. However I have a few points to add regarding this “feature”…

    1. It is not necessary to create an empty property set. Using the dot notation Siebel will construct a property set from nothing using the inputs you provide. Of course the resulting property set will only contain the elements that you provide as inputs, so if your hierarchy contain additional elements that you will not be setting then you should use the ‘PRM ANI Utility Service’ business service as per Neel’s example.

    2. Input Arguments are limited to 75 characters. When using this dot notation it is very easy to exceed this 75 character limit. If this is the case then you should use the ‘SetProperty’ method of the ‘PRM ANI Utility Service’ business service.

    And finally, I’ve seen a few comments saying that in order for this to work in Siebel 8 the SiebelMessage parameter should have the highest Sequence… well I’ve just been playing around in version 8.1.1.7 and this was not the case for me. I had some dot notation input arguments with a higher Sequence than the SiebelMessage and some with a lower Sequence and it all worked just fine for me. Maybe this only applies to later versions of Siebel, who knows!

    Regards

    Mark

  17. >> And finally, I’ve seen a few comments saying that in order for this to work in Siebel 8 the SiebelMessage
    >> parameter should have the highest Sequence… well I’ve just been playing around in version 8.1.1.7 and this
    >> was not the case for me.
    At this very moment working in 8.1.1.11 and when the Msg sequence is higher than the properties I want to add they are ignored.
    Apparently sequence is important (again).

    Also having the problem that adding new properties eliminates all existing ones.
    Anyone have a solution for that by now?
    (Apart from explicitly adding those again…)

    Thanks,
    Chip

  18. I’m using Siebel 8.1.1.11. When the property set (say SiebelMessage) has a higher Sequence than the Property Name inputs, the Echo method will keep the existing property names and only updates the ones you set in your Output Arguments.

  19. The method which worked for me was ,

    Siebel Message should have a higher sequence (for ex: 8) than the argument which sets the property in the siebel message (for ex: 5). Also, Siebel Message Output Argument should have sequence more than the two input arguments. (for ex : 10)

    Please try once. I have tried in both 8.1.1.11 and 8.1.1.4 and the above method worked in both. 🙂

    • For Ex : SiebMessage.ListOfAccount_wizard_IO.Account.Name – this should have the sequence , lets say – 0.
      Then SiebMessage – should have the sequence , any other number which is more than 0 (lets say 1)

      A minor correction on my previous comment. Output Argument sequence doesnt play any role in Workflow Utilities setting any value in a property set.

Leave a Reply

Contribute