Efficy Overflow Q&A - Recent questions and answers in migration

Answered: How does Efficy application choose what Oracle client should be used? (10.2 , 11.2 ?)

Tue, 09 Jul 2019 11:44:24 +0000

Hello Vladimir,

We have this issue for Eiffage, we had to installed Oracle Client version 64 bits on the serveur that already had the Oracle Client 32 bits.

To make both client working, we use the information of this internet Web Page :
Use 32 and 64bit Oracle Client in parallel on Windows 7 64-bit for e.g. .NET Apps

Hope this will help :)

Answered: Upgrade to Efficy 11 – Migration guide & Best practices

Thu, 10 Jan 2019 14:00:56 +0000

Hi Stoko

I shared you this internal document, you can access is for 30 days.

Regards,
Kristof

Answered: Efficy 11: Flexmail settings Upgrade from Efficy 2014 ?

Fri, 03 Aug 2018 09:10:15 +0000

Hi Stéphane,

The script has been removed since the new acc_auth mechanism does not allow what was done here. The password and the token are now encrypted directly by Efficy and this kind of manipulation can not be done in serverscript.

To upgrade from Efficy 2014 to Efficy 11, I suggest to do the following step only once:

Create in Conficy the flexmail user depending of information stored in sys_storage
Edit the everyone group and select the new flexmail user.
Copy the FLEXMAIL.K_FLEXMAIL of this new user.

Execute the function upgradeFrom6640To11 of the following upgrade script directly with a task scheduler (the kFlexmail needs to be replaced with the K_FLEXMAIL of the FLEXMAIL table):

/* upgradeFrom6640To11: Upgrade from Efficy 2014 (<= 6640) to Efficy 11 (or newer):
Initialize:
    field PUBL$EMAILING.K_FLEXMAIL
    field PROF_FLEXMAIL.FLEXGROUP_ID

upgradeFrom7987To11: Upgrade from Efficy 10 (v.7987) to Efficy 11 (newer):
Initialize:
    table PROF_FLEXMAIL (from PROF_FLEXPROFILE) 
*/

var EFFICY_PUBL_CATEGORY_NAME = 'PUBL$EMAILING';

function upgradeFrom6640To11() {
    var
        sql, ds, sqlContext, editHandle, categDs,
        kFlexmail;

    kFlexmail = 2;
    Database.Log('   [upgrade from Efficy 2014 (v.6640) to Efficy 11]');
    try {
        Database.DisableSecurity = true;
        Database.Log('--Linking Publications (PUBL$EMAILING) to Flexmail account...');
        sql = 'select K_PUBLICATION from <#TABLE name=PUBL$EMAILING> where CAMPAIGN_ID is not null';
        sqlContext = Database.OpenTemporaryContext;
        ds = Database.ExecuteSystemSQLQuery(0, sqlContext, sql, '', true, true, 0);
        if (!ds)
            throw new Error ('----Error while fetching records from table PUBL$EMAILING');
        if (!ds.IsEmpty) {
            ds.First;
            while (!ds.Eof) {
                editHandle = Database.OpenEditContext(ntPubl, ds.FieldByName('K_PUBLICATION').AsFloat);
                try {
                    Database.ActivateCategory(editHandle, EFFICY_PUBL_CATEGORY_NAME);
                    categDs = Database.GetCategoryDataSet(editHandle, EFFICY_PUBL_CATEGORY_NAME);
                    if (!categDs.IsEmpty) {
                        categDs.Edit;
                        categDs.FieldByName('K_FLEXMAIL').AsFloat = kFlexmail;
                        categDs.Post;
                        Database.CommitChanges(editHandle, false);
                    }
                }
                finally {
                    Database.CloseContext(editHandle);
                }
                ds.Next;
            }
        }

        Database.Log('--Linking Profiles (PROF$EMAILING) to Flexmail account...');
        sql = 'select pe.FLEXGROUPID, pe.K_PROFILE from <#TABLE NAME=PROF$EMAILING> pe where FLEXGROUPID is not null';
        ds = Database.ExecuteSystemSQLQuery(0, sqlContext, sql, '', true, true, 0);
        if (!ds)
            throw new Error ('----Error while fetching records from table PROF$EMAILING');
        if (!ds.IsEmpty) {
            ds.First;
            while (!ds.Eof) {
                try {
                    updateEfficyProfile(ds.FieldByName('K_PROFILE').AsFloat, kFlexmail, ds.FieldByName('FLEXGROUPID').AsString);
                }
                catch(ex) {
                    Database.Log('----Error while linking Profile to Flexmail account: K_PROFILE = ' + ds.FieldByName('K_PROFILE').AsString);
                }
                ds.Next;
            }
        }

    }
    finally {
        Database.DisableSecurity = false;
    }
}

