Eliminate all creation / generation tasks in SF

@Harm Horstman and other Voters: On the Translations topic, how would you feel about also automatically using the ‘Translate’ task which effectively removes the [], replaces the _ with a space and changes the first character to a capital?

I'd be in favor of including that too (for the default Language), potential changes could then be done as part of the Approval step.

If it were an option to enable, I would not mind it. Some projects or customers might have columns, parameters that can easily be translated 1:1.

In our project we have prefixed a lot as somewhat of a replacement for schemas and certain terms are quite technical, that have an entirely different user friendly translation. So the automatic method would not help us in most cased and makes it hard to identify them as they count as “translated” now.

The 'automatic' translation function is not very useful for us, for the following reasons:
- multiple active languages
- grid header translations are often different
- tooltips always remain manual work
- naming convention applies to columns, often including abbreviations

The full creation process essentially enriches the model and sets up the updates for the database and logic layer. 

While a lot of database and logic layer updates originate from tables, tasks, reports, process flows and their parameters, it is worth noting that any change to the model may introduce changes in the database or logic layer. Dynamic modeling which is invoked during the creation process allows these kinds of cascading changes.

For example, adding a role may cause an extra checkbox column to be generated in the ‘employee’ table to facilitate a synchronization mechanism of role information from IAM to your product.

With this in mind, literally any change to the model could potentially require the full creation process to be kicked off.

There are some situations that are surefire moments to start full creation, for instance adding a column. However, if the developer is adding a few new tables and columns one-by-one, the creation process will have to be aborted and rebooted after every change or will have to be debounced somehow.

In short, I doubt this is practical for the full creation process.

For individual specific scenarios such as translation generation, code group generation or control procedure generation it may be more feasible to do this on certain changes to the model.

@Anne Buit, thanks for your response on this topic. Of course, it must be ensured at all times that the model remains consistent in all respects.

However, I would definitely do the generation processes that can be automated and also see if the more complex processes can also be performed automatically under certain conditions.

There is much to be gained, my estimate is that more than 25% of the time, during development with the software factory, consists of waiting.

Another one I'd like to address…