Component definition

Similar Questions

• RT construction specifications: category of component definition does not

  Hello

  I use LabVIEW 2013 SP1 f2, with real-time 13.0.1

  When I open the properties page of a build specification Application in real-time (to run on a cRIO-9075) and select the category of component definition, I find that the following occur:

  -LabVIEW unresponsive and think for a while. It takes about 20-30 seconds to finally display the component definition page.

  -When I click on create a component definition file (.cdf), nothing happens. As I write this, I see 'required software components', and then they are grayed out: "The software component Description" and "Software version" - but there is nothing to choose or change?

  -If I click on another category, it takes in the order of 20 seconds to finally see the establishment of this category.

  -To close the build specification (press OK), it also takes a long time (more than 60 seconds).

  -Things are fine with the construction specifications if I ever fall into the category of component definition.

  Everyone knows this?

  Any help would be appreciated.

  Hey Chris,

  I believe that the next patch is the solution you're looking for.

  LabVIEW Real-time Module 2013 SP1 Application Builder Patch details

  http://digital.NI.com/public.nsf/allkb/D72B45C6905D327A86257CC800547992?OpenDocument

  There is a link to download the patch at the bottom of this page.

  Kind regards

  Ryan

• Deploying an application by using a component definition file does not work (cRIO 9035 - LV2015)

  Hello
  I created an application for the cRIO 9035 only in real-time with the component definition file, but when I try to deploy with MAX, I don't see the application - MAX has the dialog add/remove software standards. The files are created in the folder "National Instruments\RT Images\User Components".
  I was able to do with cRIO 9068 in the past with no problems. Do you know what I'm missing?
  I want to sent build files to a colleague from another place so it can deploy on a similar system without me having to create a large image with the wheel for every little change in the code.
  Thank you!

  Hello, Lucien.

  What you describe is actually a known problem with the cRIO-903 x family. It is already a CAR on the same subject when I won't be able to give you a deadline for a solution, it is already handled by R & D. The number of CAR is 545686, so if you see a bug in trouble with that number in a future version, it means, it was fixed.

  Unfortunately, currently there is no workaround solution identified, so the only way to get the application running on any cRIO-903 x is either by pushing through a project, or deploy an image (this is what we are trying to avoid the definition of the component).

  Kind regards

• Persistent componement definition data

  Hello

  I use a definition of componnement of unlimited entry of object in my application, but when the application is near, all objects are deleted. I use some QSettings to store a lot of data, but how to keep a container?

  So this is an example of my application:

  hand. QML

  page{
      container{
          id: root
  
          textField{
             id: input
          }
          button{
              text: "add"
              onClicked {
                   var createdControl = new.createObject();
               root.add(createdControl);
               createdControl.text = input.text
              }
          }
      }
      attachedObjects: [
           ComponentDefinition {
               id: new
               source: "new.qml"
           }
       ]
  }
  

  and with another qml file, I add what I want.

  I just have this when I open the app, it'll be the same previous in the root container.

  Hi all and thanks for your reply!

  I found my answer on a sample here

  This is a sample Blackberry app and they use serialization to store objects.

  bool FileStorage::serializeDataModel(int lastID, GroupDataModel* model, QDataStream* stream)
  {
      // This is a simple serialization function.
      // For more info on dealing with complex types,
      // or incorporating file versions see "Serializing data type in Qt"
      // http://qt-project.org/doc/qt-4.8/datastreamformat.html
      bool addedData = false;
  
      *stream << lastID;
      if (stream->status() == QDataStream::Ok) {
          for (int i = 0; i < model->size(); i++) {
              Person *person = (Person *) model->children()[i];
              *stream << person->customerID() << person->firstName()
                      << person->lastName();
              if (stream->status() != QDataStream::Ok) {
                  return addedData = false;
              }
          }
          addedData = true;
      }
  
      return addedData;
  }
  

