Article last updated on the 4th of March 2022.
Contents
1. Introduction
The Multiple Stage Model per Business Module feature allows you to define multiple stage models for your business modules and utilize them in various ways.
An example of the use of multiple stage models could be using different stage models for different project types on a project management solution, or using different stage models based on project size.
2. Requirements
The Multiple Stage Models per Business Module feature is available with the WorkPoint Enterprise license plan.
3. Configuration
For general information about creating stages, transitions, and constraints, please visit this article.
3.1. Accessing stage settings
Setting up multiple stage models can be done from the WorkPoint Administration, which can be accessed in the following way.
- On the WorkPoint solution, click the "Home" button in the top left of the page to open the left side menu.
- In the bottom of the left side menu, click the cog to access the WorkPoint Administration.
- Click the header of the business module for which you wish to configure stage settings.
- In the drop down menu, click "Stage Settings".
This opens the stage settings page:
3.2. Creating multiple stage models
The following section describes how to set up multiple stage models for the "Projects" business module on a Project Management solution.
The section presupposes that Staging has been enabled for the module in the Stage Settings page, and has the following settings configured:
- The default stage change wizard is set to the "Change stage and edit entity"-wizard.
- The stage rendering mode is set to "Full". For more information about this setting, please visit this article.
- The "Mapping Field" is set to a field on the business module list called "Project Type". In this example that field is a managed metadata field which refers to the following term set on the tenant of the solution:
Note that the mapping field is an existing field on the business module in question. If no appropriate field can be found for this setting, you will have to create one for this purpose. Only Managed Metadata fields are supported as Mapping fields.
Note that for the Managed Metadata field, the term set that the field is linked with must be tenant scoped.
Note also that this field, once selected for this purpose, is set as Read-Only, meaning it can only be edited through a WorkPoint Wizard.
The Mapping Field is the field used for determining which stage model to use for a specific entity on the business module. With this setup, we can e.g. create three different stage models - one for each type of project. When creating a project and setting the project type, the associated stage model is then used for that project.
- "Allow Stage Model Transition" is set to "Yes". Setting this to "No" will disallow switching stage models for an entity when changing stage. Setting this to "Yes" allows this process to be carried out. A case where this could be useful is if a small project evolves into a large project, and therefore requires a different stage model. Instead of creating a new project, you could simply switch and use a stage model appropriate for large projects.
Note that when switching to another stage model, you rewind to the initial stage of the new stage model.
Further, in this section, the following stages have been set up beforehand:
We have also set up a stage model for the "Implementation" project type:
Next, we will set up a stage model for the "Maintenance" project type:
- In the "Stage Models" section of the page, click "Add Stage Model".
- We grant the new stage model the name "Maintenance Stage Model". When naming your stage models, it is a good idea to name them in a way which makes the intended usage of the stage model clear.
- We keep the "Is Default" checker off, as we already have a default stage model.
- For the Mapping Field Value, we click the term set icon to select a term to use as project type.
- In the "Select: Project Type" window, double-click the term you wish to use. In this case, we double-click "Maintenance" as this stage model is going to relate to this project type.
- Click the "OK" button to confirm the selection.
- When all setting are set, click the "Save" button to save the stage model.
We can now start adding stages, transitions, and constraints to the stage model:
- In the "Edit Stage Model" page, we can add stages defined in the "Stage Settings" page to the stage model. To do this, click "Set Existing Stages".
- In the "Existing Stages" window, we can check the existing stages to set which ones we want to be usable in the stage model we are configuring. In this case, we select the four shown stages. This means that for this stage model (the Maintenance stage model), only these four stages will be usable.
- To save the stage selection, click the "Save" button. The stages are now saved and shows up in the "Edit Stage Model" page:
We can now set up transitions between the stages in the stage model. In this example, we will create a simple progression from the Analysis stage through Active, Closed, and eventually ending in the Archived stage:
- In the "Transitions" section of the Edit Stage Model page, click "Add transition".
- For the first transition, we will select the "Analysis" stage as "From stage".
- As "To stage", we will select the "Active" stage.
- To save the transition, click the "Save" button.
We will repeat this process, adding the other transitions until we have the following transitions:
We can now also set up a constraint. In this example, we will add a constraint which throws a warning to the user if they attempts to transition into the Active stage if there is no document in the Project's Documents library called "Analysis":
- In the "Edit Stage Model" page, in the "Constraints" section, click "Add constraint" if you want to add a constraint. For detailed information on how to create constraints, please visit this article.
The model is now shown in the Stage Settings page:
- Click the "Edit" button to edit the stage model.
- Click the "Delete" button to delete the stage model. Note that you cannot delete the default stage model unless another stage model exists. You would need to create a new stage model, set that one to default, and then delete the previous default model. In the case from the image above, if the "Implementation Stage Model" is deleted, the "Maintenance Stage Model" would become the new default stage model, and the "Implementation Stage Model" would be deleted.
4. End User Guide
For an End User Guide for Multiple Stage Models, please visit this article.
Comments
0 comments
Please sign in to leave a comment.