Skip to main content

Idea pipeline (top 25)

Filter by idea status

Filter by product

1967 Ideas

Third option for manual data conversion - SmartOpen

Our team is currently investigating adding our manual data conversion scripts to the SF instead of managing them manually and running a bunch of scripts before and after the 020-upgrade script.We ran into a small issue, the current option for adding manual data conversion including from version x to y or always don't exactly suffice. We are looking for a smart option in between those two, which works similarly to a smart upgrade of tables, control procedures or tasks. An example of the problem, I have version 1.1, 1.2 and 1.3 of a project. If I add a manual conversion script to the 1.2 using the ‘always’ option, this script is generated into any upgrade following the 1.2 upgrades. For example 1.1 → 1.2, 1.1 → 1.3 but also 1.3 → 1.4. And that one we find less desirable.If we chose the second manual data conversion option, x to y, and add the script to the 1.2 version we have to specify which specific version the code is generated from (the x). Most logical would be to specify this manual data conversion script to be applicable from 1.1 to 1.2. Now the conversion script is only generated into upgrades from 1.1 → 1.2. Not into 1.1 → 1.3 for example.  We would like to be able to generate these into upgrade scripts ‘smart’-ly. Thus, if we add a manual conversion script in version 1.2, it will be generated in updates 1.1 → 1.2, 1.1 → 1.3, 1.1 → 1.4, etc. But not into the upgrade script 1.3 → 1.4.Splitting up upgrades and upgrading from 1.1→ 1.2 and then 1.2→ 1.3 manually doesn't work for us as we have about 40 instances of our applications running as production databases, a fair number of which are 24/7 available/active with limited time for downtime/upgrades.

'Default User Groups' should always be updated by Sync to IAMOpen

​Hi,To enable us developers, apply correct role assignment to IAM 'User Groups' from SF via 'Default User Groups'. Default User Groups from Software Factory should be used as a template for related applications' User Groups in IAM.New changes from 'Default User Groups' should always apply and overwrite every time US developers 'Sync To IAM.'We were informed that "if you want to un-grant access of existing roles, you need to change it within the IAM as the Default user group will not overrule (and thus not un-grant) the existing role assignment" , in our recent ticket in TCP.Every deployments from SF to different environments or If we need to apply corrections for non development environments, We sync to IAM:* After creation once the an environment is upgraded with the new objects from SF * We do a 'Sync to IAM' for the rights changes in the 'Roles' and 'Default User Groups' from the main branch* After 'Sync to IAM' from SF, I press the 'Apply Default Authorization' in IAM for the synced 'Default User Groups(SF)' to apply on 'User Groups(IAM)'* Then the 'User Groups' from IAM should mirror the 'Default User Groups' from SF regardless of if a user group is just new or old, and SF User Group is the main templateThis should be the case so that, It is faster to remove/add roles from a user group if changes were introduced by the users.and the default user groups changes is always kept in every creation of a branch of a model and is no need to manually change the role assignments from User Groups in IAM every time we have a deployment.We have scenarios where:If the Admin gets a complain that a User is missing Roles then a Custom IAM user group can be created to attach on the related problematic user(s). A ticket to update the defaults in case it is for everyone on the same Default User group should be raised to do so in SF.If the Admin/Manager sees a User having more permissions than expected a temporary removal from the Default User Group can be made. A ticket to update the defaults in case it is for everyone on the same default User group should be raised to do so in SF or add an extra default User group to cater for this scenario of Users.Regards,Jeff  ​