• Manipulate the properties of component definition

  Currently I have containers that are separate pages in main.qml

  pages: main.qml, CustomContainer.qml

  Page {
    CustomContainer{
       id: myCustomContainer
    }
  
  }
  

  I want to use this

  Page {
    attachedObjects: [
      componentDefinition: {
         id: myCustomContainer
         source: "CustomContainer.qml"
      }
    ]
  
  }
  

  I want to make the definitions of component so I can destroy them when not used however

  I don't know how to access the properties of CustomContainer subsequently

  Here are some examples of how I do now

  Page {
    CustomContainer{
       id: myCustomContainer
    }
  
    onSomePropertyAliasChanged: {
  
    }
  }
  

  or

  myCustomContainer.somePropertyAlias = somethingNew
  

  Although more sense, you should be able to access the standard way, if for example alias property in the component of property you want to edit and navigate through the object you created...

                          myPage.source = "Custom.qml";
                          var page = myPage.createObject();
                          page.myProperty = "test";
  

  // Custom.qml
  
  Page {
      property alias myProperty: lab.text
  
      Label {
          id: lab
          text: "Replace me"
      }
  }
  

• Send the property in the component definition

  I have an object attached with a webview on my page qml

  attachedObjects:]

  {ComponentDefinition}

  ID: statPortalDef

  {Page}

  string urlString property

  WebView {}

  ID: webView

  URL: urlString

  }

  }

  }

  ]

  I'm trying to create and define this webview url with the following

  statPopUp = statPortalDef.createObject)

  activePane.push (statPopUp)

  statPopUp.urlString = ""http://google.com " "

  But set the urlString always breaks the code. Does anyone have advice on how I can accomplish sending my url in the attached webview?

  try to add "var" in front of statPopup to make a local variable that is accessible.

• Destroy the definition component qml in c ++ destructor

  I install some components, but they can only be destroyed if the application will be closed.  Currently, a mistake is cause attesting that they are not made when the application is closed.

  What I am unsure of is how to reference the alias or objectname to a definition of compoenent in c ++ and then destroy it.

  ApplicationUI::~ApplicationUI()
  {
    // Destroy the sound manager.
      ComponentDefinition *myDef = bb::cascades::Application::instance()->findChild("myDef");
          qDebug() << "Destroying Definition";
          myDef->destroy();
  }
  

  Only, I was not able to find how to link the component definition in c ++ because it doesn't have a #include<>

  If not, is there something in qml who inform me just before the application closes, so can I do this?

  Normally, you can solve it by setting the parent of all objects you create in your definition. The parent must be something that you know will be destroyed when your application is closed, as the app itself class.

  I don't think you should look for ComponentDefintion but because it's just a factory for components, you do not create. You should rather look for the type of object that creates the definition.

  Also, do you you know that some objects of Cascades don't clean up after them properly and may generate errors no 'no' even if you do everything right. Why don't post it your console error messages because it can help you get an answer better than this one.

  slashkyle wrote:

  I install some components, but they can only be destroyed if the application will be closed.  Currently, a mistake is cause attesting that they are not made when the application is closed.

  What I am unsure of is how to reference the alias or objectname to a definition of compoenent in c ++ and then destroy it.

  ApplicationUI::~ApplicationUI()
  {
    // Destroy the sound manager.
      ComponentDefinition *myDef = bb::cascades::Application::instance()->findChild("myDef");
          qDebug() << "Destroying Definition";
          myDef->destroy();
  }
  

  Only, I was not able to find how to link the component definition in c ++ because it doesn't have a #include<>

  If not, is there something in qml who inform me just before the application closes, so can I do this?