function upgradeFrom7987To11() {
    var
        sql, ds, sqlContext;

    Database.Log('Migrating data from PROF_FLEXPROFILE to PROF_FLEXMAIL');
    Database.Log('   [upgrade from Efficy 10 (v.7987) to Efficy 11]');
    sql = 'select K_FLEXMAIL, K_PROFILE, FLEXGROUP_ID from <#TABLE NAME=PROF_FLEXPROFILE>';
    try {
        sqlContext = Database.OpenTemporaryContext;
        ds = Database.ExecuteSystemSQLQuery(0, sqlContext, sql, '', true, true, 0);
        if (ds) {
            if (!ds.IsEmpty) {
                ds.First;
                while (!ds.Eof) {
                    try {
                        updateEfficyProfile(ds.FieldByName('K_PROFILE').AsFloat, ds.FieldByName('K_FLEXMAIL').AsFloat, ds.FieldByName('FLEXGROUP_ID').AsString);
                    }
                    catch(ex) {
                        Database.Log('--Impossible to migrate a record of PROF_FLEXPROFILE: K_PROFILE = ' + ds.FieldByName('K_PROFILE').AsString + ', K_FLEXMAIL = ' + ds.FieldByName('K_FLEXMAIL').AsString);
                        Database.Log('  (record probably already exists)');
                    }
                    ds.Next;
                }
            }
        }
        else
            Database.Log('--No records PROF_FLEXPROFILE found => Nothing to be done');
    }
    catch(ex) {
        Database.Log('--No records PROF_FLEXPROFILE found => Nothing to be done');
    }
}

// Fill flex group ID in Efficy profiles
function updateEfficyProfile(kProfile, kFlexmail, flexGroupId) {
    var editHandle = 0;
    if (kProfile) {
        editHandle = Database.OpenEditContextRelation2(ntProf, ntFlexmail, kProfile, kFlexmail);
        try {
            Database.UpdateStringField(editHandle, 0, 'FLEXGROUP_ID', flexGroupId);
            Database.CommitChanges(editHandle, false);
        }
        finally {
            Database.CloseContext(editHandle);
        }
    }
}

If you have to upgrade from Efficy 10 r7987 to a newer version, execute the upgradeFrom7987To11 function to transfer information from PROF_FLEXPROFILE to PROF_FLEXMAIL.

We will no longer do this kind of upgrade function as it can not be easily maintained. In the future, the UpgradeDB will always be used for this kind of manipulation. For example, to migrate from Efficy 10 to Efficy 11, the upgradeDB is taking care of the migration of the table FLEXMAIL to the table ACC_AUTH and also migrates the field PROF$EMAILING.FLEXGROUP to FLEXKIND.

Kind regards,

Answered: DialogHeader has disapear on Efficy 10th SP2

Mon, 23 Jan 2017 10:19:32 +0000

This is not a bug.
This macro has disappeared in favor of two new macros in MacroDialog.txt :

DialogScripts
DialogScriptsRequire

Please note that the <%UseStyleSheet()%> is no longer present in those macros, and should manually added if needed, and the correct syntax in Efficy 10 is :
<%UseStyleSheet(page='%%OnLanguage(ar="efficy-rtl", else="efficy")')%>

efficy\pages\dialog\Category.htm is a good example of the good practices on the usage of those macros.

Answered: Delphi Server Scripts not supported anymore since Efficy10SP1

Tue, 17 Jan 2017 08:58:22 +0000

Hello Pierre,

Indeed, only JavaScript is supported in Serverscripts, Scheduled scripts and DataSynchro since Efficy 10 SP1.

Answered: Upgrade to Efficy 10 – Migration guide & Best practices

Tue, 14 Jun 2016 13:02:15 +0000

From Efficy 2014 to Efficy 10

A/ What to be checked

Of course, all custom must be tested, but, the “general” structure of the files, the macros, the Js and the Css, is the same. However, there is some file you will always need to adapt if you are coming from an Efficy 2014 to an Efficy 10.

This list is not exhaustive:

1.Js files

In some file, the « define ([…] » as changed (some Js files are new, and some Js file have been moved). Also, base/, utils/, … are not necessary anymore. So, you need to verify the define of all your custom files in Js folder.

The best way, is to replace the define in your custom, by the define copied from the standard file, and add your custom define if needed. (easy to do with a tools like beyond compare)

2. Css/Scss files

If you have a custom efficy.css generated by a custom scss, you need to adapt the “_custom-settings.scss” file, because Efficy 10 comes with Badges and Chronos (TimeLine) who have some Css configuration.

The best way to upgrade this file, is to write a new one, who is a copy of the standard “app-settings.scss” and reintegrate your custom in this new file (keep the same name for the new file “custom-settings.scss” there is no reason to change it), and recompile your efficy.css.

3. Macro files

With coming of TimeLine, we have a new tab, so, in each macro who display or use multiple entities like “DetailSelectTabs” or “DetailTabsButtons” for example, you need to compare with the standard file, and add the timeline if needed.

Badges are also new, so, some macro like “DetailTabs” must be checked to integrate new standard badges if you have customized these macros.

4.Htm files

It’s difficult to point something, each file where you have a custom must be opened in Efficy, to see if your custom is always working good, if not, compare with the standard file.