Relatics has released the new feature “Synchronization” to help functional designers manage modifications within multiple project workspaces centrally and more efficiently.
Flexibility and scalability
Relatics is known for its decentralized architecture. Instead of having one central information structure and user interface, projects have their own workspace in which everything can be tailored to the specific project needs. This flexibility guarantees a perfect fit between Relatics and the unique project characteristics.
A potential drawback of this architecture is the effort required to maintain those individual projects. If new insights or features need to be implemented, functional designers need to apply these changes to each project workspace. As the number of projects increases, scalability might become an issue.
With Synchronization, changes to multiple projects can be applied almost effortlessly and without sacrificing any of the flexibility. New reports, building blocks or information structures can automatically be added to existing projects. Even if those projects have their own project-specific changes.
This means having the best of both worlds.
With Synchronization, a (standard) workspace can now be transformed into a Relatics template. This Relatics template is a frozen copy of the standard workspace. If a new version of the workspace arises, another template can be made that includes the new features.
In the environment portal, a new "Templates" table is visible for users that have been assigned the role of "Template creator". This table shows the templates, selectability and the number of attached workspaces. A new template is created after selecting a standard workspace on which to base the template on.
Creating new workspaces based on a template is very straightforward. The context menu in the environment portal is enriched with a new menu item, "Create from template". This menu lists all the available templates that can be used to create a new workspace.
It is also possible to attach existing workspaces, which were originally created by copying a standard workspace, to a template. This means that today’s running projects can profit from this feature as well.
End users will not notice any difference in workspaces attached to a template. Functional designers can still modify workspaces, even if they are attached to a template. Project-specific relations, properties and building blocks can be added, while building blocks obtained from the template can be extended with extra columns. Future template updates will always be possible.
Functional designers are informed whether the information structure or building block are obtained from the template (shown in green) or are created locally. Items obtained from the template cannot be modified or deleted but can be extended easily.
In addition, projects that require extreme modifications (for instance changes to the information structure) can be detached from the template and can continue to operate as a standalone project workspace.
Template owners can update project workspaces attached to these templates. On the detail page of a template, project workspaces can be selected for updating.
Relatics will validate each workspace to ensure no conflicts arise when the new template is attached to the project workspace. Updates will never result in data loss or modifications. Once the update has been completed successfully, the selected workspaces are attached to the new template.
"Synchronization" has been designed with minimal constraints. There are no requirements for template versioning or migration policies at all. It is up to the template owner to determine which projects need to be updated and when. The introduction of “Synchronization” guarantees a perfect fit between Relatics and the unique project characteristics, while remaining perfectly scalable. As said: it’s the best of both worlds.
Released on April 4, 2017.