<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Efficy Overflow Q&amp;A - Recent questions and answers</title>
<link>https://overflow.efficy.io/?qa=qa</link>
<description>Powered by Question2Answer</description>
<item>
<title>E-deal / Efficy Corporate — New Extranet Offering (v2.0.1)</title>
<link>https://overflow.efficy.io/?qa=7253/e-deal-efficy-corporate-new-extranet-offering-v2-0-1</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new version of the E-deal Extranet is available:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal Extranet v2&lt;/strong&gt; - Version &lt;strong&gt;2.0.1&lt;/strong&gt;:&lt;br&gt;
-- Documentation : &lt;a rel=&quot;nofollow&quot; href=&quot;https://helpcenter.efficy.io/articles/?readerUiPreview=1#!e-deal/extrv2_introduction&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-extranet/2.0.1/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the build, use your login / password from our external repository.&lt;/p&gt;

&lt;p&gt;Extranet v2 is a standalone offering: refer to the introduction chapter of the online documentation for the scope, prerequisites and installation procedure.&lt;/p&gt;

&lt;p&gt;If you have any questions, please contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7253/e-deal-efficy-corporate-new-extranet-offering-v2-0-1</guid>
<pubDate>Fri, 24 Jul 2026 19:42:39 +0000</pubDate>
</item>
<item>
<title>Answered: SYS_FIELDS : DataType, EditStyle and Usage and do they influence the FullSearch Method?</title>
<link>https://overflow.efficy.io/?qa=2893/sysfields-datatype-editstyle-influence-fullsearch-method&amp;show=7252#a7252</link>
<description>&lt;h4&gt;DATATYPE — physical data type&lt;/h4&gt;

&lt;pre&gt;&lt;code&gt;A = Alphanumeric (string)
V = Alphanumeric variant (Oracle varchar2, used for the TEXTSEARCH feature)
B = Blob (binary) - NOT boolean
H = Character (single char)
C = Currency
D = Date
T = DateTime
I = Integer
G = Int64 (large integer)
L = Logical (boolean, stored as a string char) - NOT &quot;lookup by key&quot;
M = Memo text
N = Numeric (float)
S = SmallInt (marked &quot;not used&quot; in the source)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;So two corrections to your list: &lt;code&gt;L&lt;/code&gt; is &lt;strong&gt;Logical&lt;/strong&gt; (boolean), and &lt;code&gt;B&lt;/code&gt; is &lt;strong&gt;Blob&lt;/strong&gt;, not boolean.&lt;/p&gt;

&lt;h4&gt;USAGE — how the field gets its value&lt;/h4&gt;

&lt;pre&gt;&lt;code&gt;' ' = Normal stored field
K = Primary key of the table
C = Calculated - client-side calculation, rule in RULETEXT
L = Lookup - the field stores the VALUE itself, constrained by a lookup table
R = Lookup by reference - the field stores the KEY of a record in the
    lookup table (displayed and searched through the looked-up value)
E = Encrypted - stored encrypted (E_ column), decrypted via stored procedure
P = Procedure - value produced by an SQL function/procedure call
Q = Inline procedure
S = Inline SQL
V = Virtual
M = Main-detail (newer versions only)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;&lt;code&gt;P&lt;/code&gt;, &lt;code&gt;Q&lt;/code&gt;, &lt;code&gt;S&lt;/code&gt; and &lt;code&gt;V&lt;/code&gt; together form the &quot;logical fields&quot;: they have no physical storage of their own and are computed at query time.&lt;/p&gt;

&lt;h4&gt;EDITSTYLE — how the field is rendered/edited in the UI&lt;/h4&gt;

&lt;pre&gt;&lt;code&gt;A = Label (static text)
C = Checkbox - NOT currency
E = Edit box
W = Edit box for URLs
F = Rich edit (HTML)
G = Group box
L = Lookup allowing free values
K = Lookup list WITHOUT free values (closed list)
J = Lookup with search drop-down
R = Lookup rendered as a radio group
U = Multi-value lookup
V = Multi-value lookup with search
M = Memo
N = JSON memo (settings), shown as a dialog button
P = Picture blob with file upload
S = Picture blob with signature pad
&lt;/code&gt;&lt;/pre&gt;

&lt;h4&gt;Forbidden/enforced combinations&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;Multi-value edit styles (&lt;code&gt;U&lt;/code&gt;, &lt;code&gt;V&lt;/code&gt;): the server &lt;strong&gt;forces USAGE to blank&lt;/strong&gt; when loading the field cache — a multi-value field cannot be &lt;code&gt;USAGE = R&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Calculated fields (&lt;code&gt;USAGE = C&lt;/code&gt;): the edit style is expected to be &lt;code&gt;E&lt;/code&gt; or &lt;code&gt;C&lt;/code&gt;, and the data type must be one of &lt;code&gt;A V C I L N S G&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Single/multi-value lookup edit styles (&lt;code&gt;L K J R U V&lt;/code&gt;): the data type must be one of &lt;code&gt;A V C D T I N S&lt;/code&gt; (no memo, no blob).&lt;/li&gt;
&lt;li&gt;&lt;code&gt;A&lt;/code&gt; (label) and &lt;code&gt;G&lt;/code&gt; (group box) are pure layout elements: they are excluded from searches.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;Does EDITSTYLE influence the Full Search? No — USAGE does.&lt;/h4&gt;

&lt;p&gt;The full search builds its field list like this: a field is included when its USAGE is not a logical field (&lt;code&gt;P Q S V&lt;/code&gt;), its EDITSTYLE is not &lt;code&gt;A&lt;/code&gt;/&lt;code&gt;G&lt;/code&gt;, &lt;strong&gt;and&lt;/strong&gt; (its DATATYPE is &lt;code&gt;A&lt;/code&gt; or &lt;code&gt;M&lt;/code&gt;, &lt;strong&gt;or its USAGE is &lt;code&gt;R&lt;/code&gt;&lt;/strong&gt;).&lt;/p&gt;

&lt;p&gt;So your two fields are not picked up because of &lt;code&gt;EDITSTYLE = K&lt;/code&gt;: they are picked up because of &lt;code&gt;USAGE = R&lt;/code&gt;, and that is by design. For a lookup-by-reference field, the engine does not search the integer key — it replaces the field with a correlated sub-select returning the lookup's &lt;strong&gt;display value&lt;/strong&gt;:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;(select VALUE from LOOKUPTABLE L where L.K_xxx = TABLE.FIELD)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;which is a string — that is why they are &quot;considered like string fields&quot; in the full search. Your standard &lt;code&gt;I&lt;/code&gt;/&lt;code&gt;R&lt;/code&gt;/&lt;code&gt;L&lt;/code&gt; fields go through exactly the same code path; K vs L makes no difference to the generated SQL.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The likely cause of your error&lt;/strong&gt;: when the lookup definition of the field cannot be resolved (unknown &lt;code&gt;K_LOOKUPTABLE&lt;/code&gt;/&lt;code&gt;K_LOOKUPFIELD&lt;/code&gt;), the engine falls back to the &lt;strong&gt;raw field name&lt;/strong&gt; — the integer column then ends up wrapped in string operators (&lt;code&gt;upper(...) like ...&lt;/code&gt;), which raises the SQL error. Check the &lt;code&gt;K_LOOKUPTABLE&lt;/code&gt; and &lt;code&gt;K_LOOKUPFIELD&lt;/code&gt; values of those two custom fields in SYS_FIELDS: they most probably point to a missing table/field, unlike the standard fields you compared with.&lt;/p&gt;
</description>
<category>Database</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=2893/sysfields-datatype-editstyle-influence-fullsearch-method&amp;show=7252#a7252</guid>
<pubDate>Thu, 16 Jul 2026 16:00:11 +0000</pubDate>
</item>
<item>
<title>Answered: Can anyone explain the SYS_ENTITIES columns secured - notify - favorite - sharingcontext - drive – dashboard?</title>
<link>https://overflow.efficy.io/?qa=6914/explain-sysentities-favorite-sharingcontext-dashboard&amp;show=7251#a7251</link>
<description>&lt;h4&gt;SECURED — security mode of the entity&lt;/h4&gt;

