Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • linuxmce linuxmce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 255
    • Issues 255
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linuxmcelinuxmce
  • linuxmcelinuxmce
  • Issues
  • #1230
Closed
Open
Issue created Sep 12, 2011 by Langston Ball@golgoj4Maintainer

New DCE functions for 'dynamic' orbiter generation

The purpose of this ticket is to catalog the data that qOrbiter (or any new type of orbiter for that matter) would require to run. This would encompass lists of data like rooms, scenarios, etc that is normally encapsulated in the orbitergeneration process.

off the top of my head *Room_Users *Room_Ea *scenarios for the different categories *Users *default data like default room, user

Assignee
Assign to
Time tracking