• Access a drop-down list component created in fom runtime C++

  Hello everyone.

  I included a file "Settings.qml" as a ComponentDefinition in my file "main.qml" as follows:

  *******************************
  main.qml
  *******************************
  
  Page {
      id: page
  
      //App menu
      Menu.definition: MenuDefinition {
          settingsAction: SettingsActionItem {
              title: "Settings"
              imageSource: "asset:///icons/ic_settings.png"
              onTriggered: {
                  var settings = settingsSheet.createObject(_cam);
                  settings.open();
              }
          }
      }
  
      //Main container
      Container {        Camera {            id: cameraQML            objectName: "cameraQML"        }    }
  
      //Attached objects
      attachedObjects: [
          //*****this is the component definition****
          ComponentDefinition {
              id: settingsSheet
              source: "Settings.qml"
          }
      ]
  }
  

  Then, in the "Settings.qml" file, I have something like that.

  On the crack of onCreationCompleted I call you access of wich C++ function to the cameraQML component and gets the available resolution values and add them to the drop down list component.

  ***********************Settings.qml***********************
  
  Sheet {
      id: settingsSheet
      objectName: "settingsSheet"
      peekEnabled: true
      content: Page {        Container {            DropDown {
                  title: "Capture Resolution"
                  objectName: "resolution"
  
                  options: [
                      Option {
                          text: "16:9"
                          value: 16/9
                      }
                  ]
  
                  onCreationCompleted: {
                      _cam.loadResolutionValues();
                  }
  
                  onSelectedValueChanged: {
                      //_cam.selectResolution(selectedValue);
                  }
              }
          }    }}
  

  The PROBLEM comes when I try to access the menu item drop down because, even if I get error when you call the function findChild(), I do when I try to add Options by calling the add() function:

  ******************applicationui.cpp******************
  
  AbstractPane* root;Camera* cameraQML;DropDown* resolutionsDD;
  
  void AppliactionUI::ApplicationUI() {    //code...    QmlDocument *qml = QmlDocument::create("asset:///main.qml").parent(this);    qml->setContextProperty("_cam", this);    root = qml->createRootObject();    cameraQML = root->findChild("camera");    //code...}void ApplicationUI::loadResolutionValues() {
      QVariantList reslist = camaraQML->supportedCaptureResolutions(CameraMode::Photo);
                  //**I don't get error by calling this function
          resolutionsDD = root->findChild("resolution");
  
          //**The app do crashes when calling any of these three functions
      //resolutionsDD->setTitle("Choose an option");        //resolutionsDD->removeAll();
      //resolutionsDD->remove(resolutionsDD->at(0));    for (int i = 0; i < reslist.count(); i++) {
          qDebug()<<"QVatiant value:"<add(Option::create().text(res.width()+"x"+res.height()).value(reslist[i]));
      }
  }
  

  I thought it was a problem with the type of value, I was put in the service. value() when you create an option, but then I realized that, while trying to change the title from the drop-down list, or delete i ' ts options that the application crashed also.

  This makes me think that the problem is that I'm not a correct reference for component drop-down menu QML due to the fact that this drop-down list does not exist when the application starts and is created until the user opens the Settings.qml file. Also, I think that this is a problem with all that stuff parent and child, but of course, it's just a feeling.

  I'd really appreciate your help on this type of problem. I'm not experienced enough to know what is the right way to get a reference of work to the drop down list component in question in a situation like this

  Thank you very much in advance!

  P.D. I'm sorry, I know that my English is not very good. Hope you do not misunderstand

  Hello
  Very probably findChild returns NULL and a NULL pointer dereference causes the crash. I remember there was problems with findChild during the use of the leaves.

  Try from the drop-down list directly to the function as an argument:

  (1) in applicationui.cpp:

  After:
  QmlDocument *qml = QmlDocument::create("asset:///main.qml").parent(this);
  
  Add:
      // This is needed for passing DropDown in function parameters from QML to C++
      qmlRegisterType("bb.cascades", 1, 0, "DropDown");
  

  (2) modify the function declaration for:

  Q_INVOKABLE void loadResolutionValues(bb::cascades::DropDown *dropDown);
  

  (3) in QML:

  DropDown {
    id: dropDown
    ...
    onCreationCompleted: {
       _cam.loadResolutionValues(dropDown)
  
       // _cam.loadResolutionValues(this) // maybe this will also work, but I haven't checked
  
    }
  }
  

• Delete a dynamic component created with QML?

  Hello

  How can I keep the reference to the created object, for example to remove it later.

  In the example below the reference "createdControl" is stored in a local variable of Manager 'onClicked' and is not accessible afterwards.

  It is not possible to use a property of the container to store, because then I need to specify a data type (curiously its possible to store it in a javascript imported the file into a variable typless...).

  Therefore this reference seems to be pretty useless at the moment, or did I miss something?

  Thank you.

  Container {
      id: rootContainer
      Label  {
          text: "Example Component Definition"
      }
      Button  {
          text: "Click to create dynamic component"
          onClicked :  {
              // Create the component and add it to the Container
              var createdControl = compDef.createObject();
              rootContainer.add(createdControl);
          }
      }
      attachedObjects: [
          ComponentDefinition {
              id: compDef
              source: "test.qml"
          }
      ]
  }
  

  OK, the right kind of data is 'variant', sorry, I searched for an hour, just found

