Although the 2022.2 version of the Thinkwise Platform has only just been released, we already have big plans for a major change for the 2023.1. We are planning to store only the latest version of every project and move all old data to history tables.The main goal of this change is performance improvement by separating the operational data in the Software Factory from the non-operational data. A secondary goal is preventing massive amounts of unnecessary data from being stored.In the 2022.2 and earlier versions of the Software Factory the version control was handled by making a copy of a complete model in the shape of a project version. This resulted in largely the same data being saved multiple numbers of times, whenever a new project version or branch was created. Since the changes only make up a small percentage of the whole model, this unnecessary data caused the Software Factory databases to grow over time and becoming slower due to their size.The change that is intended is to star
Some clients use different webpages for different situations, for example situations where there's a separate page for a specific symposium in a specific year and another page for the same event but a year later. In these situations it would be very beneficial if they could set up the look and feel of that page in one Indicium i.e. determining the background of the page dynamically based on the source of the request.In the current situation it is possible to do this by setting up multiple Indiciums (Indicia?) next to eachother and editing the logo.jpg and background.jpg files with the specific images for the specific situation and editing the styles.css file to use that specific logo and/or background image.However, this results in the client having to manage multiple instances of Indicium, which is not the preferred situation.Perhaps this also relates to the idea posted by Jaap van Beusekom (linked below), but I'm not 100% sure if that is the case. If so, feel free to link the two ide
From a back-office perspective it can be beneficial to see records on a tile, instead of in a grid or a form type of display. This ensures that a combination of data can be more accessible, without first having to click on specific details. Currently we only have the option to show a table, task, report or detail tab as a tile, but in this case, it would be preferable to also have the option to show records in a table or view as tiles in the GUI.For example: a production company can currently view their employee planning either from the perspective of a specific employee, or a specific project. They would like to have one screen, with a tile for every employee, that immediately shows the project they’re planned on and any possible existing comments/notes. This will provide them with a clear overview of the current status/situation of who is present and scheduled to do which project.This idea can however be applied to a variety of different situations.
Within our project we have encountered the problem that key-users in the analysis process do not always know what the key components of a process diagram mean. This is why we have created our own legend (see appendix, sorry that it's in Dutch) in the form of an user requirement in the SF, that contains a 'diagram' with all the key components that we use in our process diagram. Perhaps it would be nice if there would be one generic legend, in both Dutch and English, that explains all the key-components used in process diagrams within the SF, that can be used in every single project in communication with key-users who have to review the requirements and their corresponding process diagrams.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
