Skip to main content

Idea pipeline (top 25)

Filter by idea status

Filter by product

2004 Ideas

Ricky
Superhero
RickySuperhero

Specify a collation for 1 specific column in a tableOpen

We like to be able to specify a collation for 1 specific column in a table in the model.Currently our default database collation is set to SQL_Latin1_General_CP1_CI_ASWe have this special column that really wants be case-sensitive and wants to be unique preferably Latin1_General_100_CS_AI_SC_UTF8  so that not only case-sensitive uniqueness is guaranteed but als super/subscripting for cubic meters for example. The latter can be achieved, but we cannot seem to find a way to make this specific column case sensitive/sub/supercripting ‘aware’ towards the database.We also would like to have the user interface to react to it as it was case insensitive in lookups for example. How can I achieve such functionality? An example is milliohm [mΩ] to meg(a)ohm [МΩ] (or mOhm and MOhm) - the column for such unit has to be unique since they actually really mean a load of difference in resistance, but I want them to be found by the user when typing in any case ‘mohm’ which currenly follows the collation rules:above is Latin1_General_100_CS_AI_SC_UTF8 (needs UTF8 and case sensitive for for both case and sub/superscripting uniqueness) where you can see that the client will act accordingly to the collation - which we do not want to happen.We want the user to have a result in a lookup that gives both options despite the collation settings:We do not want to bypass the SF-model or fiddle around with tags or dynamic(ly)/manually generated stuff. 

Arie V
Community Manager
Arie VCommunity Manager

IAM: delete authentication details when changing from IAM to External/Windows authentication typeOpen

We are about to move our users from IAM to External authentication type. Testing and reviewing this migration proved very simple: I only have to change the authentication type for the user from IAM to External. This change seems to do nothing more and nothing less than updating the authentication type of the user in the usr_authentication table. The great benefit of SSO is not only a better User Experience, but also improved security, as it eliminates the need for storing User credentials in different systems (i.e. it reduces the ‘attack surface’ for hackers). For the purpose of improved security I would therefore advocate that the (now obsolete) authentication details from the usr_authentication table in IAM should be deleted when changing from IAM to External or Windows authentication type.I intend to run this script myself after having updated the authentication type, but I would rather see IAM doing this by default:UPDATE usr_authentication SET two_factor_authentication_type = 0 , totp_key = null , totp_active = 0 , password_hash = null , password_salt = null , password_algorithm = nullwhere authentication_type = 4 and password_hash is not nullNote: to make sure this doesn't happen accidently or unnoticed, I would recommend adding a warning message or confirmation when an administrator is changing the authentication type from IAM to External.Note 2: I am not certain about Kerberos authentication type, but I think the same would apply.

Add the 'Generated' property for process actions and process variablesClosed

I would like to have the ‘Generated’ property available for process actions and process variables. (Possibly process steps as well since these are dependent on process actions and might cause errors during generation if these aren’t generated as well)I am running into problems with partially generated process flows. A process flow can have the ‘Generated’ property in the SF but individual process actions and process variables cannot. This causes some issues when adding process actions/variables through the dynamic model. To manage these generated process actions and variables, we have to write code to check for them and delete/update them when needed. This is functionality that is available for most other objects in the SF by default.There is also the problem that dynamic model code to manage these object without the ‘Generated’ property can only be executed after the other generated objects are automatically deleted and re-created through the generation process. (Because it is impossible to execute code from the dynamic model before the ‘delete generated objects’ process during generation.) In some cases this causes errors during generation when these objects are dependent on objects that do have the ‘Generated’ property.I’ve noticed that these objects do have a ‘Generation’ group label under ‘Trace info’ but the only column available there is ‘By control procedure’. Does this indicate that the ‘Generated’ property is planned to be added in a later release?