I am confused on the workings of code history tab on control procedures - templates. The workings seems to differ from one version to another. The way I would expect it to work is like this: The template is created in the trunk, amended in the trunk a day later. The next day a branch is created and the template is amended in the branch. And the next day it is merged back to the trunk. trunk - create the template on 2019-1-1 in version 1.00 trunk - amended the template on 2019-1-2 in version 1.00 branch - amended the template on 2019-1-3 in version 1.00 (branch) trunk - merged the branch back to the trunk on 2019-1-4 in version 1.10 now in the trunk I would expect the following in the code history: insert - trunk - 1.00 - 2019-1-1 update - trunk - 1.00 - 2019-1-2 update - branch - 1.10 - 2019-1-4 and in the branch the following: insert - trunk - 1.00 - 2019-1-1 update - trunk - 1.00 - 2019-1-2 update - branch - 1.00 - 2019-1-3 what i actually get after merging is this in t
During development you often have a SF and the application running against the SF. However, both have the same icon. Is there an option to change the icon for the application when it's running against the SF?
When you have an information panel on your screen the reload of this information panel makes all tasks disappear from the tasks/reports bar, probably due to the row loosing it's focus. Is there a way to prevent this from happening without creating a process flow to retain the focus?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.