Migration from eBiss 2 to eBiss 3

An upgrade from eBiss 2 to eBiss 3 is simply possible via eBiss.Configurator.exe. This already works with eBiss 2 version 2.18.189. If you have an eBiss 2 version 2.18.189 from 12.6.2014 (DB Schema 2.18.73) or older, just start the eBiss.Configurator.exe, which updates the eBiss database and then you can on this server to start the service and the client.

Note: Make sure that custom plugins work as usual in the new environment.

As long as the custom plugin only uses the eBiss.Api there are no problems.

Tasks created by eBiss 2 may not appear in the message preview and message under certain circumstances. For example, if the task is assigned to a document. To resolve the problem, the following script can be executed on the SQL Server.

INSERT INTO Message_Task
SELECT DISTINCT d.Message_oid, t.Oid FROM Task t 
JOIN Task_ObjectReference tor ON t.Oid = tor.Task_oid
JOIN ObjectReference oref ON oref.Oid = tor.ObjectReference_oid AND  oref.TypeName = 'eBiss.Data.Document'
JOIN Document d ON d.Oid = oref.RefOid
WHERE t.Oid NOT IN (SELECT Task_oid FROM Message_Task)

Note: Flag type variables are of type boolean in eBiss3 and the Get functions effectively return boolean True or False. If migrated variables are not redefined in eBiss3 they keep the old properties when evaluating the Get function and return string values “True” or “False” or Null¹⁾.