Verify if the SysConfig are in the standard iDempiere System

Description

We have to check if all needed sysconfig keys are in the standard iDempiere system. All keys that can be changed on client level should be there.

Reference: http://wiki.idempiere.org/en/IDempiere_workshop_2015/transcript#Sysconfig_Keys

Environment

None

Activity

Show:
Hiep Lq
June 6, 2018, 1:19 PM

on sql migrate i see two line can make conflict

line 51: update ad_sysconfig set ad_sysconfig_id=200137, ad_sysconfig_uu='0599feeb-845f-4ccb-a740-94ad04c85d64' where ad_client_id=0 and name='ZK_SESSION_TIMEOUT_IN_SECONDS';

line 122: INSERT INTO AD_SysConfig (AD_SysConfig_ID,AD_Client_ID,AD_Org_ID,Created,Updated,CreatedBy,UpdatedBy,IsActive,Name,Value,Description,EntityType,ConfigurationLevel,AD_SysConfig_UU) VALUES (200137,0,0,TO_DATE('2018-05-02 15:45:08','YYYY-MM-DD HH24:MI:SS'),TO_DATE('2018-05-02 15:45:08','YYYY-MM-DD HH24:MI:SS'),100,100,'Y','ZK_SESSION_TIMEOUT_IN_SECONDS','-2','ZK session timeout. -2 meaning not set','D','O','0599feeb-845f-4ccb-a740-94ad04c85d64')

Carlos Ruiz
June 6, 2018, 1:47 PM

Thanks ,

It is intentional, because these features were created some time ago, many implementations probably already have defined their own keys in System client.

So, the update covers the case when the implementation already defined the key locally, and the insert covers the case when it is not defined yet.

For the first scenario when the update succeeds the insert will fail - but it would be a failure that can be ignored by the implementor.

Another approach would be to try to change the insert with a conditional insert (insert if not exists).

Assignee

Carlos Ruiz

Reporter

Diego Ruiz

Tested By

None

Priority

Minor
Configure