&lt;pre&gt;&lt;code&gt;(empty)/0 = not secured - no rights configuration, no record-level security
1 = Secured   - full record-level security: the entity's table is added to
                the secure-tables list (per-record SECURITY handling) and
                the entity appears in the rights configuration screens
2 = Rights    - the entity appears in the rights configuration screens
                (per-user/group access rights) but records are NOT
                individually secured
3 = Scripting - same as Rights, but the entity is flagged as accessible
                from scripting only
&lt;/code&gt;&lt;/pre&gt;

&lt;h4&gt;NOTIFY — enables the notification mechanism&lt;/h4&gt;

&lt;p&gt;A boolean (&lt;code&gt;T&lt;/code&gt;/&lt;code&gt;F&lt;/code&gt;). When set, the entity is included in the list of &quot;notification entities&quot;: users linked to a record of this entity can be notified of changes (the actual per-record notification flags are stored as an integer bitmask on the user relation records). When not set, no notify options are offered for this entity.&lt;/p&gt;

&lt;h4&gt;FAVORITE — enables the &quot;recent items&quot; tracking&lt;/h4&gt;

&lt;p&gt;A boolean (&lt;code&gt;T&lt;/code&gt;/&lt;code&gt;F&lt;/code&gt;). Despite its name, it drives the &lt;strong&gt;Recents&lt;/strong&gt; feature — the source code even carries the comment &quot;&lt;em&gt;Favorite was old name for recents&lt;/em&gt;&quot;. Entities flagged with FAVORITE are included in the list of entities whose consulted records are tracked in the user's recent-items list.&lt;/p&gt;

&lt;h4&gt;SHARINGCONTEXT — the entity's bit in the SHARING bitmask&lt;/h4&gt;

&lt;p&gt;Your guess is correct. It is an integer bit value (power of 2) identifying the entity in the sharing mechanism: entities with a non-zero SHARINGCONTEXT appear as a checkbox in the &quot;Sharing list&quot; of the user/group configuration, and the checkbox is checked when &lt;code&gt;SHARING and SHARINGCONTEXT &amp;lt;&amp;gt; 0&lt;/code&gt; — i.e. the stored SHARING integer is the OR-combination of the SHARINGCONTEXT values of all shared entities. An entity with &lt;code&gt;0&lt;/code&gt; simply doesn't participate in sharing.&lt;/p&gt;

&lt;h4&gt;DRIVE — enables Efficy Drive for the entity&lt;/h4&gt;

&lt;p&gt;A boolean (&lt;code&gt;T&lt;/code&gt;/&lt;code&gt;F&lt;/code&gt;). When set, the entity participates in the Efficy Drive integration (document/folder synchronization): the Drive module only processes entities flagged with DRIVE.&lt;/p&gt;

&lt;h4&gt;DASHBOARD — not used by the runtime&lt;/h4&gt;

&lt;p&gt;A boolean (&lt;code&gt;T&lt;/code&gt;/&lt;code&gt;F&lt;/code&gt;), initialized to false when records are created, but nothing in the current server runtime ever reads it — it is a legacy/reserved column. You can safely leave it at &lt;code&gt;0&lt;/code&gt;/&lt;code&gt;F&lt;/code&gt;.&lt;/p&gt;
</description>
<category>Database</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=6914/explain-sysentities-favorite-sharingcontext-dashboard&amp;show=7251#a7251</guid>
<pubDate>Thu, 16 Jul 2026 15:49:04 +0000</pubDate>
</item>
<item>
<title>Answered: Can anyone explain the SYS_TABLES table the possible values of columns kind - rgroup - ranking – code?</title>
<link>https://overflow.efficy.io/?qa=6915/anyone-explain-systables-possible-values-columns-ranking&amp;show=7250#a7250</link>
<description>&lt;h4&gt;KIND — the table type&lt;/h4&gt;

&lt;pre&gt;&lt;code&gt;S = System table (SYS_*) - metadata, never CRM data
E = Entity - main entity tables (COMPANIES, CONTACTS, PROJECTS...)
R = Relation - many-to-many link table between two entities
L = Look-up table
B = Files - binary/blob storage tables
A = Account entity - the ACCOUNTS (users) table, handled separately
    for security and replication
N = Local entity - only included in the entity-table list when
    explicitly requested
C = Category - 1-1 extension table of an entity
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The set [E, R, B, A, C] is what the server considers &quot;normal tables&quot; (tables holding actual data).&lt;/p&gt;

&lt;h4&gt;RGROUP — replication select group (0 to 3)&lt;/h4&gt;

&lt;p&gt;A replicated (offline/satellite) database is created with three selection group/mode pairs (&lt;code&gt;K_RGROUP1..3&lt;/code&gt; in SYS_DATABASES). When the replication engine selects the records to replicate for a given table, it looks at the table's RGROUP:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;0&lt;/code&gt; (or empty): the table is always replicated in full (mode &lt;code&gt;A&lt;/code&gt; = All)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;1&lt;/code&gt; / &lt;code&gt;2&lt;/code&gt; / &lt;code&gt;3&lt;/code&gt;: the table follows the mode configured for that group: &lt;code&gt;A&lt;/code&gt; = All, &lt;code&gt;G&lt;/code&gt; = by Group, &lt;code&gt;U&lt;/code&gt; = by User, &lt;code&gt;M&lt;/code&gt; = Mirror&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This lets you replicate, say, companies according to one selection criterion and documents according to another. If you don't use replication, the column has no effect.&lt;/p&gt;

&lt;h4&gt;RANKING — activity-ranking flag&lt;/h4&gt;

&lt;p&gt;A boolean (&lt;code&gt;T&lt;/code&gt;) that only matters on entity tables (&lt;code&gt;KIND = 'E'&lt;/code&gt;). Tables flagged with RANKING are collected into a &quot;ranking tables&quot; list used by the Query Wizard to build two virtual query fields:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;GLOBALRANKING&lt;/strong&gt;: the sum of &lt;code&gt;count(*)&lt;/code&gt; of records linked (through the relation tables) between the queried record and each ranking table — an activity indicator, e.g. &quot;how many actions + documents + mails are linked to this company&quot;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;USERRANKING&lt;/strong&gt;: the same count, restricted to linked records whose &lt;code&gt;K_USER&lt;/code&gt; is the current user&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For backward compatibility, if the RANKING column doesn't exist in the database, the server defaults the list to DOCUMENTS, ACTIONS and MAILS — which is why those three tables typically carry the flag.&lt;/p&gt;

&lt;h4&gt;CODE — unused in the classic product&lt;/h4&gt;

