Frequently Asked Questions - Version Change and Servers

Objective

This page outlines popular questions and answers related to version changes.

 

Tests

  1. Do actions completed in version 3.05 during testing have an effect on the current production environment?

No. You are using a test server that is independent from your production server. For your GoLive, a new copy of your data is used for the final conversion to 3.05 in production.

  1. Does the link to use mobility change when moving into production in version 3.05?

Sometimes yes, our teams will guide you through this process.

  1. Do I need to test new functionalities or icons in 3.05?

No. The tests boil down to "if you use it in 3.04, then you should test it in 3.05". You can test what's new in 3.05 on your test server, however, it is strongly recommended that you do this only after you have completed your version change tests. There are several reasons for this recommendation, but first and foremost to make sure you don't run out of time and thus avoid having to postpone your GoLive. Especially since, once live in 3.05, you will have plenty of time to test new features in a test company without affecting the operations in progress.

 

Terminology

Maestro* Versions

  • PSQL: Refers to Pervasive technology. For example, to date, Maestro offers a version 3.04 PSQL and a version 3.05 PSQL.
  • Refers to SQL technology. For example, to date, Maestro offers version 3.05 MS SQL.

Version Change

  • Refers to any difference in behavior between two versions of the same technology. For example, a difference in behavior between maestro* 3.04, which uses Pervasive technology, and maestro* 3.05 PSQL, which also uses Pervasive, is due to the version change.
  • An expression used to designate your project to switch from maestro* in version 3.04 to maestro* in version 3.05 PSQL since these versions use the same technology. This term is currently confused with the term "Migration" so it is also used to refer to migration projects to 3.05 MS SQL.
  • At the technical level, if you upgrade to maestro* 3.05 PSQL, we are talking about converting your data from maestro* 3.04.

Migration

  • Refers to any difference in behavior between two versions that do not use the same technology. For example, a difference in behavior between maestro* 3.04 or 3.05 PSQL, which uses Pervasive technology, and maestro* 3.05 MS SQL, which uses SQL technology, is due to migration.
  • Expression used to designate your project to switch from maestro* 3.04 or maestro* 3.05 PSQL to maestro* 3.05 MS SQL since these versions do not use the same technology. This expression is currently confused with the expression "Version change" so it is also used to refer to the 3.05 PSQL migration projects.
  • At the technical level, if you upgrade to maestro* 3.05 MS SQL, there is also a step to convert your data from maestro* 3.04 to maestro* 3.05 PSQL, but the final step is to migrate your data to maestro* 3.05 MS SQL. To simplify the language and make a distinction, we are talking about migration here.

 

Server Details

  • MS SQL: An MS SQL server is required when a client is converting to version 3.05 MS SQL.
  • Regardless of whether it is MS SQL or PSQL, a separate server is required for testing purposes.

 

Differences between 3.05 PSQL and MS SQL

  • MS SQL: Purchase new Microsoft database (not supplied by maestro*, additional cost above the migration).
  • Certain features available in MS SQL only (maestro*BI, Service call and Work order quotes, etc.).

 

Questions about maestro*CLOUD (MS SQL)

  • Includes all standard steps for conversion and is considered a hosted solution, not a local or web solution.
    • Maestro* can also be used via alternate hosted solutions, as desired.
  • Database conversion required (including Professional Services time).
  • Office365 licences required.

 

Last modification: September 19, 2024