• Populating drop-down list with SQL

  I have a database and I want to fill the drop-down list with a 'Group By' request to show the various categories without showing many of the same.  Here's the code I'm having difficult with:

  DropDown {
                  id: filterSelect
                  visible: true
                  enabled: {if (purchaseValue != false){false}}
                  bottomPadding: 20
                  title: qsTr("Category:") + Retranslate.onLanguageChanged
                  horizontalAlignment: HorizontalAlignment.Center
                  options: Option {
                      id: allOption
                      text: qsTr("All") + Retranslate.onLanguageChanged
                      selected: true
                  }
                  onSelectedOptionChanged: {
                      if(filterSelect.selectedOption == allOption){
                      _app.refreshObjects()
                      }
                      else{
                      dataSource.query = "select * from items where categoryfield LIKE '%"+ filterSelect.selectedOption.text+"%'"}
                  }
                  attachedObjects: [
                      ComponentDefinition {
                          id: optionFactory
                          Option {
  
                          }
                      }
                  ]
                  onCreationCompleted: {
  //                    "select categoryfield from items group by categoryfield"
                      var newOption = optionFactory.createObject()
                      newOption.text = 'Text to add' // or a variable fetched from data source
                      //newOption.otherfields = ...
                      filterSelect.add(newOption);
                  }
              }
  

  I have a data source that fills the listview, I want to use the same database to populate the drop-down list.  How should I go about this?  I tried to configure a different DataSource {} just for the dropdown menu, but I couldn't make it work.  In bold text, I am not clear as where I incorporate my SQL query against the newOption.text =

  TL; DR I try to use a SQL query to fill my menu drop-down using the same PB that is used for the listview.

  Any help will be appreciated and thanked!

  A friend by the name of Roger Leblanc http://appworld.blackberry.com/webstore/vendor/70290/?lang=en&countrycode=CA helped me and created a small code example to explain how it works.

  import bb.cascades 1.2
  import bb.data 1.0
  
  Page {
      Container {
          DropDown {
              id: dropdown
          }
          ListView {
              id: myListView
              dataModel: dataModel
              listItemComponents: [
                  ListItemComponent {
                      type: "item"
                      StandardListItem {
                          title: ListItemData.categoryfield
                      }
                  } // end of ListItemComponent
              ]
          } // end of ListView
      }
  
      attachedObjects: [
          GroupDataModel {
              id: dataModel
          },
          DataSource {
              id: dataSource
  
              // Load the data from an SQL database, based on a specific query
              source: "asset:///pinguin.db"
              query: "select categoryfield from items group by categoryfield"
  
              onDataLoaded: {
                  // After the data is loaded, insert it into the data model
                  // This will populate the ListView. You don't want to show
                  // categoryfield in ListView, I just wanted to show the difference
                  // between populating a ListView and a DropDown
                  dataModel.insertList(data);
  
                  // Now, this will populate the DropDown by iterating through every
                  // data from the query and adding it one by one to the DropDown
                  // using the optionFactory Component Definition to add dynamically
                  // new Options to the DropDown
                  for (var i = 0; i < data.length; ++i)
                  {
                      // Create new Option
                      var newOption = optionFactory.createObject()
  
                      // Set the Option text to categoryfield
                      newOption.text = data[i].categoryfield
  
                      // Add the Option to DropDown
                      dropdown.add(newOption);
                  }
              }
          },
          ComponentDefinition {
              id: optionFactory
              Option {}
          }
  // end of DataSource
      ]
  
      onCreationCompleted: {
          // After the root Page is created, direct the data source to start
          // loading data
          dataSource.load();
      }
  }
  