&lt;p&gt;In the Efficy server code, this column is never read: nothing in the runtime uses it. Its only consumer is tooling outside the classic product, so for a standard Efficy installation it is effectively unused — you can safely ignore it (which also explains why its content just looks like the entity name in lowercase: it is generated, not consulted).&lt;/p&gt;
</description>
<category>Database</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=6915/anyone-explain-systables-possible-values-columns-ranking&amp;show=7250#a7250</guid>
<pubDate>Thu, 16 Jul 2026 15:41:37 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (W2021-147 / 2021-202)</title>
<link>https://overflow.efficy.io/?qa=7249/deal-efficy-corporate-new-build-versions-w2021-147-2021-202</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;147&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-147.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-147/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;202&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-202.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-202/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7249/deal-efficy-corporate-new-build-versions-w2021-147-2021-202</guid>
<pubDate>Mon, 13 Jul 2026 12:07:00 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-049 / W2021-145 / 2021-200)</title>
<link>https://overflow.efficy.io/?qa=7248/deal-efficy-corporate-new-build-versions-2024-049-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;49&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-049.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-049/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;145&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-145.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-145/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;200&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-200.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-200/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7248/deal-efficy-corporate-new-build-versions-2024-049-w2021-2021</guid>
<pubDate>Wed, 08 Jul 2026 12:07:39 +0000</pubDate>
</item>
<item>
<title>Answered: openEditContext(31, 0) throws &quot;Unknown TableView&quot; on Dev — works on Prod</title>
<link>https://overflow.efficy.io/?qa=7239/openeditcontext-31-throws-unknown-tableview-dev-works-prod&amp;show=7243#a7243</link>
<description>&lt;p&gt;Please open a ticket to our support, they will be able to help you with this question.&lt;/p&gt;
</description>
<category>Errors</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7239/openeditcontext-31-throws-unknown-tableview-dev-works-prod&amp;show=7243#a7243</guid>
<pubDate>Tue, 16 Jun 2026 15:26:09 +0000</pubDate>
</item>
<item>
<title>Answered: Liste des attributs possibles dans un displaybox</title>
<link>https://overflow.efficy.io/?qa=7220/liste-des-attributs-possibles-dans-un-displaybox&amp;show=7241#a7241</link>
<description>&lt;p&gt;Bonjour&lt;br&gt;
Désolé pour la réponse tardive à votre question.&lt;br&gt;
Il existe une page dans notre documentation produit en ligne qui liste les attributs disponible&lt;br&gt;
&lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/Efficy_Corporate_Edition/fune_displaybox_fields_att.html&quot;&gt;https://help.efficy.io/Efficy_Corporate_Edition/fune_displaybox_fields_att.html&lt;/a&gt;&lt;br&gt;
PS : bien penser à afficher le menu de navigation de la documentation pour aller dans les autres sections qui concernent le DisplayBox&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;http://&quot; alt=&quot;enter image description here&quot;&gt;&lt;/p&gt;
</description>
<category>E-Deal support</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7220/liste-des-attributs-possibles-dans-un-displaybox&amp;show=7241#a7241</guid>
<pubDate>Mon, 15 Jun 2026 13:43:50 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-048 / W2021-144 / 2021-199)</title>
<link>https://overflow.efficy.io/?qa=7240/deal-efficy-corporate-new-build-versions-2024-048-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;48&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-048.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-048/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;144&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-144.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-144/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;199&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-199.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-199/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7240/deal-efficy-corporate-new-build-versions-2024-048-w2021-2021</guid>
<pubDate>Mon, 15 Jun 2026 13:15:33 +0000</pubDate>
</item>
<item>
<title>Modify default notify</title>
<link>https://overflow.efficy.io/?qa=7238/modify-default-notify</link>
<description>&lt;p&gt;When creating a new user, default lines are inserted in ACC&lt;em&gt;RIGHTS :&lt;br&gt;
K&lt;/em&gt;TABLENOTIFY&lt;br&gt;
1000016&lt;br&gt;
1100016&lt;br&gt;
2000016&lt;br&gt;
2100016&lt;br&gt;
2200016&lt;br&gt;
2300016&lt;br&gt;
2400016&lt;br&gt;
3100019&lt;br&gt;
3200019&lt;br&gt;
3300019&lt;br&gt;
3600019&lt;br&gt;
3800019&lt;/p&gt;

&lt;p&gt;Is it possible to modify this default values ?&lt;br&gt;
For now, after each creation, i do an update in database, but I would like to optimise this process.&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;
</description>
<category>Database</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7238/modify-default-notify</guid>
<pubDate>Fri, 12 Jun 2026 14:54:41 +0000</pubDate>
</item>
<item>
<title>Answered: Query results clickable (links)</title>
<link>https://overflow.efficy.io/?qa=7231/query-results-clickable-links&amp;show=7232#a7232</link>
<description>&lt;p&gt;Hello, you need to add the K_CONTACT column and it should work out of the box&lt;/p&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7231/query-results-clickable-links&amp;show=7232#a7232</guid>
<pubDate>Wed, 10 Jun 2026 15:11:14 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-047 / W2021-143 / 2021-198)</title>
<link>https://overflow.efficy.io/?qa=7230/deal-efficy-corporate-new-build-versions-2024-047-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;47&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-047.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-047/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;143&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-143.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-143/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;198&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-198.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-198/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7230/deal-efficy-corporate-new-build-versions-2024-047-w2021-2021</guid>
<pubDate>Tue, 12 May 2026 08:08:14 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-046 / W2021-142 / 2021-197)</title>
<link>https://overflow.efficy.io/?qa=7229/deal-efficy-corporate-new-build-versions-2024-046-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;46&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-046.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-046/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;142&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-142.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-142/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;197&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-197.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-197/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7229/deal-efficy-corporate-new-build-versions-2024-046-w2021-2021</guid>
<pubDate>Thu, 30 Apr 2026 07:45:45 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-045 / W2021-141 / 2021-196)</title>
<link>https://overflow.efficy.io/?qa=7228/deal-efficy-corporate-new-build-versions-2024-045-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;45&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-045.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-045/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;141&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-141.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-141/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;196&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-196.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-196/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7228/deal-efficy-corporate-new-build-versions-2024-045-w2021-2021</guid>
<pubDate>Fri, 03 Apr 2026 07:36:49 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-044 / W2021-140 / 2021-195)</title>
<link>https://overflow.efficy.io/?qa=7227/deal-efficy-corporate-new-build-versions-2024-044-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;44&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-044.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-044/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;140&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-140.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-140/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;195&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-195.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-195/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7227/deal-efficy-corporate-new-build-versions-2024-044-w2021-2021</guid>
<pubDate>Fri, 27 Mar 2026 11:05:49 +0000</pubDate>
</item>
<item>
<title>Answered: Efficy Entreprise toolbar in New Outlook ?</title>
<link>https://overflow.efficy.io/?qa=7215/efficy-entreprise-toolbar-in-new-outlook&amp;show=7225#a7225</link>
<description>&lt;p&gt;Hi Dimitri,&lt;br&gt;
I have the same question. Has anyone answered you?&lt;br&gt;
Mark&lt;/p&gt;
</description>
<category>Efficy Partners</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7215/efficy-entreprise-toolbar-in-new-outlook&amp;show=7225#a7225</guid>
<pubDate>Wed, 25 Mar 2026 10:44:18 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-043 / W2021-139 / 2021-194)</title>
<link>https://overflow.efficy.io/?qa=7224/deal-efficy-corporate-new-build-versions-2024-043-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;43&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-043.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-043/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;139&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-139.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-139/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;194&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-194.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-194/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7224/deal-efficy-corporate-new-build-versions-2024-043-w2021-2021</guid>
<pubDate>Sun, 15 Mar 2026 08:58:20 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-042 / W2021-138 / 2021-193)</title>
<link>https://overflow.efficy.io/?qa=7223/deal-efficy-corporate-new-build-versions-2024-042-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;42&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-042.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-042/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;138&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-138.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-138/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;193&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-193.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-193/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7223/deal-efficy-corporate-new-build-versions-2024-042-w2021-2021</guid>
<pubDate>Sun, 08 Mar 2026 09:20:28 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-041 / W2021-137 / 2021-192)</title>
<link>https://overflow.efficy.io/?qa=7222/deal-efficy-corporate-new-build-versions-2024-041-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;41&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-041.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-041/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;137&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-137.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-137/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;192&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-192.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-192/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7222/deal-efficy-corporate-new-build-versions-2024-041-w2021-2021</guid>
<pubDate>Mon, 02 Mar 2026 09:00:34 +0000</pubDate>
</item>
<item>
<title>Answered: How works Efficy.autoMergeDuplicate exactly ?</title>
<link>https://overflow.efficy.io/?qa=6970/how-works-efficy-automergeduplicate-exactly&amp;show=7221#a7221</link>
<description>&lt;p&gt;Hello,&lt;br&gt;
Is there someone to answer ? I have the same problem ...&lt;br&gt;
Thanks&lt;/p&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=6970/how-works-efficy-automergeduplicate-exactly&amp;show=7221#a7221</guid>
<pubDate>Thu, 26 Feb 2026 11:07:15 +0000</pubDate>
</item>
<item>
<title>Answered: Delete a custom entity</title>
<link>https://overflow.efficy.io/?qa=4326/delete-a-custom-entity&amp;show=7219#a7219</link>
<description>&lt;p&gt;For Whom it may concern, The Oracle version of What Kristof presented:&lt;br&gt;
First, drop the views and tables related to the entity. With the SQL below, you can generate the drop statements&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;DECLARE
    v_K_ENTITY   NUMBER;
    v_NAME       NVARCHAR2(32);
    v_TABLENAME  NVARCHAR2(24);
