| Next revision | Previous revision |
| 75:newprocesses [2020/12/01 08:33] – created aakr | 75:newprocesses [2024/02/15 00:00] (current) – external edit 127.0.0.1 |
|---|
| ====== Getting started in a new workspace ====== | ====== Getting started in a new workspace ====== |
| |
| In Stages, any process resides in a workspace. Once a workspace has been created, process can be populated in this workspace by four different mechanisms. | Once a workspace has been created, there is a welcome screen which provides four different mechanisms to get started. |
| |
| 1. Start with an Empty Process: To create a process from scratch, this option can be used. | [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=ac6367&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/welcomeprocess_1.png|{{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/welcomeprocess_1.png?direct&900x361 }}]] |
| |
| 2. Add Modules: This is one of the often used methods to integrate mutiple modules into single workspace. Refer process architecture for detailed explanation. Add module can also be used to instantiate standard process into projects. | **1. Start with an Empty Process: **To build a process from scratch, use this option. It loads the default [[:general:metamodel|m]][[:general:metamodel|etamodel]] (''Unified Configuration'') to begin the modeling. |
| |
| 3. Copy a Process: If two processes are very similar, it might be useful and efficent to simply bring the entire module by copying into over into the new workspaces and making any changes in the target workspace. | **2. Add Modules: **This is one of the often used methods to integrate mutiple modules into single workspace. Refer [[:73:process_architecture|process architecture]] for detailed explanation. ''Add module'' can also be used to instantiate standard process into projects. |
| |
| 4. Import a Process: This allows to import the process from a zip file. Typically it is used to bring a process that possibly has been created in an instance of Stages which is on a separate server or cloud. A process zip file is exported from source process and brought into target workspaces and uploaded using Import a Process option. | **3. [[:75:copyprocess|]]: **If two processes are very similar, it might be useful and efficent to simply bring the entire module by copying into over into the new workspaces and making any changes in the target workspace. |
| | |
| | **4. [[:75:import-processes|]]: **This allows to import the process from a zip file. Typically it is used to bring a process that possibly has been created in an instance of Stages which is on a separate server or cloud. A process zip file is exported from source process and brought into target workspaces and uploaded using ''Import a Process'' option. |
| |
| |