• Navigate from a to an other navigation pane navigation pane

  Hi all

  In the navigation pane, we can spread one component to the next.

  But what happens if I want to navigate from a navigation to another part of the navigation pane.

  for example: -.

  hand. QML: -.

   ActionItem {
                  title: qsTr ("ReadFromSD")
                  imageSource: "asset:///images/action_addcontact.png"
                  ActionBar.placement: ActionBarPlacement.OnBar
  
                  onTriggered: {
                      if (_addressBook.detectSD()) {
                          var page = secondPageDefinition.createObject();
                          navigationPane.push(page);
                      }
                  }
              }
  

  and the second page definition is like: -.

   ComponentDefinition {
              id: secondPageDefinition
              source: "filePicker.qml"
              Page {
                  Container {
  
                  }
                          paneProperties: NavigationPaneProperties {
                              backButton: ActionItem {
                                  title: "Back"
                                  onTriggered: {
                                      /*username.text = "";
                                      password.text = "";*/
                                      navigationPane.pop();
                                  }
                              }
                          }
                      }
          }
  

  The problem that is happening, is that the flow is not the trigger from one component to the other:

  NavigationPane {
      id: navigationPaneFilePicker
  
      onPopTransitionEnded: page.destroy()
  
      Page {
          titleBar: TitleBar {
              title: qsTr ("Select contacts File")
          }
  
          Container {
              layout: DockLayout {}
  
              // The background image
              ImageView {
                  horizontalAlignment: HorizontalAlignment.Fill
                  verticalAlignment: VerticalAlignment.Fill
  
                  imageSource: "asset:///images/background.png"
              }
              FilepickerScrollView {
  
                  Container {
                      horizontalAlignment: HorizontalAlignment.Fill
                      verticalAlignment: VerticalAlignment.Fill
  
  ................................................
  ...............................................
  

  When I click the first page its not sailing does not to the second. When the second does not have the navigation pane it worked correctly, but as soon as I added the tag in navigation pane to it it stopped working

  Please suggest

  The element root firstPage.qml and secondPage.qml doesn't have to be a NavigationPane but a page element. You already have a navigationPane in your hierarchy of context and as a result, you can refer to your main QML file NavigationPane directly.

  For example:

  hand. QML:

  include bb.cascades 1.3
  
  NavigationPane {
    id: root
    Container {
      Button {
        text: "Push the first pane"
        onClicked: {
      var first = firstPane.createObject();
      root.push(first);
        }
      }
    }
    attachedObjects: ComponentDefinition {
      id: firstPane
      source: "firstPage.qml"
    }
  }
  

  firstPage.qml

     include bb.cascades 1.3
  
      id: navigationPane
  
      // The initial page
      Page {
          content: Container {
              Button {
                  text: "Display First Page"
  
                  onClicked: {
                      var second= secondPage.createObject();
              // Use the navigationPane defined in main.qml
                      root.push(second); //pushes the defined component definition (first)
                  }
              }
          } // end of Container
  
        attachedObjects: [
          ComponentDefinition {
              id: secondPage
              source: "place the asset filepath to your secondPageQML here"
          }
      ] // end of attachedObjects list
     } // end of Page
  

• Read the dynamically created objects

  Hello

  I get my feet wet with development of Cascades, and I was hoping someone here could answer some questions I had.

  I am defining a container that contains a drop-down list and a zone of textfield and I need to repeat this containing three more times. I thought by using the ControlDelegate class to create three instances without writing the code three times. However, I don't know how I'd read the value of each instance of the drop-down list and the ControlDelegate textfield.

  Any Suggestions?

  If you instantiate the like this:

  Container {
      property variant control1
      property variant control2
      property variant control3
  
      id: rootContainer
      Label  {
          text: "Example Component Definition"
      }
      Button  {
          text: "Click to create dynamic component"
          onClicked :  {
              // Create the component and add it to the Container
              control1 = compDef.createObject();
              rootContainer.add(control1);
              control2 = compDef.createObject();
              rootContainer.add(control2);
              control3 = compDef.createObject();
              rootContainer.add(control3);
          }
      }
      attachedObjects: [
          ComponentDefinition {
              id: compDef
              textfield { id: text }
          }
      ]
  }
  

  Then components are accessible as control1.text, control2.text etc.

  If the number of objects is constant, then ControlDelegate might be more convenient.

  For ListView, you can use ArrayDataModel or GroupDataModel (for more complex models with sorting) and fill it with any type of data. Any kind of items can be added, it's just a picture of QVariantMaps. It is not necessarily Xml or SQL wrapper, but specialized models also exist for this. It is even possible to create a subclass of DataModel custom c++ to expose existing data objects.

• NavigationPane pushing a Page several times

  Not sure, which continues, but I have a navigationPane and in the ComponentDefinition, I have another qml page that gets thrust on the navigationPane when the signal of customDefined is called.

  Thus, as soon as the custom signal is triggered, it pushes page in the componentDefinition to the NavigationPane.

  So, now when I click on a listItem which finally triggers the signal customized in QML, he pushes the page very well, but if I come back and click again on the issue, he is now pushing 2 times and now I have to go back 2 times. the number keeps on incrementing at the same time, I click on the listItem.

  BTW, in the page defined in the component definition, it has properties pane that appears when the user clicks on the back of the battery.

  on newspapers, I see the page being skipped too.

  not sure what goes wrong, any help will be appreciated.

  Thank you

  S.

  Hello
  So, I found what the problem was.

  (1)   ListView *listV = root->findChild("listP");
      bool success = QObject::connect(this, SIGNAL(goodForPushPToTest1()), listV, SIGNAL(goodForPush()) );
      emit goodForPushToTest1(); // so, QT signal connected to signal in QML
  

  (1) is the line that caused the problem. the reason being that I create a new object each time and then pushing him to the navPane.

  make sense?

• QML question setting of dynamic components

  I am wanting to adjust objects in a component definition in my main qml.

  hand. QML

  Page {
     id: mainPage
     Container {
         id: root
  
     //Container in separate page
     SomeCustomControl {
         id: someCustomControl
     }
  
     }
  
    onCreationCompleted: {        //I attempt to change them but nothing is recognized past customDef        someCustomControl.customDef.changeContainer.background = Color.Blue  }
  
  }
  

  someCustomControl.qml

  Container {
      id: root
  
      property variant attachedDef    property alias customDef: myDef
  
      Container {
         id: body
      }
  
      attachedObjects: [
          ComponentDefinition {
              id: myDef
              source: "myDef.qml"
          }
      ]
  
     onCreationCompleted: {
        if (!root.attachedDef){
          root.attachedDef= myDef.createObject();
        }
        body.add(root.attachedDef);
  }
  
  }
  

  myDef.qml

  Container {
      id: root
      property alias ccback: changeContainer.background    //Goal is to change the background color
      //From main.qml
      Container {
          id: changeContainer
          preferredWidth: 100
          preferredHeight: 100
          background: Color.Green
      }
  
  }
  

  I don't know how to access the components in the component definition to change

  I thought about it, instead of using the alias customDef, if I just use the Variant that he accepts the definition inside objects

  hand. QML

  onCreationCompleted: {   if (someCustomControl.attachedDef){      someCustomControl.attachedDef.ccback = Color.Blue   }
  }
  

  The other form of definition makes things a little crazy unless is just a really small item, I had just questions so that it connects, but then I played a little with this example, I wrote just out and turns out it was not as hard as I thought

• srvrmgr syntax: How can I create subsystem named with the name and Description of the values?

  Looking through the library, he did discuss are of syntax that allows you to include the value of name and the named value of the Description of a subsystem/Profile Configuration.  In the screenshot, the circled values were created with the server online order Manager.

  

  On the other hand, pouvez create a definition of the element with a name (full name) and a Description.

  For CompDef, it works:
  create the CompDefTest1_enu component definition for the type of component AppObjMgr component fins group run mode interactive full name 'Test Comp Def Test 1' description 'Test 1 CompDef Manager object.

  For named Subsytem, it does NOT work:
  create named subsystem Test5 subsystem EAITransportDataHandlingSubsys full name 'Test 5' description 'Test 5 Description'

  Someone can tell me if there is a good for a named subsystem, syntax to include the name and Description of the values in the command line, or is the only way to create it manually in the UI?

  Hello

  I spent reviewing aid to create the order in srvrmgr, it does not give the full name and description as parameters for the creation of subsystem. However, as you noted these settings are available for creating components definition:

  srvrmgr > help to create

  Create {component group | compgrp}

  [full name: ]

  [{description | desc} ]

  create {definition component: compdef}

  for {component type | comptype}

  {Component group | compgrp}

  run in mode {batch | interactive | background}

  [full name: ]

  [{description | desc} ]

  [with [ param =[, =...]]]

  [[fixparam =[,...]]]

  create the subsystem named for

  subsystem with = [,...]

  Shelf also has an example of creation of subsystem that doesn't include no description, name and first name:

  http://docs.Oracle.com/CD/E14004_01/books/StoreFwdMsg/StoreFwdMsg_InstallConfig14.html#wp1351472

  In this case I suggest that allows you to create a ticket on My Oracle Support to confirm this srvrmgr does not support the creation of a new subsystem with the full name and description settings and request an enhancement for these settings include request in create statement for new subsystems when using srvrmgr.

  It will be useful,

  WSiebel