BEGIN
    v_K_ENTITY := &amp;lt;YOUR K_ENTITY&amp;gt;;

    SELECT NAME
    INTO v_NAME
    FROM SYS_ENTITIES
    WHERE K_ENTITY = v_K_ENTITY;

    -- Drop view statements
   FOR r IN (
       SELECT 'drop view R_' || NAME AS stmt
       FROM SYS_TABLES
       WHERE ROUND(K_TABLE, -3)/1000 = v_K_ENTITY
           OR SUBSTR(TO_CHAR(K_TABLE), -3) = '0' || v_K_ENTITY
    ) LOOP
        DBMS_OUTPUT.PUT_LINE(r.stmt);
    END LOOP;

    -- Drop table statements
    FOR r IN (
        SELECT 'drop table ' || NAME AS stmt
        FROM SYS_TABLES
        WHERE ROUND(K_TABLE, -3)/1000 = v_K_ENTITY
           OR SUBSTR(TO_CHAR(K_TABLE), -3) = '0' || v_K_ENTITY
    ) LOOP
         DBMS_OUTPUT.PUT_LINE(r.stmt);
    END LOOP;
END;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Now proceed with the system tables cleanup. Note that the order of execution is important.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;DECLARE
     v_K_ENTITY   NUMBER := &amp;lt;YOUR K_ENTITY&amp;gt;;
     v_NAME       NVARCHAR2(32);
BEGIN

    -- Get entity name
    SELECT NAME
    INTO v_NAME
    FROM SYS_ENTITIES
    WHERE K_ENTITY = v_K_ENTITY;

    ---------------------------------------------------
    -- Ordered deletes (DO NOT REORDER)
    ---------------------------------------------------

    DELETE FROM SYS_REFERENCES
    WHERE K_TABLE = v_K_ENTITY * 1000;

    DELETE FROM SYS_QUERIES
    WHERE K_MASTER = v_K_ENTITY
       OR K_DETAIL = v_K_ENTITY;

    DELETE FROM SYS_RELATIONS
    WHERE K_TABLE1 = v_K_ENTITY * 1000
       OR K_TABLE2 = v_K_ENTITY * 1000;

    DELETE FROM SYS_RELENTITIES
    WHERE ROUND(K_TABLE, -3)/1000 = v_K_ENTITY
       OR SUBSTR(TO_CHAR(K_TABLE), -3) = '0' || v_K_ENTITY;

    DELETE FROM SYS_FIELDS
    WHERE K_TABLE IN (
        SELECT K_TABLE
            FROM SYS_TABLES
            WHERE ROUND(K_TABLE, -3)/1000 = v_K_ENTITY
    );

    DELETE FROM SYS_TABLES
    WHERE ROUND(K_TABLE, -3)/1000 = v_K_ENTITY
       OR SUBSTR(TO_CHAR(K_TABLE), -3) = '0' || v_K_ENTITY;

    DELETE FROM SYS_SECTFIELDS
    WHERE K_SECTION IN (
        SELECT K_SECTION
        FROM SYS_SECTIONS
        WHERE K_FORM IN (
            SELECT K_FORM
            FROM SYS_FORMS
            WHERE K_TABLE = v_K_ENTITY * 1000
        )
    );

    DELETE FROM SYS_SECTIONS
    WHERE K_FORM IN (
        SELECT K_FORM
        FROM SYS_FORMS
        WHERE K_TABLE = v_K_ENTITY * 1000
    );

    DELETE FROM SYS_FORMS
    WHERE K_TABLE = v_K_ENTITY * 1000;

    DELETE FROM SYS_ENTITIES
    WHERE K_ENTITY = v_K_ENTITY;

    DELETE FROM SYS_TABLEVIEWS
    WHERE ROUND(K_TABLE, -3)/1000 = v_K_ENTITY
       OR SUBSTR(TO_CHAR(K_TABLE), -3) = '0' || v_K_ENTITY;

    DELETE FROM SYS_ENTITYVIEWS
    WHERE NAME LIKE '%' || v_NAME || '%';

    ---------------------------------------------------
    -- Update with nested REPLACE
    ---------------------------------------------------

    UPDATE SYS_ENTITYVIEWS
    SET TABLEVIEWS =
        REPLACE(
            REPLACE(
                TABLEVIEWS,
                ';' || SUBSTR(NAME,1,4) || '_' || v_NAME || '=' || v_NAME,
                ''
            ),
            ';' || v_NAME || '_' || SUBSTR(NAME,1,4) || '=' || v_NAME,
            ''
        )
    WHERE TABLEVIEWS LIKE '%;' || SUBSTR(NAME,1,4) || '_' || v_NAME || '=' ||     v_NAME || '%'
   OR TABLEVIEWS LIKE '%;' || v_NAME || '_' || SUBSTR(NAME,1,4) || '=' || v_NAME || '%';

COMMIT;

