This discussion is archived
8 Replies Latest reply: Aug 4, 2013 11:18 PM by SelinaChen RSS

New 6.1.1 Key Missing from BaseFeatureConfig?

Trey Explorer
Currently Being Moderated

It appears the new key <add key="GSM.SpecificationTracks.Enabled" value="true" configDescription="Turn on specification tracks to prevent cocurrent conflict of multi-user editing when set to true."/> is possibly missing from the encrypted file that sets all the Base Feature Config.

 

After installing 6.1.1 & 6.1.1.1 we ran ConfigRollup and GSM.SpecificationTracks.Enabled" was not listed at all and the new functionality didnt work. However if you look in the BaseFeatureConfig.config reference file in config/reference it is in there.

To get the new functionality to work, we had to add the key to our CustomerSettings.config.

 

Should we report this in an SR, or was this the intention that it needs to be added to CustomerSettings?

  • 1. Re: New 6.1.1 Key Missing from BaseFeatureConfig?
    SelinaChen Newbie
    Currently Being Moderated

    "GSM.SpecificationTracks.Enabled" exists in BaseFeatureConfig.config, don't worry.

    And to have it work, you should extend it to CustomerSettings.config, so that you can control it by yourself.

  • 2. Re: New 6.1.1 Key Missing from BaseFeatureConfig?
    Trey Explorer
    Currently Being Moderated

    If it exists in BaseFeatureConfig.config then why does it not appear at all when you run ConfigRollup?

    Is it missing from the encrypted BaseFeatureConfig.config file?

  • 3. Re: New 6.1.1 Key Missing from BaseFeatureConfig?
    SelinaChen Newbie
    Currently Being Moderated

    I'm sure it exists, I checked the release pack.

    If you still have question about it, please welcome to send your BaseFeatureConfig.config, I'd like to check.

  • 4. Re: New 6.1.1 Key Missing from BaseFeatureConfig?
    Trey Explorer
    Currently Being Moderated

    Yes Im saying it IS IN the REFERENCE BaseFeatureConfig.config, but it doesnt appear in the output when you run ConfigRollup until you add it to your CustomerSettings.config. That makes me think its not in the encrypted version of the BaseFeatureConfig.config used by the application.

    Do this.

    Make sure the key is NOT in your CustomerSetttings file. <add key="GSM.SpecificationTracks.Enabled" value="true" configDescription="Turn on specification tracks to prevent cocurrent conflict of multi-user editing when set to true."/>

    Now run http://<PLM4P.com>/gsm/WebCommon/AdminForms/ConfigRollup.aspx

    Search for the key in the output.

    Its not there.

    Now add the key to your CustomerSettings.config file and reset IIS.

    Run http://<PLM4P.com>/gsm/WebCommon/AdminForms/ConfigRollup.aspx again

    It now appears in the output.

  • 5. Re: New 6.1.1 Key Missing from BaseFeatureConfig?
    SelinaChen Newbie
    Currently Being Moderated

    Sorry, we have this key contains in 611 but in 6111 it has been removed. In 6111, config GSM.SpecificationTracks.Enabled has been changed into GSM.ChangeConflictPrevention.Enabled, so that we don't contains GSM.SpecificationTracks.Enabled anymore.

  • 6. Re: New 6.1.1 Key Missing from BaseFeatureConfig?
    Trey Explorer
    Currently Being Moderated

    Alrighty now we are getting to something. We are going to submit an SR, because we had to set the old key GSM.SpecificationTracks.Enabled to true in our CustomerSettings config to get the conflict prevention to work and we are running 6111. The 6111 release notes do not mention this new key GSM.ChangeConflictPrevention.Enabled, however the 611 release notes have notes on the GSM.SpecificationTracks.Enabled key. And when we run ConfigRollup we do see the new key as well set to true.

    GSM now performs optimistic locking to help prevent data conflicts. For example, when a User A saves a specification or places a specification in edit mode, the system ensures no one else has edited the specification after User A opened/edited the specification. If another user edited the specification during User A’s editing session, then User A is prevented from saving the specification and overriding the changes the other user made.

    This feature is configurable using the following configuration key. It is turned on by default:

    <add key="GSM.SpecificationTracks.Enabled" value="true"/>

     

     

    Thanks for sticking with me on this!

  • 7. Re: New 6.1.1 Key Missing from BaseFeatureConfig?
    StephenD Newbie
    Currently Being Moderated

    Hello Selina,

     

    Can you please answer the following questions for us?

     

    1. If the old key has really been replaced, why is the key still listed in 6.1.1.1 and working?

    2. Why is the new key not documented?  Is this a documentation bug?

    3. Why is the new key not included in the BaseFeatureConfig?

     

    Thanks,

    Stephen

  • 8. Re: New 6.1.1 Key Missing from BaseFeatureConfig?
    SelinaChen Newbie
    Currently Being Moderated

    1. If the old key has really been replaced, why is the key still listed in 6.1.1.1 and working?

    The old key has been removed in 6.1.1.1.

    2. Why is the new key not documented?  Is this a documentation bug?

    The new key not included is a document bug, I've reported already.

    3. Why is the new key not included in the BaseFeatureConfig?

    The new key has been included in 6.1.1.1 BaseFeatureConfig.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points