New created component is greyed out

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
5
down vote

favorite












I'm attempting to create a simple component in a DEV environment on an SDL Web Cloud (SDL Web Content Manager - Build 8.6.0, SDL Web Content Manager Explorer - Build 8.6.0.45274, Update Version - 0, SDL Web Experience Manager - Build 8.6.0.46292) within the content publication and it's greyed out once I save it. Google search came up empty.



What I've tried:



  • Check the cd_client logs and found no errors.

  • Check that my user/group has full permissions.

  • Check the history of the component and version is 0.1 and with the comment "Creation".

  • Inspect the component using Chrome inspector and found components have the class "ghost" applied to it.

  • Check different browsers (Firefox and IE)

  • Check the documentation for SDL Web Cloud and SDL Web 8.5 for any known issues with no luck.

Note: workflow is enabled on this environment and attempting to add the component to a bundle is also not possible.



Any ideas what may be causing this?










share|improve this question

























    up vote
    5
    down vote

    favorite












    I'm attempting to create a simple component in a DEV environment on an SDL Web Cloud (SDL Web Content Manager - Build 8.6.0, SDL Web Content Manager Explorer - Build 8.6.0.45274, Update Version - 0, SDL Web Experience Manager - Build 8.6.0.46292) within the content publication and it's greyed out once I save it. Google search came up empty.



    What I've tried:



    • Check the cd_client logs and found no errors.

    • Check that my user/group has full permissions.

    • Check the history of the component and version is 0.1 and with the comment "Creation".

    • Inspect the component using Chrome inspector and found components have the class "ghost" applied to it.

    • Check different browsers (Firefox and IE)

    • Check the documentation for SDL Web Cloud and SDL Web 8.5 for any known issues with no luck.

    Note: workflow is enabled on this environment and attempting to add the component to a bundle is also not possible.



    Any ideas what may be causing this?










    share|improve this question























      up vote
      5
      down vote

      favorite









      up vote
      5
      down vote

      favorite











      I'm attempting to create a simple component in a DEV environment on an SDL Web Cloud (SDL Web Content Manager - Build 8.6.0, SDL Web Content Manager Explorer - Build 8.6.0.45274, Update Version - 0, SDL Web Experience Manager - Build 8.6.0.46292) within the content publication and it's greyed out once I save it. Google search came up empty.



      What I've tried:



      • Check the cd_client logs and found no errors.

      • Check that my user/group has full permissions.

      • Check the history of the component and version is 0.1 and with the comment "Creation".

      • Inspect the component using Chrome inspector and found components have the class "ghost" applied to it.

      • Check different browsers (Firefox and IE)

      • Check the documentation for SDL Web Cloud and SDL Web 8.5 for any known issues with no luck.

      Note: workflow is enabled on this environment and attempting to add the component to a bundle is also not possible.



      Any ideas what may be causing this?










      share|improve this question













      I'm attempting to create a simple component in a DEV environment on an SDL Web Cloud (SDL Web Content Manager - Build 8.6.0, SDL Web Content Manager Explorer - Build 8.6.0.45274, Update Version - 0, SDL Web Experience Manager - Build 8.6.0.46292) within the content publication and it's greyed out once I save it. Google search came up empty.



      What I've tried:



      • Check the cd_client logs and found no errors.

      • Check that my user/group has full permissions.

      • Check the history of the component and version is 0.1 and with the comment "Creation".

      • Inspect the component using Chrome inspector and found components have the class "ghost" applied to it.

      • Check different browsers (Firefox and IE)

      • Check the documentation for SDL Web Cloud and SDL Web 8.5 for any known issues with no luck.

      Note: workflow is enabled on this environment and attempting to add the component to a bundle is also not possible.



      Any ideas what may be causing this?







      web8 cme sdl-cloud






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Sep 4 at 8:33









      Tim Alonso

      9510




      9510




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          6
          down vote













          If a component is greyed out when it's just created, this usually means it's created, but not yet checked in.



          There are several causes for this



          • you build the component using custom code, but you save it without checking in


          • when you manually create the component in the CME gui, you save it, but you don't check in the component.


          • some workflow process starts when creating the component, and this needs to be finished before the component is checked in


          • there is some eventsystem code that intercepts the creation of the form and does something, but doesn't check in the result.


          To test, could you open the component (or open the context menu of the component, and choose versioning -> check in ? Normally, then the version 1.0 of the component should be created, and it should no longer be greyed out.






          share|improve this answer




















          • Thanks, Harald, the check-in option is disabled when I checked. There is no event system code and there is no active workflow started as far as I can tell. When creating the component and prompted to add it to a bundle, I'm unable to select the new component.
            – Tim Alonso
            Sep 4 at 9:12










          • can you clarify how you created the component ? Was this using XPM or via the regular CME Gui, or via code ?
            – Harald Hoffelinck
            Sep 4 at 9:31










          • Manually via regular CME GUI.
            – Tim Alonso
            Sep 4 at 9:31






          • 1




            I also can't find a direct explanation. Since you have this on Web 8.5 Cloud, could you ask support to have a look at this ?
            – Harald Hoffelinck
            Sep 5 at 11:28

















          up vote
          6
          down vote













          You may want to check whether there is Workflow set via the Associated Component Process on the Schema.



          enter image description here



          This may put the Component straight into Workflow (as a Version 0.1) without needing it to be added to a Bundle.






          share|improve this answer




















          • The Associated Component Process is set to (None) but the checkbox "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" is selected with a legacy Workflow Process definition. I've checked for any active processes and nothing appears to have been started. I was under the impression that this won't apply on creation, just on modify. Am I missing something?
            – Tim Alonso
            Sep 4 at 9:08






          • 3




            It's this. If you have the "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" tick-box selected then the components need to go through workflow before they are fully checked in. Until then, they will exist in a "reserved" state (appearing greyed out), which is what you are seeing. There will be no active processes because you have not started one via a bundle or otherwise.
            – David Forster
            Sep 6 at 11:47










          • @DavidForster - That sounds familiar, now that you mention it. I think you should put that as a separate answer. If you don’t, then I’ll update my answer in a few days to include your idea (but I’d prefer you to get the credit!). :)
            – Jonathan Williams
            Sep 6 at 15:54










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "485"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19269%2fnew-created-component-is-greyed-out%23new-answer', 'question_page');

          );

          Post as a guest






























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          6
          down vote













          If a component is greyed out when it's just created, this usually means it's created, but not yet checked in.



          There are several causes for this



          • you build the component using custom code, but you save it without checking in


          • when you manually create the component in the CME gui, you save it, but you don't check in the component.


          • some workflow process starts when creating the component, and this needs to be finished before the component is checked in


          • there is some eventsystem code that intercepts the creation of the form and does something, but doesn't check in the result.


          To test, could you open the component (or open the context menu of the component, and choose versioning -> check in ? Normally, then the version 1.0 of the component should be created, and it should no longer be greyed out.






          share|improve this answer




















          • Thanks, Harald, the check-in option is disabled when I checked. There is no event system code and there is no active workflow started as far as I can tell. When creating the component and prompted to add it to a bundle, I'm unable to select the new component.
            – Tim Alonso
            Sep 4 at 9:12










          • can you clarify how you created the component ? Was this using XPM or via the regular CME Gui, or via code ?
            – Harald Hoffelinck
            Sep 4 at 9:31










          • Manually via regular CME GUI.
            – Tim Alonso
            Sep 4 at 9:31






          • 1




            I also can't find a direct explanation. Since you have this on Web 8.5 Cloud, could you ask support to have a look at this ?
            – Harald Hoffelinck
            Sep 5 at 11:28














          up vote
          6
          down vote













          If a component is greyed out when it's just created, this usually means it's created, but not yet checked in.



          There are several causes for this



          • you build the component using custom code, but you save it without checking in


          • when you manually create the component in the CME gui, you save it, but you don't check in the component.


          • some workflow process starts when creating the component, and this needs to be finished before the component is checked in


          • there is some eventsystem code that intercepts the creation of the form and does something, but doesn't check in the result.


          To test, could you open the component (or open the context menu of the component, and choose versioning -> check in ? Normally, then the version 1.0 of the component should be created, and it should no longer be greyed out.






          share|improve this answer




















          • Thanks, Harald, the check-in option is disabled when I checked. There is no event system code and there is no active workflow started as far as I can tell. When creating the component and prompted to add it to a bundle, I'm unable to select the new component.
            – Tim Alonso
            Sep 4 at 9:12










          • can you clarify how you created the component ? Was this using XPM or via the regular CME Gui, or via code ?
            – Harald Hoffelinck
            Sep 4 at 9:31










          • Manually via regular CME GUI.
            – Tim Alonso
            Sep 4 at 9:31






          • 1




            I also can't find a direct explanation. Since you have this on Web 8.5 Cloud, could you ask support to have a look at this ?
            – Harald Hoffelinck
            Sep 5 at 11:28












          up vote
          6
          down vote










          up vote
          6
          down vote









          If a component is greyed out when it's just created, this usually means it's created, but not yet checked in.



          There are several causes for this



          • you build the component using custom code, but you save it without checking in


          • when you manually create the component in the CME gui, you save it, but you don't check in the component.


          • some workflow process starts when creating the component, and this needs to be finished before the component is checked in


          • there is some eventsystem code that intercepts the creation of the form and does something, but doesn't check in the result.


          To test, could you open the component (or open the context menu of the component, and choose versioning -> check in ? Normally, then the version 1.0 of the component should be created, and it should no longer be greyed out.






          share|improve this answer












          If a component is greyed out when it's just created, this usually means it's created, but not yet checked in.



          There are several causes for this



          • you build the component using custom code, but you save it without checking in


          • when you manually create the component in the CME gui, you save it, but you don't check in the component.


          • some workflow process starts when creating the component, and this needs to be finished before the component is checked in


          • there is some eventsystem code that intercepts the creation of the form and does something, but doesn't check in the result.


          To test, could you open the component (or open the context menu of the component, and choose versioning -> check in ? Normally, then the version 1.0 of the component should be created, and it should no longer be greyed out.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 4 at 8:42









          Harald Hoffelinck

          7,3111226




          7,3111226











          • Thanks, Harald, the check-in option is disabled when I checked. There is no event system code and there is no active workflow started as far as I can tell. When creating the component and prompted to add it to a bundle, I'm unable to select the new component.
            – Tim Alonso
            Sep 4 at 9:12










          • can you clarify how you created the component ? Was this using XPM or via the regular CME Gui, or via code ?
            – Harald Hoffelinck
            Sep 4 at 9:31










          • Manually via regular CME GUI.
            – Tim Alonso
            Sep 4 at 9:31






          • 1




            I also can't find a direct explanation. Since you have this on Web 8.5 Cloud, could you ask support to have a look at this ?
            – Harald Hoffelinck
            Sep 5 at 11:28
















          • Thanks, Harald, the check-in option is disabled when I checked. There is no event system code and there is no active workflow started as far as I can tell. When creating the component and prompted to add it to a bundle, I'm unable to select the new component.
            – Tim Alonso
            Sep 4 at 9:12










          • can you clarify how you created the component ? Was this using XPM or via the regular CME Gui, or via code ?
            – Harald Hoffelinck
            Sep 4 at 9:31










          • Manually via regular CME GUI.
            – Tim Alonso
            Sep 4 at 9:31






          • 1




            I also can't find a direct explanation. Since you have this on Web 8.5 Cloud, could you ask support to have a look at this ?
            – Harald Hoffelinck
            Sep 5 at 11:28















          Thanks, Harald, the check-in option is disabled when I checked. There is no event system code and there is no active workflow started as far as I can tell. When creating the component and prompted to add it to a bundle, I'm unable to select the new component.
          – Tim Alonso
          Sep 4 at 9:12




          Thanks, Harald, the check-in option is disabled when I checked. There is no event system code and there is no active workflow started as far as I can tell. When creating the component and prompted to add it to a bundle, I'm unable to select the new component.
          – Tim Alonso
          Sep 4 at 9:12












          can you clarify how you created the component ? Was this using XPM or via the regular CME Gui, or via code ?
          – Harald Hoffelinck
          Sep 4 at 9:31




          can you clarify how you created the component ? Was this using XPM or via the regular CME Gui, or via code ?
          – Harald Hoffelinck
          Sep 4 at 9:31












          Manually via regular CME GUI.
          – Tim Alonso
          Sep 4 at 9:31




          Manually via regular CME GUI.
          – Tim Alonso
          Sep 4 at 9:31




          1




          1




          I also can't find a direct explanation. Since you have this on Web 8.5 Cloud, could you ask support to have a look at this ?
          – Harald Hoffelinck
          Sep 5 at 11:28




          I also can't find a direct explanation. Since you have this on Web 8.5 Cloud, could you ask support to have a look at this ?
          – Harald Hoffelinck
          Sep 5 at 11:28










          up vote
          6
          down vote













          You may want to check whether there is Workflow set via the Associated Component Process on the Schema.



          enter image description here



          This may put the Component straight into Workflow (as a Version 0.1) without needing it to be added to a Bundle.






          share|improve this answer




















          • The Associated Component Process is set to (None) but the checkbox "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" is selected with a legacy Workflow Process definition. I've checked for any active processes and nothing appears to have been started. I was under the impression that this won't apply on creation, just on modify. Am I missing something?
            – Tim Alonso
            Sep 4 at 9:08






          • 3




            It's this. If you have the "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" tick-box selected then the components need to go through workflow before they are fully checked in. Until then, they will exist in a "reserved" state (appearing greyed out), which is what you are seeing. There will be no active processes because you have not started one via a bundle or otherwise.
            – David Forster
            Sep 6 at 11:47










          • @DavidForster - That sounds familiar, now that you mention it. I think you should put that as a separate answer. If you don’t, then I’ll update my answer in a few days to include your idea (but I’d prefer you to get the credit!). :)
            – Jonathan Williams
            Sep 6 at 15:54














          up vote
          6
          down vote













          You may want to check whether there is Workflow set via the Associated Component Process on the Schema.



          enter image description here



          This may put the Component straight into Workflow (as a Version 0.1) without needing it to be added to a Bundle.






          share|improve this answer




















          • The Associated Component Process is set to (None) but the checkbox "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" is selected with a legacy Workflow Process definition. I've checked for any active processes and nothing appears to have been started. I was under the impression that this won't apply on creation, just on modify. Am I missing something?
            – Tim Alonso
            Sep 4 at 9:08






          • 3




            It's this. If you have the "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" tick-box selected then the components need to go through workflow before they are fully checked in. Until then, they will exist in a "reserved" state (appearing greyed out), which is what you are seeing. There will be no active processes because you have not started one via a bundle or otherwise.
            – David Forster
            Sep 6 at 11:47










          • @DavidForster - That sounds familiar, now that you mention it. I think you should put that as a separate answer. If you don’t, then I’ll update my answer in a few days to include your idea (but I’d prefer you to get the credit!). :)
            – Jonathan Williams
            Sep 6 at 15:54












          up vote
          6
          down vote










          up vote
          6
          down vote









          You may want to check whether there is Workflow set via the Associated Component Process on the Schema.



          enter image description here



          This may put the Component straight into Workflow (as a Version 0.1) without needing it to be added to a Bundle.






          share|improve this answer












          You may want to check whether there is Workflow set via the Associated Component Process on the Schema.



          enter image description here



          This may put the Component straight into Workflow (as a Version 0.1) without needing it to be added to a Bundle.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 4 at 8:47









          Jonathan Williams

          12.2k1548




          12.2k1548











          • The Associated Component Process is set to (None) but the checkbox "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" is selected with a legacy Workflow Process definition. I've checked for any active processes and nothing appears to have been started. I was under the impression that this won't apply on creation, just on modify. Am I missing something?
            – Tim Alonso
            Sep 4 at 9:08






          • 3




            It's this. If you have the "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" tick-box selected then the components need to go through workflow before they are fully checked in. Until then, they will exist in a "reserved" state (appearing greyed out), which is what you are seeing. There will be no active processes because you have not started one via a bundle or otherwise.
            – David Forster
            Sep 6 at 11:47










          • @DavidForster - That sounds familiar, now that you mention it. I think you should put that as a separate answer. If you don’t, then I’ll update my answer in a few days to include your idea (but I’d prefer you to get the credit!). :)
            – Jonathan Williams
            Sep 6 at 15:54
















          • The Associated Component Process is set to (None) but the checkbox "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" is selected with a legacy Workflow Process definition. I've checked for any active processes and nothing appears to have been started. I was under the impression that this won't apply on creation, just on modify. Am I missing something?
            – Tim Alonso
            Sep 4 at 9:08






          • 3




            It's this. If you have the "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" tick-box selected then the components need to go through workflow before they are fully checked in. Until then, they will exist in a "reserved" state (appearing greyed out), which is what you are seeing. There will be no active processes because you have not started one via a bundle or otherwise.
            – David Forster
            Sep 6 at 11:47










          • @DavidForster - That sounds familiar, now that you mention it. I think you should put that as a separate answer. If you don’t, then I’ll update my answer in a few days to include your idea (but I’d prefer you to get the credit!). :)
            – Jonathan Williams
            Sep 6 at 15:54















          The Associated Component Process is set to (None) but the checkbox "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" is selected with a legacy Workflow Process definition. I've checked for any active processes and nothing appears to have been started. I was under the impression that this won't apply on creation, just on modify. Am I missing something?
          – Tim Alonso
          Sep 4 at 9:08




          The Associated Component Process is set to (None) but the checkbox "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" is selected with a legacy Workflow Process definition. I've checked for any active processes and nothing appears to have been started. I was under the impression that this won't apply on creation, just on modify. Am I missing something?
          – Tim Alonso
          Sep 4 at 9:08




          3




          3




          It's this. If you have the "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" tick-box selected then the components need to go through workflow before they are fully checked in. Until then, they will exist in a "reserved" state (appearing greyed out), which is what you are seeing. There will be no active processes because you have not started one via a bundle or otherwise.
          – David Forster
          Sep 6 at 11:47




          It's this. If you have the "Any changes made to a Component based on this Schema required approval by a Bundle Workflow Process" tick-box selected then the components need to go through workflow before they are fully checked in. Until then, they will exist in a "reserved" state (appearing greyed out), which is what you are seeing. There will be no active processes because you have not started one via a bundle or otherwise.
          – David Forster
          Sep 6 at 11:47












          @DavidForster - That sounds familiar, now that you mention it. I think you should put that as a separate answer. If you don’t, then I’ll update my answer in a few days to include your idea (but I’d prefer you to get the credit!). :)
          – Jonathan Williams
          Sep 6 at 15:54




          @DavidForster - That sounds familiar, now that you mention it. I think you should put that as a separate answer. If you don’t, then I’ll update my answer in a few days to include your idea (but I’d prefer you to get the credit!). :)
          – Jonathan Williams
          Sep 6 at 15:54

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19269%2fnew-created-component-is-greyed-out%23new-answer', 'question_page');

          );

          Post as a guest













































































          這個網誌中的熱門文章

          Is there any way to eliminate the singular point to solve this integral by hand or by approximations?

          Why am i infinitely getting the same tweet with the Twitter Search API?

          Carbon dioxide