END;
&lt;/code&gt;&lt;/pre&gt;
</description>
<category>Database</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=4326/delete-a-custom-entity&amp;show=7219#a7219</guid>
<pubDate>Thu, 12 Feb 2026 14:41:50 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-040 / W2021-136 / 2021-191)</title>
<link>https://overflow.efficy.io/?qa=7218/deal-efficy-corporate-new-build-versions-2024-040-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;40&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-040.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-040/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;136&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-136.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-136/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;191&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-191.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-191/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7218/deal-efficy-corporate-new-build-versions-2024-040-w2021-2021</guid>
<pubDate>Mon, 02 Feb 2026 09:57:27 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-039 / W2021-135 / 2021-190)</title>
<link>https://overflow.efficy.io/?qa=7217/deal-efficy-corporate-new-build-versions-2024-039-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;39&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-039.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-039/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;135&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-135.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-135/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;190&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-190.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-190/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7217/deal-efficy-corporate-new-build-versions-2024-039-w2021-2021</guid>
<pubDate>Sun, 18 Jan 2026 16:35:03 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-038 / W2021-134 / 2021-189)</title>
<link>https://overflow.efficy.io/?qa=7216/deal-efficy-corporate-new-build-versions-2024-038-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;38&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-038.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-038/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;134&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-134.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-134/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;189&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-189.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-189/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7216/deal-efficy-corporate-new-build-versions-2024-038-w2021-2021</guid>
<pubDate>Mon, 12 Jan 2026 08:37:54 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-037 / W2021-133 / 2021-188)</title>
<link>https://overflow.efficy.io/?qa=7214/deal-efficy-corporate-new-build-versions-2024-037-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;37&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-037.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-037/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;133&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-133.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-133/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;188&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-188.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-188/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Previous builds (2024-36, Winter2021-132, and 2021-188) have been canceled due to a critical Apache Tika vulnerability (CVE-2025-66516). &lt;br&gt;
Use these new builds where the issue is resolved.&lt;/p&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7214/deal-efficy-corporate-new-build-versions-2024-037-w2021-2021</guid>
<pubDate>Sun, 21 Dec 2025 23:49:49 +0000</pubDate>
</item>
<item>
<title>Answered: Quel est la syntaxe à utiliser pour la fonction &quot;getBusOriginLabel&quot; ? Merci</title>
<link>https://overflow.efficy.io/?qa=7209/quel-syntaxe-utiliser-pour-fonction-getbusoriginlabel-merci&amp;show=7211#a7211</link>
<description>&lt;p&gt;Exemple pour afficher sur une liste de recherche de personnes&lt;/p&gt;

&lt;p&gt;&amp;lt;column xmlns=&amp;quot;&lt;a rel=&quot;nofollow&quot; href=&quot;http://www.w3.org/1999/xhtml&amp;quot;&quot;&gt;http://www.w3.org/1999/xhtml&amp;quot;&lt;/a&gt; width=&amp;quot;10%&amp;quot; value=&amp;quot;PerBusOriginID&amp;quot; order=&amp;quot;PerBusOriginID&amp;quot;&amp;gt;&lt;br&gt;
&amp;lt;value&amp;gt;&lt;br&gt;
getBusOriginLabel(session, context, PerBusOriginID:BorID)&lt;br&gt;
&amp;lt;/value&amp;gt;&lt;/p&gt;
</description>
<category>E-Deal support</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7209/quel-syntaxe-utiliser-pour-fonction-getbusoriginlabel-merci&amp;show=7211#a7211</guid>
<pubDate>Wed, 17 Dec 2025 10:32:14 +0000</pubDate>
</item>
<item>
<title>Answered: How to overwrite/customize ckeditor.config.js properly ?</title>
<link>https://overflow.efficy.io/?qa=7207/how-to-overwrite-customize-ckeditor-config-js-properly&amp;show=7208#a7208</link>
<description>&lt;p&gt;Hello Hamid, &lt;/p&gt;

&lt;p&gt;I think this is the only way of doing so, because this is the way it has been implemented in standard. &lt;/p&gt;

&lt;p&gt;I mean in standard in the following files it is calling &lt;code&gt;Model('filebaseFolder')&lt;/code&gt; so we are forced to override the &lt;code&gt;initCkEditor&lt;/code&gt; function for the following files : &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;efficy\js\editentitygrid\main.js  &lt;/li&gt;
&lt;li&gt;efficy\js\views\editView.js&lt;/li&gt;
&lt;li&gt;efficy\pages\modal\setWidgetCaption.htm&lt;/li&gt;
&lt;/ul&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7207/how-to-overwrite-customize-ckeditor-config-js-properly&amp;show=7208#a7208</guid>
<pubDate>Tue, 02 Dec 2025 10:50:55 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-035 / W2021-131 / 2021-186)</title>
<link>https://overflow.efficy.io/?qa=7206/deal-efficy-corporate-new-build-versions-2024-035-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;35&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-035.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-035/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;131&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-131.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-131/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;186&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-186.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-186/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From the versions Winter2021-129 and 2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7206/deal-efficy-corporate-new-build-versions-2024-035-w2021-2021</guid>
<pubDate>Sun, 23 Nov 2025 14:25:14 +0000</pubDate>
</item>
<item>
<title>How to queue a function call in a workflow script to execute it async?</title>
<link>https://overflow.efficy.io/?qa=7205/how-to-queue-function-call-in-workflow-script-execute-async</link>
<description>&lt;p&gt;Hi, &lt;/p&gt;

&lt;p&gt;I am working on an integration with Efficy and Exact. One of the flows i need to implement is uploading invoices from exact to Efficy as an attachment. I currently put it in a workflow function and it works fine. However, this flow is very slow (multiple calls to exact so can't make it faster)  and is blocking the end user from doing anything for 20-30 seconds. Is there a way without using schedulers to execute this flow in an async way? A bit like queueing that the  function should be executed in the background. &lt;br&gt;
Or is the only solution using a scheduler service and just use a small time interval? &lt;/p&gt;
</description>
<category>WorkFlow / Serverscript</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7205/how-to-queue-function-call-in-workflow-script-execute-async</guid>
<pubDate>Wed, 12 Nov 2025 08:29:40 +0000</pubDate>
</item>
<item>
<title>E-Deal / Efficy Corporate New Build Versions (2024-034 / W2021-130 / 2021-185)</title>
<link>https://overflow.efficy.io/?qa=7204/deal-efficy-corporate-new-build-versions-2024-034-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of Efficy Corporate Edition are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-Deal 2024&lt;/strong&gt; - Build &lt;strong&gt;34:&lt;/strong&gt;&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-034.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-034/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;130:&lt;/strong&gt;&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-130.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-130/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;185:&lt;/strong&gt;&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-185.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-185/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From vWinter2021-129 and v2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;br&gt;
As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;br&gt;
Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7204/deal-efficy-corporate-new-build-versions-2024-034-w2021-2021</guid>
<pubDate>Fri, 07 Nov 2025 11:23:25 +0000</pubDate>
</item>
<item>
<title>Answered: AutoMailUploader - 12.1 - build 28765 - CrateMailBox issue</title>
<link>https://overflow.efficy.io/?qa=7201/automailuploader-12-1-build-28765-cratemailbox-issue&amp;show=7203#a7203</link>
<description>&lt;p&gt;the best is to open a ticket to efficy support to have a quicker answer ;)&lt;/p&gt;
</description>
<category>Errors</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7201/automailuploader-12-1-build-28765-cratemailbox-issue&amp;show=7203#a7203</guid>
<pubDate>Mon, 03 Nov 2025 16:40:48 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-033 / W2021-129 / 2021-184)</title>
<link>https://overflow.efficy.io/?qa=7200/deal-efficy-corporate-new-build-versions-2024-033-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of Efficy Corporate Edition are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-Deal 2024&lt;/strong&gt; - Build &lt;strong&gt;33&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-033.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-033/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;129&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-129.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-129/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;184&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-184.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-184/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;br&gt;
WARNING :&lt;/strong&gt; The staging file present in these builds contains wrong metadata for the Person object. Please use the following file instead : &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2024 : &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WC7ON6cTHhAitm&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Winter2021: &lt;a rel=&quot;nofollow&quot; href=&quot;https://submariners.efficy.cloud/file/list?p=rHN7WhJaSYvbP71aNa&quot;&gt;Apsis-Connector.staging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Apsis connector Update&lt;/strong&gt; (From vWinter2021-129 and v2024-033)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Synchronization extension:&lt;/strong&gt; All Apsis activities (Email, SMS, Forms, MA Flows, Events) are now synchronized with E-deal.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Improved web form processing:&lt;/strong&gt; Form data is now properly mapped, enabling accurate creation of profiles&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimized subscription management:&lt;/strong&gt; Unsubscription handling is integrated, along with synchronization of email/SMS channels.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new &quot;apsis&quot; servlet has been added in the web.xml for all apsis/ routes&lt;br&gt;
Metadata were added or modified, please use the metadatastaging\Apsis-Connector.staging file to update yours&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bee Plugin new Authentication&lt;/strong&gt;&lt;br&gt;
As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7200/deal-efficy-corporate-new-build-versions-2024-033-w2021-2021</guid>
<pubDate>Fri, 24 Oct 2025 13:06:47 +0000</pubDate>
</item>
<item>
<title>Answered: Placeholders must be setted to be interpreted ?</title>
<link>https://overflow.efficy.io/?qa=7198/placeholders-must-be-setted-to-be-interpreted&amp;show=7199#a7199</link>
<description>&lt;p&gt;Dear fauremax,&lt;/p&gt;

