Disable input of connection attrbutes in RPD (BI Admin Tool) when connection is defined "externalize

gmigotto

Organization Name

Assicurazioni Generali

Description

Now, when a connection is defined "externalized" (so, connection information are defined in DC Console.Connections), attributes (data source, credentials, ...) remain editable and can differ from the one specified in DV in the externalized connection.

 

Use Case and Business Need

Ad administrative/development case. This change will lead to a single point of storage of connection attributes and help evoid errors (see details)

More details

As a side effect, put the light on this request will probably help reveal (and hopefully solve) the following bug (described in detail in SR 3-24753265591 : Error connecting to from DV to ADW after connecting to PBCS): when using ad ADW-based subject area in a DV project AFTER having connected to a PBCS application through the EPM Cloud connection defined in DV Console, we got invalid password error; we discovered that it was caused by a misalignment between the password defined on the externalized connection (DV concsole) and the one defined in RPD. this usually doesn't emerge, because DV always reads the externalized connection credentials, but after an EPM Cloud connection, it someway "switches" to the credentials stored in the RPD and, if the two are aligned, gives the error; this happens for HALF AN HOUR or so (after that time, perhaps due to some timeout expiration or "connection alignment" clock, the error disappears and we can connect to the subject area - till the next use of the EPC Cloud connection). Befor this timeframe, only solution is to restart the service (no other action - logoff/login, change browser, clear cache - works).

 

Original Idea Number: 34f7045e25