&lt;p&gt;In standard file &lt;strong&gt;MacroConsult.txt&lt;/strong&gt; cf macro &lt;strong&gt;DetailButton&lt;/strong&gt;&lt;br&gt;
there is an exemple of how to do such dev with the &lt;code&gt;$icon$&lt;/code&gt; macro parameter.&lt;/p&gt;

&lt;p&gt;1- the parameter is optional so in the definition of the macro &lt;strong&gt;EntityRelationsTemplate&lt;/strong&gt; I would add the &lt;code&gt;$label$&lt;/code&gt; like this : &lt;/p&gt;

&lt;pre&gt;&lt;code&gt;EntityRelationsTemplate$caption;label
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;2- in this macro I will call the &lt;code&gt;$label$&lt;/code&gt; macro parameter like this&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&amp;lt;%If('$label$', then=|&amp;lt;%(GetLabel('$label$', context=TAG)%&amp;gt;|)%&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;You will need to try this to be sure it works&lt;/p&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7198/placeholders-must-be-setted-to-be-interpreted&amp;show=7199#a7199</guid>
<pubDate>Wed, 22 Oct 2025 19:23:18 +0000</pubDate>
</item>
<item>
<title>Answered: How to deactivate OpenUrl.log log file ?</title>
<link>https://overflow.efficy.io/?qa=7196/how-to-deactivate-openurl-log-log-file&amp;show=7197#a7197</link>
<description>&lt;p&gt;As stated in the Overflow post you shared, the setting &quot;&lt;strong&gt;logOpenUrlRequests&lt;/strong&gt;&quot; is configured at the &lt;strong&gt;server level&lt;/strong&gt;, not at the &lt;strong&gt;database level&lt;/strong&gt;. &lt;/p&gt;

&lt;p&gt;Therefore, if you need to modify it, you must locate the &quot;&lt;strong&gt;serversettings.json&lt;/strong&gt;&quot; file on the server where Efficy is installed and make the change there.&lt;/p&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7196/how-to-deactivate-openurl-log-log-file&amp;show=7197#a7197</guid>
<pubDate>Mon, 20 Oct 2025 07:48:57 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-032 / W2021-128 / 2021-183)</title>
<link>https://overflow.efficy.io/?qa=7195/deal-efficy-corporate-new-build-versions-2024-032-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;32&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-032.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-032/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;128&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-128.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-128/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;183&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-183.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-183/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7195/deal-efficy-corporate-new-build-versions-2024-032-w2021-2021</guid>
<pubDate>Sun, 12 Oct 2025 10:27:23 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-031 / W2021-127 / 2021-182)</title>
<link>https://overflow.efficy.io/?qa=7194/deal-efficy-corporate-new-build-versions-2024-031-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;31&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-031.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-031/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;127&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-127.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-127/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;182&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-182.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-182/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7194/deal-efficy-corporate-new-build-versions-2024-031-w2021-2021</guid>
<pubDate>Sun, 05 Oct 2025 09:59:30 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-030 / W2021-126 / 2021-181)</title>
<link>https://overflow.efficy.io/?qa=7193/deal-efficy-corporate-new-build-versions-2024-030-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;30&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-030.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-030/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;126&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-126.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-126/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;181&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-181.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-181/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7193/deal-efficy-corporate-new-build-versions-2024-030-w2021-2021</guid>
<pubDate>Sun, 28 Sep 2025 17:08:26 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-029 / W2021-125 / 2021-180)</title>
<link>https://overflow.efficy.io/?qa=7192/deal-efficy-corporate-new-build-versions-2024-029-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of Efficy Corporate Edition are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-Deal 2024&lt;/strong&gt; - Build &lt;strong&gt;29&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-029.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-029/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;125&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-125.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-125/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;180&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-180.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-180/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;br&gt;
Bee Plugin new Authentication&lt;/strong&gt;&lt;br&gt;
As the Bee Plugin is slowly deprecating their old authentication method, E-deal will be compatible with the new authentication method starting from v2024-029 and vWinter2021-125.&lt;br&gt;
Please make sure to &lt;strong&gt;apply the new staging file&lt;/strong&gt; so the &quot;GetBeePluginInfo.Option.Hub.GetBeePluginInfo&quot; option is updated to &quot;/service/getbeeplugininfov2&quot;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7192/deal-efficy-corporate-new-build-versions-2024-029-w2021-2021</guid>
<pubDate>Fri, 12 Sep 2025 08:26:44 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-028 / W2021-124 / 2021-179 / 2019-193 / Mid2018-193)</title>
<link>https://overflow.efficy.io/?qa=7191/deal-efficy-corporate-build-versions-2024-w2021-2019-mid2018</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;28&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-028.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-028/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;124&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-124.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-124/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;179&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-179.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-179/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;E-Deal CRM 2019 by Efficy&lt;/strong&gt; - Build &lt;strong&gt;193&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_E-Deal_CRM_2019_by_Efficy-193.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/E-Deal_CRM_2019_by_Efficy-193/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;E-Deal CRM Mid-2018&lt;/strong&gt; - Build &lt;strong&gt;193&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_E-Deal_CRM_Mid-2018-193.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/E-Deal_CRM_Mid-2018-193/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7191/deal-efficy-corporate-build-versions-2024-w2021-2019-mid2018</guid>
<pubDate>Fri, 29 Aug 2025 12:03:12 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-027 / W2021-123 / 2021-178 / 2019-192 / Mid2018-192)</title>
<link>https://overflow.efficy.io/?qa=7190/deal-efficy-corporate-build-versions-2024-w2021-2019-mid2018</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;27&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-027.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-027/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;123&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-123.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-123/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;178&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-178.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-178/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;E-Deal CRM 2019 by Efficy&lt;/strong&gt; - Build &lt;strong&gt;192&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_E-Deal_CRM_2019_by_Efficy-192.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/E-Deal_CRM_2019_by_Efficy-192/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;E-Deal CRM Mid-2018&lt;/strong&gt; - Build &lt;strong&gt;192&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_E-Deal_CRM_Mid-2018-192.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/E-Deal_CRM_Mid-2018-192/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7190/deal-efficy-corporate-build-versions-2024-w2021-2019-mid2018</guid>
<pubDate>Fri, 08 Aug 2025 10:41:32 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-026 / W2021-122 / 2021-177)</title>
<link>https://overflow.efficy.io/?qa=7189/deal-efficy-corporate-new-build-versions-2024-026-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;26&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-026.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-026/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;122&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-122.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-122/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;177&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-177.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-177/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7189/deal-efficy-corporate-new-build-versions-2024-026-w2021-2021</guid>
<pubDate>Fri, 25 Jul 2025 08:40:00 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-025 / W2021-121 / 2021-176)</title>
<link>https://overflow.efficy.io/?qa=7188/deal-efficy-corporate-new-build-versions-2024-025-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-Deal 2024&lt;/strong&gt; - Build &lt;strong&gt;25&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-025.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-025/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;121&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-121.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-121/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;176&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-176.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-176/&quot;&gt;here&lt;/a&gt;&lt;br&gt;
To download the builds, use your login / password from our external repository&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;p&gt;Angular to 19.1.2&lt;br&gt;
Bootstrap to 5.3.3&lt;br&gt;
Webpack to 5.97.1&lt;br&gt;
To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;p&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;br&gt;
Generate and reload the description.&lt;br&gt;
Restart Solr.&lt;br&gt;
The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;p&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;br&gt;
Generate and reload the description.&lt;br&gt;
Then, restart Solr and launch the full indexation.&lt;/p&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7188/deal-efficy-corporate-new-build-versions-2024-025-w2021-2021</guid>
<pubDate>Fri, 11 Jul 2025 13:09:49 +0000</pubDate>
</item>
<item>
<title>does LOOKUPMASTER still working in Efficy enterprise 2024 ?</title>
<link>https://overflow.efficy.io/?qa=7187/does-lookupmaster-still-working-in-efficy-enterprise-2024</link>
<description>&lt;p&gt;hello&lt;br&gt;
we try to migrate code from 11.3 / 12.0 version to 2024 but we can't use anymore the solution of the field.LOOKUPMASTER&lt;/p&gt;

&lt;p&gt;Any alternate solution ?&lt;/p&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7187/does-lookupmaster-still-working-in-efficy-enterprise-2024</guid>
<pubDate>Thu, 10 Jul 2025 15:07:41 +0000</pubDate>
</item>
<item>
<title>Answered: Export Multivalue field that is on relation table is not working</title>
<link>https://overflow.efficy.io/?qa=7180/export-multivalue-field-that-is-relation-table-not-working&amp;show=7186#a7186</link>
<description>&lt;p&gt;We had a number of similar issues with multivalue fields on relation tables.&lt;br&gt;
Seems to be a bug on Efficy core side.&lt;/p&gt;

&lt;p&gt;The workaround that worked for us was to add dummy multivalue fields with the same definitions on every involved entity tables. &lt;br&gt;
In your case should be &lt;code&gt;DIINS.F_DD_GOS&lt;/code&gt; and &lt;code&gt;DEMA.F_DD_GOS&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Probably Efficy team have a better suggestion.&lt;/p&gt;

&lt;p&gt;Cheers&lt;/p&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7180/export-multivalue-field-that-is-relation-table-not-working&amp;show=7186#a7186</guid>
<pubDate>Thu, 10 Jul 2025 13:42:14 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-024 / W2021-120 / 2021-175)</title>
<link>https://overflow.efficy.io/?qa=7185/deal-efficy-corporate-new-build-versions-2024-024-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;24&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-024.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-024/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;120&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-120.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-120/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;175&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-175.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-175/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7185/deal-efficy-corporate-new-build-versions-2024-024-w2021-2021</guid>
<pubDate>Thu, 03 Jul 2025 12:17:31 +0000</pubDate>
</item>
<item>
<title>Does Enterprise &lt;&gt; Apsis connector accept virtual fields on field mapping ?</title>
<link>https://overflow.efficy.io/?qa=7184/enterprise-apsis-connector-accept-virtual-fields-mapping</link>
<description>&lt;p&gt;Hello,&lt;/p&gt;

&lt;p&gt;Did someone used a virtual (V_ with usage P) field during a mapping between Enterprise &amp;lt;&amp;gt; Apsis ? &lt;br&gt;
I was told that virtual fields are supported by Enterprise &amp;lt;&amp;gt; Apsis connector. It is possible to select the field during the mapping (Apsis interface). But when running the full sync I am getting the error that &lt;code&gt;V_  fields is invalid column name&lt;/code&gt; which is normal in Enterprise as it's a virtual field.&lt;/p&gt;

&lt;p&gt;To get the contacts based on mapped fields in Apsis, Apsis calls an Enterprise node/api end point &lt;code&gt;serverjs\api\node\marketing\apsis\contacts.js&lt;/code&gt; which calls a function from  &lt;code&gt;serverjs\marketing\apsis.js &amp;gt; contacts&lt;/code&gt; that runs a query using the provided list of fields from a payload.&lt;img src=&quot;https://overflow.efficy.io/?qa=blob&amp;amp;qa_blobid=15271177369622694093&quot; alt=&quot;enter image description here&quot;&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Internal replies from @Kristof Pauwels:&lt;/strong&gt; &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The consult, list and search API do not support virtual fields, they&lt;br&gt;
are always excluded from the result.  That's not wrong on itself, it&lt;br&gt;
guarantees the best performance. Only when running a query, virtual&lt;br&gt;
fields can be included. So it will depend on what operation the Apsis integration uses. There are dedicated Apsis system queries and ServerJs node endpoints..&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;You can also decide to override the contacts method with a custom&lt;br&gt;
version. Try using the &lt;code&gt;&amp;lt;#Field&amp;gt;&lt;/code&gt; tag and see if its replaced by the&lt;br&gt;
SQL expression, else you have to hardcode the SQL expression and&lt;br&gt;
alias it as V_MYCOLUMN.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7184/enterprise-apsis-connector-accept-virtual-fields-mapping</guid>
<pubDate>Tue, 01 Jul 2025 13:41:14 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-023 / W2021-119 / 2021-174)</title>
<link>https://overflow.efficy.io/?qa=7183/deal-efficy-corporate-new-build-versions-2024-023-w2021-2021</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;23&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-023.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-023/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;119&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-119.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-119/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;174&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-174.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-174/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7183/deal-efficy-corporate-new-build-versions-2024-023-w2021-2021</guid>
<pubDate>Tue, 24 Jun 2025 08:08:08 +0000</pubDate>
</item>
<item>
<title>E-deal / Efficy Corporate New Build Versions (2024-022 / W2021-118 / 2021-173/ 2019-191 / Mid2018-191)</title>
<link>https://overflow.efficy.io/?qa=7182/deal-efficy-corporate-build-versions-2024-w2021-2019-mid2018</link>
<description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;The new builds versions of E-deal are available for the following versions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;E-deal 2024&lt;/strong&gt; - Build &lt;strong&gt;22&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_2024-022.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/2024-022/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Winter 2021&lt;/strong&gt; - Build &lt;strong&gt;118&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Winter2021-118.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Winter2021-118/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficy Corporate Edition 2021&lt;/strong&gt; - Build &lt;strong&gt;173&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_Efficy_Corporate_Edition_2021-173.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/Efficy_Corporate_Edition_2021-173/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;E-Deal CRM 2019 by Efficy&lt;/strong&gt; - Build &lt;strong&gt;191&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_E-Deal_CRM_2019_by_Efficy-191.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/E-Deal_CRM_2019_by_Efficy-191/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;E-Deal CRM Mid-2018&lt;/strong&gt; - Build &lt;strong&gt;191&lt;/strong&gt;:&lt;br&gt;
-- Release note : &lt;a rel=&quot;nofollow&quot; href=&quot;https://help.efficy.io/E-deal_crm/releaseNote_E-Deal_CRM_Mid-2018-191.html&quot;&gt;here&lt;/a&gt;&lt;br&gt;
-- Build : &lt;a rel=&quot;nofollow&quot; href=&quot;https://repository.efficy.cloud/artifactory/edeal-repo-lib/com/edeal/frontline/edeal-distribution/E-Deal_CRM_Mid-2018-191/&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To download the builds, use your login / password from our external repository&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;!!! PRE-REQUISITES BEFORE INSTALLATION !!!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New Microsoft Authentication Method for the Outlook plug-in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Following our previous communication regarding Microsoft’s new authentication method, we are pleased to announce that the builds for the affected versions will be made available on May 22, 2025.&lt;/p&gt;

&lt;p&gt;To assist you with this update, a link to the step-by-step procedure is available in the dedicated folder for the Outlook plug-in installation within our online documentation on E-deal. You will be able to navigate through the relevant chapters as needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outlook plugin for on-premise versions of Exchange Server (2013, 2016, 2019):&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;if new manifest (since v2024 Build 21, vWinter2021 Build 117, v2021 172) has been installed you need to delete the 'WebApplicationInfo' tag added to the e-deal-crm-outlook-plugin-manifest.xml file. If no you can keep your current manifest.&lt;/p&gt;

&lt;p&gt;set the new OfficeAddIn.Api option to 'EWS' : Use the staging file metadatastaging\OfficeAddinAPI_option.staging provided in the distribution.&lt;/p&gt;

&lt;p&gt;If you require any assistance with the implementation of this procedure or have any questions, please do not hesitate to contact our Customer Care team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Extranet upgrade&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The majority of the extranet node's dependencies have been updated, notably :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Angular to 19.1.2&lt;/li&gt;
&lt;li&gt;Bootstrap to 5.3.3&lt;/li&gt;
&lt;li&gt;Webpack to 5.97.1&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To upgrade those dependencies, ng-jhipster has been removed and replaced by already present libraries.&lt;br&gt;
Moment and moment-timezone were also removed as they were not used.&lt;br&gt;
Tslint has been replaced by es-lint.&lt;br&gt;
The webpack build module has been changed from commonJs to ES6.&lt;/p&gt;

&lt;p&gt;Node and npm version has also been updated to 22.13.1 and 10.9.2.&lt;br&gt;
You should upgrade your own version of node and npm to the one above when working with the extranet.&lt;/p&gt;

&lt;p&gt;On java's side, Jhipster has been updated to 8.8.0 and Spring Boot to 3.4.1.&lt;br&gt;
Sonar plugin and properties were removed from the pom as they were not used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vulnerability - Migration from solr3 to solr8.11.2&lt;/strong&gt;&lt;br&gt;
(from the build W2021-032 / 2021-89 / 2019-133)&lt;/p&gt;

&lt;p&gt;In order to fix vulnerabilities, the solr version has been upgraded from v3.6.2 to v8.11.2 (working with servlet above or equal to v3.1 (javax.servlet)).&lt;/p&gt;

&lt;p&gt;Only the Solr home direction need to be updated with the Solr 8.11.2 jars and the new configuration : in the Solr home directory any jars with the version 3.6.1 need to be replaced as well as the configuration files.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the content of the solr home directory by the content you can&lt;br&gt;
find under the distribution res/solr.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Restart Solr.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The existing indexation may work, but in case of any issue a full re-indexation may be required by following these steps :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Delete existing index : /edeal/data and /knowledgebase/data.&lt;/li&gt;
&lt;li&gt;Generate and reload the description.&lt;/li&gt;
&lt;li&gt;Then, restart Solr and launch the full indexation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;Efficy R&amp;amp;D Teams&lt;/p&gt;
</description>
<category>Announcements</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7182/deal-efficy-corporate-build-versions-2024-w2021-2019-mid2018</guid>
<pubDate>Fri, 06 Jun 2025 11:50:45 +0000</pubDate>
</item>
<item>
<title>how to set main = 1 using /addrelation web request</title>
<link>https://overflow.efficy.io/?qa=7181/how-to-set-main-1-using-addrelation-web-request</link>
<description>&lt;p&gt;Hi, i'm using web request /addrelation like this:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;fetch(
&quot;/crm/addrelation?edithandle=&quot;.concat(
  Model.get(&quot;editHandle&quot;),
  &quot;&amp;amp;bookmark=&quot;,
  Model.get(&quot;bookmark&quot;),
  &quot;&amp;amp;entity=Mark&amp;amp;key=&quot;,
  kMarket
).then(...)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;It is working this way, but how would i set main = 1 in the relation, using this request?&lt;/p&gt;

&lt;p&gt;Thanks in advance!&lt;/p&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7181/how-to-set-main-1-using-addrelation-web-request</guid>
<pubDate>Wed, 28 May 2025 16:48:01 +0000</pubDate>
</item>
<item>
<title>How to make appear a filter on same fields for different entities in query builder ?</title>
<link>https://overflow.efficy.io/?qa=7179/make-appear-filter-fields-different-entities-query-builder</link>
<description>&lt;p&gt;Hello,&lt;/p&gt;

&lt;p&gt;Imagine you have a query that shows list of document and the contacts that are linked to it.&lt;/p&gt;

&lt;p&gt;The selection fields will be DOCUMENTS.NAME, CONTACTS.NAME, CONTACTS.FIRSTNAME, etc..&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://overflow.efficy.io/?qa=blob&amp;amp;qa_blobid=8290205301470632635&quot; alt=&quot;enter image description here&quot;&gt;&lt;/p&gt;

&lt;p&gt;When running the query I've get the grid with the results. On the header of DOCUMENTS.NAME I have a filter that allows to search/filter by document name.&lt;br&gt;
&lt;img src=&quot;https://overflow.efficy.io/?qa=blob&amp;amp;qa_blobid=3655404963710729320&quot; alt=&quot;enter image description here&quot;&gt;&lt;/p&gt;

&lt;p&gt;When looking into CONTACTS.NAME header the filter is not present.&lt;br&gt;
&lt;img src=&quot;https://overflow.efficy.io/?qa=blob&amp;amp;qa_blobid=15958168956195280864&quot; alt=&quot;enter image description here&quot;&gt;&lt;/p&gt;

&lt;p&gt;From what I understand the same field naming NAME causes the issue. But when I set an alias on one of them I loose the filter too.&lt;/p&gt;

&lt;p&gt;How could I manage to show the filter on both NAME fields ? &lt;br&gt;
Should I name (alias) a field and use the alias to create a grid definition to make include the filter ? &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;Finally with custom definition of an ALIAS it works.&lt;br&gt;
&lt;img src=&quot;https://overflow.efficy.io/?qa=blob&amp;amp;qa_blobid=15585575705114281849&quot; alt=&quot;enter image description here&quot;&gt;&lt;/p&gt;

&lt;p&gt;In GridColumnsCustom.txt: &lt;/p&gt;

&lt;pre&gt;&lt;code&gt;th.ContactName {[&amp;lt;th class=&quot;text-center nowrap&quot;&amp;gt;&amp;lt;#H=$FIELD$;sort=true;hfilter=true&amp;gt;&amp;lt;/th&amp;gt;]}
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The main point is to have the propriety &lt;strong&gt;hfilter=true&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;To make it more generic alias ENTITYNAME.&lt;br&gt;
GridColumnsCustom.txt: &lt;/p&gt;

&lt;pre&gt;&lt;code&gt;th.ENTITYNAME {[&amp;lt;th class=&quot;text-center nowrap&quot;&amp;gt;&amp;lt;#H=$FIELD$;sort=true;hfilter=true;Text=$ENTITY$Name&amp;gt;&amp;lt;/th&amp;gt;]}
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;And the $ENTITY$Name depending on entity will be ContName, CompName, etc... can be translated in CustomLabels.txt.&lt;/p&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=7179/make-appear-filter-fields-different-entities-query-builder</guid>
<pubDate>Tue, 27 May 2025 07:40:28 +0000</pubDate>
</item>
</channel>
</rss>